June 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2542) NullPointerException in TypeFactory.replaceAssociations for ComponentType

by Reto Urfer (JIRA)

NullPointerException in TypeFactory.replaceAssociations for ComponentType ------------------------------------------------------------------------- Key: HHH-2542 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2542 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Reporter: Reto Urfer The following code block will throw a NullPointerException when targetComponentValues should be determines and target[i] contains a NULL value. else if ( types[i].isComponentType() ) { // need to extract the component values and check for subtype replacements... AbstractComponentType componentType = ( AbstractComponentType ) types[i]; Type[] subtypes = componentType.getSubtypes(); Object[] origComponentValues = original[i] == null ? new Object[subtypes.length] : componentType.getPropertyValues( original[i], session ); Object[] targetComponentValues = componentType.getPropertyValues( target[i], session ); replaceAssociations( origComponentValues, targetComponentValues, subtypes, session, null, copyCache, foreignKeyDirection ); This problem can be fixed the same way as it is prevented when origComponentValues are determined (see following line) Object[] targetComponentValues = target[i] == null ? new Object[subtypes.length] : componentType.getPropertyValues( target[i], session ); copied[i] = target[i]; } The problem did not exist in Version 3.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2369) Documentation doesn't state what hibernate returns for empty/null collections

by James Roper (JIRA)

Documentation doesn't state what hibernate returns for empty/null collections ----------------------------------------------------------------------------- Key: HHH-2369 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2369 Project: Hibernate3 Type: Improvement Components: documentation Versions: 3.2.1 Reporter: James Roper Priority: Trivial Reading the hibernate documentation, section 6.1: "Hibernate does not distinguish between a null collection reference and an empty collection" This is all very well, but what does hibernate return when loading a null/empty collection? According to the EJB3 specification, section 2.1.7: "If there are no associated entities for a multi-valued relationship of an entity fetched from the database, the persistence provider is responsible for returning an empty collection as the value of the relationship." If this is the behavior that hibernate implements, then this should be explicitly stated in the hibernate documentation, so that developers know whether they need to do null checks or not after loading an object from the database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2468) Is setParameter 0- or 1-based?

by Rafael Borges (JIRA)

Is setParameter 0- or 1-based? ------------------------------ Key: HHH-2468 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2468 Project: Hibernate3 Type: Bug Versions: 3.2.2 Environment: Hibernate 3.2.2.GA, RDBMS: H2, version: 1.0 (2007-01-30), JDK 6.0, Windows XP Pro Reporter: Rafael Borges Priority: Trivial The following query throws a wrong message in the Exception == Query == query = session.createQuery("select t from Test t where t.id = ?"); query.setParameter(1, 1); == Message == Exception in thread "main" java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based! at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterDescriptor(ParameterMetadata.java:55) at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterExpectedType(ParameterMetadata.java:61) at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:397) at org.hibernate.impl.AbstractQueryImpl.setParameter(AbstractQueryImpl.java:369) at Test.main(Test.java:25) The Javadoc says it is 0-based, and that works perfectly when used accordingly. So I think it is just a comestic fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2519) Schema dropping not documented with hibernate.hbm2ddl.auto=create

by Ville Skyttä (JIRA)

Schema dropping not documented with hibernate.hbm2ddl.auto=create ----------------------------------------------------------------- Key: HHH-2519 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2519 Project: Hibernate3 Issue Type: Patch Components: documentation Environment: svn trunk Reporter: Ville Skyttä Attachments: create-drops.patch Dropping the schema is not documented with hibernate.hbm2ddl.auto=create, fix attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-79) Recommend to use FlushMode.APPLICATION on massive indexing

by Emmanuel Bernard (JIRA)

Recommend to use FlushMode.APPLICATION on massive indexing ---------------------------------------------------------- Key: HSEARCH-79 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-79 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.0.0.beta3 Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.0.0.beta4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2696) Consider migrating to slf4j

by Koda Janh (JIRA)

Consider migrating to slf4j --------------------------- Key: HHH-2696 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.4 Reporter: Koda Janh Please consider migrating away from commons-logging and onto slf4j for the reasons mentioned here: http://www.qos.ch/logging/classloader.jsp The author of log4j went on to write "logback" which is an implementation of slf4j that has much better performance than log4j and much cleaner output. I recommend you evaluate these alternatives seriously and consider them for future releases of Hibernate. To ease migration you could use the "log4j bridge" mentioned here: http://logback.qos.ch/bridge.html You simply replace log4j's jar by the bridge jar and all log4j method calls get redirected to logback under the hood. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
8
0 / 0

[Hibernate-JIRA] Created: (ANN-530) introduce fetch_size for Hibernate Search scrollable resultsets.

by Emmanuel Bernard (JIRA)

introduce fetch_size for Hibernate Search scrollable resultsets. ---------------------------------------------------------------- Key: ANN-530 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-530 Project: Hibernate Annotations Type: New Feature Components: search Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HBX-950) Code generation on seam-gen projects includes fake tx manager

by Max Rydahl Andersen (JIRA)

Code generation on seam-gen projects includes fake tx manager ------------------------------------------------------------- Key: HBX-950 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-950 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2beta10 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 org.hibernate.console.FakeTransactionManagerLookup should not end up in generated hibernate.cfg.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-615) Inherited relationships not found in collections of subclasses of the entity containing the relationship

by Michael Newcomb (JIRA)

Inherited relationships not found in collections of subclasses of the entity containing the relationship -------------------------------------------------------------------------------------------------------- Key: ANN-615 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-615 Project: Hibernate Annotations Issue Type: Bug Components: binder Reporter: Michael Newcomb Consider: @Entity public class A { @Id @GeneratedValue protected int id; @OneToMany(mappedBy = "a") protected Collection<C> c; } @Entity public abstract class B { @Id @GeneratedValue protected int id; @ManyToOne protected A a; } @Entity public class C extends B { } Gives the following errors upon deployment: Caused by: org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: com.gd.iewtpt.isi.C.a in com.gd.iewtpt.isi.A.c at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:552) at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:517) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:316) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:186) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:246) ... 7 more I can get around this issue, but it seems there is a bug here... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-88) Workspace.getIndexReader AssertionFailure: Tries to read for update a index while a writer is accessed

by Charles Chappell (JIRA)

Workspace.getIndexReader AssertionFailure: Tries to read for update a index while a writer is accessed ------------------------------------------------------------------------------------------------------ Key: HSEARCH-88 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-88 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.beta3 Environment: Hibernate 3.2.4.sp1, PostGRESQL Reporter: Charles Chappell Priority: Blocker May be an application server interaction. Somewhat sporatic, but always in the same places in my code. Basically I had one class that created an entity exit via NullPointerException, (Database updates were successful) and a second attempt to read the same data was made, and failed due to this assertion. The only connection to Hibernate Search is via the Annotations/Runtime, nowhere in this process did I directly use Hibernate Search. I'll attempt to produce test code, since this is the simplest case that I've gotten this assertion failure in. Application Server is Glassfish, reproducable both on OSX and Solaris 10 Intel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

3
14
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2007