April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4053) Incorrect SQL with substring for Firebird

by yeti the foot (JIRA)

Incorrect SQL with substring for Firebird ----------------------------------------- Key: HHH-4053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4053 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.1 Reporter: yeti the foot HQL query substring function generate incorrect SQL query for Firebird. In Firebird SQL query with substring has follow syntax: substring(str from 1 for 3). Generated ин Hibernate query looks like: substring(str, 1, 3). -- 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

16 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2190) JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed()

by Jeffrey Bennett (JIRA)

JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed() ------------------------------------------------------------------------------------- Key: HHH-2190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2190 Project: Hibernate3 Type: Bug Components: core Reporter: Jeffrey Bennett In error-handling routines, I use Transaction.isActive() to determine if it is 'safe' to perform Transaction.rollback(). If the Session has previously closed, Transaction.isActive() mis-reports that the transaction is still alive when it is not. I'll grant that the JavaDoc for isActive indicates it is the 'local transaction', not the underlying transaction, but since there is no way to delve into the underlying connection in the public API, that is really a cop-out. If you don't like the idea of modifying the behavior of isActive(), how about exposing a 'public Connection connection()' method that exposes the connection? -- 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

16 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3058) When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query

by Sean Blaes (JIRA)

When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query --------------------------------------------------------------------------------------------------------------------------- Key: HHH-3058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3058 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4sp1, Microsoft SQL Server Reporter: Sean Blaes Priority: Minor When using a query similar to the following: DECLARE @SUB_TABLE TABLE( ID INT ) INSERT INTO @SUB_TABLE SELECT ID FROM FOO SELECT * FROM BAR INNER JOIN @SUB_TABLE ON ... Then if I call setMaxResults(100) on the query object. It inserts "TOP 100" in the first query, which isn't really what would be expected. Since the second SELECT actually consists of the data that will be returned, the TOP 100 statement should go there. I'd expect it's an easy fix. Just start your search for SELECT from the bottom rather than the top. However, I guess you have to make sure you're not hitting a subquery of a larger select either... I may try cooking up a patch this weekend for this if I can find the time, and I'll attach it to this issue if I do. -- 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

16 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3405) Add support for Unicode aware MS SQL Server dialect

by Chris Larun (JIRA)

Add support for Unicode aware MS SQL Server dialect --------------------------------------------------- Key: HHH-3405 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3405 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.6 Reporter: Chris Larun Cf. http://jira.atlassian.com/browse/CONF-4786 for a description of the issue. http://forum.hibernate.org/viewtopic.php?t=941781&highlight=sqlserver+dia... for a possible solution. -- 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

16 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3905) Improve FieldInterceptionHelper perfomance

by Sergey Vladimirov (JIRA)

Improve FieldInterceptionHelper perfomance ------------------------------------------ Key: HHH-3905 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3905 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Sergey Vladimirov Priority: Minor Attachments: patch.txt do not iterate over interfaces, use Class.isAssignableFrom -- 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

16 years, 1 month

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-1989) Deleted object remains referenced in 2nd level cache collections

by Justin Haddad (JIRA)

Deleted object remains referenced in 2nd level cache collections ---------------------------------------------------------------- Key: HHH-1989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1989 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: Spring 1.2.8, Hibernate 3.2, Postgres 8.0.3 Reporter: Justin Haddad This problem seems identical to issue NH-678. I have enabled caching for an one-to-many association. I use Ehcache. I have a test in which I load the parent object along with its collection. Both the parent and the collection wind up in the 2nd level cache. I then delete an object that is in the collection, not by removing it from the collection, but rather by doing a delete on the object itself. After deleting, I try to reload the parent and get the following exception (User#3102 is the deleted object): aused by: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.bluenotenetworks.common.management.sm.User#3102] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:372) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:128) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:839) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) at org.hibernate.collection.PersistentSet.initializeFromCache(PersistentSet.java:101) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1705) (continues on) I stepped through the code in the debugger and can see that the object's ID (3102 in this case) remains in the cached collection even after the deletion. -- 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

16 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3075) Should be possible to register UserTypes for known property types (classes) in configuration

by Martin Probst (JIRA)

Should be possible to register UserTypes for known property types (classes) in configuration -------------------------------------------------------------------------------------------- Key: HHH-3075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3075 Project: Hibernate3 Issue Type: Improvement Components: core Environment: n/a Reporter: Martin Probst Priority: Minor Currently, when persisting primitive properties of a class that are not known to Hibernate, there are only cumbersome ways to tell Hibernate that a certain UserType should be used. Good example is Joda Time: <pre> @Entity class MyClass { org.joda.time.DateTime foo; } </pre> .. which will result in ugly binary fields in database. Next try: <pre> @Entity class MyClass { @Type(type = "org.joda.time.contrib.hibernate.PersistentDateTime") org.joda.time.DateTime foo; } </pre> That works, but now I have to specify that on all time fields of all classes. Plus it's different types for different classes, which makes it more messy. And it's simply a string in code, so it's fragile to refactoring, code move, etc. TypeDefs allow a shorter handle for certain types, but don't really address the refactoring issues. A better way might be to allow configurations to register UserTypes for known classes. E.g. have a configuration directive like this: <mappable-type class="org.joda.time.DateTime" usertype="org.joda.time.hibernate.DateTimeType"/> This would allow the classes to stay clean from type mappings and reduce coupling between domain objects and persistence mapping. This might be as easy as allowing the org.hibernate.type.TypeFactory map to be extended at configuration time. -- 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

16 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5004) Specifying entity access type at class level and then redundantly again on id field or getId() causes EntityManagerFactory configuration failure

by Jesse Hutton (JIRA)

Specifying entity access type at class level and then redundantly again on id field or getId() causes EntityManagerFactory configuration failure ------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5004 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5004 Project: Hibernate Core Issue Type: Bug Components: annotations, entity-manager Affects Versions: 3.5.0-CR-2 Environment: I'm developing on Fedora 12 64bit version. java version: Java(TM) SE Runtime Environment (build 1.6.0_18-b07) Reporter: Jesse Hutton Priority: Minor Attachments: testHibernate.tar.gz If you annotation an entity class with @Access and either AccessType.FIELD or AccessType.PROPERTY and then repeat the same respective access annotation for identifier of the class, hibernate will not be able to find the identifier. An example stack trace is: javax.persistence.PersistenceException: [PersistenceUnit: testhibernate] Unable to configure EntityManagerFactory ... Caused by: org.hibernate.AnnotationException: No identifier specified for entity: com.mycompany.testhibernate.Foo ... To annotate a class as such is clearly redundant, but it doesn't seem like it should really cause this error. I happened to have discovered it while experimenting with different access type options in JPA 2 using EclipseLink, forgetting to remove an access type annotation to the getId() method of my entity, and then eventually switching JPA providers to Hibernate. Under EclipseLink, there was no problem with the redundant annotations. Attached is a sample test app illustrating the problem. It has access PROPERTY specified, but the error occurs with FIELD just the same. -- 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

16 years, 1 month

4
6
0 / 0

[Hibernate-JIRA] Created: (HV-293) Annotation processor fails in Eclipse when evaluating custom constraints not defined in the current project

by Gunnar Morling (JIRA)

Annotation processor fails in Eclipse when evaluating custom constraints not defined in the current project ----------------------------------------------------------------------------------------------------------- Key: HV-293 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-293 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0-Beta-1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik In certain situations the AP fails when being integrated in Eclipse with the following exception: java.lang.AssertionError: Class org.hibernate.validator.constraints.impl.LengthValidator specified in @Constraint.validatedBy doesn't implement ConstraintValidator. at org.hibernate.validator.ap.util.ConstraintHelper.getConstraintValidatorSuperType(ConstraintHelper.java:497) at org.hibernate.validator.ap.util.ConstraintHelper.getSupportedType(ConstraintHelper.java:426) at org.hibernate.validator.ap.util.ConstraintHelper.getSupportedTypes(ConstraintHelper.java:402) at org.hibernate.validator.ap.util.ConstraintHelper.checkCustomConstraint(ConstraintHelper.java:356) at org.hibernate.validator.ap.util.ConstraintHelper.checkConstraint(ConstraintHelper.java:295) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.checkConstraintAtField(ConstraintAnnotationVisitor.java:290) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.visitVariableAsField(ConstraintAnnotationVisitor.java:174) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.visitVariableAsField(ConstraintAnnotationVisitor.java:45) at javax.lang.model.util.ElementKindVisitor6.visitVariable(ElementKindVisitor6.java:199) at org.eclipse.jdt.internal.compiler.apt.model.VariableElementImpl.accept(VariableElementImpl.java:55) at org.hibernate.validator.ap.ConstraintValidationProcessor.process(ConstraintValidationProcessor.java:84) at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.handleProcessor(RoundDispatcher.java:139) at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.round(RoundDispatcher.java:121) at org.eclipse.jdt.internal.compiler.apt.dispatch.BaseAnnotationProcessorManager.processAnnotations(BaseAnnotationProcessorManager.java:159) at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:134) at org.eclipse.jdt.internal.compiler.Compiler.processAnnotations(Compiler.java:810) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:428) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:364) at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.compile(IncrementalImageBuilder.java:321) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:301) at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.build(IncrementalImageBuilder.java:134) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildDeltas(JavaBuilder.java:265) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:193) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) This happens, if the AP examines a constraint annotation, which is not defined in the currently built project itself, but is imported from some other JAR (e.g. @Length from HV): public class TestModel { @Length private String test; } The problem occurs, regardless whether the JAR containing the constraint is on the AP classpath or not. The AP works as expected when running on javac. -- 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

16 years, 1 month

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4436) Stackoverflow exception if Composite id has many to one relationship and fetchMode = EAGER

by Kirill Trofimov (JIRA)

Stackoverflow exception if Composite id has many to one relationship and fetchMode = EAGER ------------------------------------------------------------------------------------------ Key: HHH-4436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4436 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: hibernate-core: 3.3.0.SP1, hibernate-annotations: 3.4.0.GA Reporter: Kirill Trofimov Attachments: hibernatetest.zip Stackoverflow occurred if composite id has many to one relationshipt. See unit test in attached file. -- 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

16 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4868) Upgrade to Javassist 3.11.GA

by Julien Kronegg (JIRA)

Upgrade to Javassist 3.11.GA ---------------------------- Key: HHH-4868 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4868 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.5.0-Beta-4, 3.3.2, 3.3.1 Reporter: Julien Kronegg Priority: Minor Hibernate 3.3.1 uses Javassist 3.4.GA (3.5 years old) Hibernate 3.3.2 uses Javassist 3.9.GA (1.5 years old) Hibernate 3.5.0 uses Javassist 3.9.GA (1.5 years old) -- 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

16 years, 1 month

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4738) getSingleResult returning SQLException in DerbyDialect

by Samuel Halliday (JIRA)

getSingleResult returning SQLException in DerbyDialect ------------------------------------------------------ Key: HHH-4738 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4738 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.5.0-Beta-2 Environment: hibernate 3.5.0-0.2, Glassfish v3, Derby Reporter: Samuel Halliday I am encountering problems when issuing getSingleResult queries using the Glassfish v3 "hibernate 3.5.0-0.2". These queries work fine if I use hibernate 3.3.1.GA, or a PostgreSQL backend/dialect. Something between 3.3.1 and 3.5 has therefore introduced this bug. The queries are along the lines of [code] Query q = em.createQuery("SELECT COUNT(s) FROM MyTable s"); Long result = (Long) q.getSingleResult(); [/code] and [code] Query query = em.createQuery("SELECT s FROM MyTable s ORDER BY s.id"); query.setFirstResult(id); query.setMaxResults(1); MyTable random = (MyTable) query.getSingleResult(); [/code] The exception I am seeing is below, when used with (at least) the Java Derby DB. The message is "The column position '1' is out of range. The number of columns for this ResultSet is '0'." [code] Caused by: java.sql.SQLException: The column position '1' is out of range. The number of columns for this ResultSet is '0'. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) at org.apache.derby.client.am.ColumnMetaData.getColumnType(Unknown Source) at org.apache.derby.client.am.PreparedStatement.setInt(Unknown Source) at org.hibernate.loader.Loader.bindLimitParameters(Loader.java:1669) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1594) at org.hibernate.loader.Loader.doQuery(Loader.java:694) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:257) at org.hibernate.loader.Loader.doList(Loader.java:2232) ... 42 more Caused by: org.apache.derby.client.am.SqlException: The column position '1' is out of range. The number of columns for this ResultSet is '0'. at org.apache.derby.client.am.ColumnMetaData.checkForValidColumnIndex(Unknown Source) ... 49 more [/code] -- 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

16 years, 1 month

4
7
0 / 0

[Hibernate-JIRA] Created: (HCANN-21) EnumType speed up in initEnumValues()

by Ondrej Medek (JIRA)

EnumType speed up in initEnumValues() ------------------------------------- Key: HCANN-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-21 Project: Hibernate Commons Annotations Issue Type: Patch Affects Versions: 3.1.0.GA, 3.2.x Environment: Hibernate 3.5.1, Sun JDK 1.6.0_18 Reporter: Ondrej Medek Priority: Minor Attachments: EnumType.java.patch Hi, I have simplified and sped up the method EnumType.initEnumValues(). See the attached patch. Tested on Sun JDK 1.6.0_18 Note 1: I do not know, why the author (Emmanuel Bernard?) has used reflection. Maybe the method Class.getEnumConstants() in not implemented by other JREs (IBM, BEA) or he just didn't know this method.? Note: the method getEnumConstants() in SUN JRE does use the reflection to look for method "values()", too, but it's results are cached, so the second call to the getEnumConstants() is fast. And because the results are cached inside the Enum class itself, it does not cause any memory leaks like HHH-4317. -- 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

16 years, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2645) Synchronization bottleneck in EntityModeToTuplizerMapping

by Erik Bergersjö (JIRA)

Synchronization bottleneck in EntityModeToTuplizerMapping --------------------------------------------------------- Key: HHH-2645 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2645 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.4.sp1, 3.2.4, 3.2.3 Environment: Hibernate 3.2.3 (and later), Sun's JDK 1.4.2_12 (server VM) on SunOS 5.10, Oracle 10g R2 Reporter: Erik Bergersjö Priority: Minor We have had a major performance bottleneck in EntityModeToTuplizerMapping with Hibernate version 3.2.3 and the code for that class in 3.2.4sp1 is unchanged. We have found a solution that solves the issue and would like to get it into the real version. I submitted to the user forum first and was asked to create a JIRA issue. The problematic line is: private final Map tuplizers = Collections.synchronizedMap( new SequencedHashMap() ); We have changed it to (using util.concurrent): private final Map tuplizers = new EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap(); This change alone makes our use cases six times faster. The difference is that ConcurrentReaderHashMap handles concurrent readers much better, they don't have to wait for each other. The problem occurs when a high number of threads try to initialize sets (see mapping below). A thread dump showed a high number of threads waiting for the same monitor, see partial stack trace below. The code runs on Sun's JDK 1.4.2_12 (server VM) on SunOS 5.10 and the kernel spends a lot of time handling mutexes with the original implementation. That time disappears from the radar screen with the fixed version. Example mapping for set: [code] <set name="lines" lazy="true" inverse="true" cascade="all-delete-orphan"> <key> <column name="col1" not-null="true" /> <column name="col2" not-null="true" /> </key> <one-to-many class="LineClass" /> </set> [/code] Stack trace (partial): "Thread-108" prio=5 tid=0x05852e90 nid=0x103 waiting for monitor entry [0x3ed7e000..0x3ed7fc28] at java.util.Collections$SynchronizedMap.get(Collections.java:1942) - waiting to lock <0x89d30788> (a java.util.Collections$SynchronizedMap) at org.hibernate.tuple.EntityModeToTuplizerMapping.getTuplizerOrNull(EntityModeToTuplizerMapping.java:53) at org.hibernate.tuple.EntityModeToTuplizerMapping.getTuplizer(EntityModeToTuplizerMapping.java:66) at org.hibernate.type.ComponentType.getPropertyValues(ComponentType.java:353) at org.hibernate.type.ComponentType.isEqual(ComponentType.java:141) at org.hibernate.engine.CollectionKey.equals(CollectionKey.java:50) at java.util.HashMap.eq(HashMap.java:274) at java.util.HashMap.get(HashMap.java:323) at org.hibernate.engine.loading.CollectionLoadContext.getLocalLoadingCollectionEntry(CollectionLoadContext.java:163) at org.hibernate.engine.loading.CollectionLoadContext.locateLoadingCollectionEntry(CollectionLoadContext.java:150) at org.hibernate.engine.loading.CollectionLoadContext.getLoadingCollection(CollectionLoadContext.java:92) at org.hibernate.loader.Loader.readCollectionElement(Loader.java:1003) at org.hibernate.loader.Loader.readCollectionElements(Loader.java:646) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:591) at org.hibernate.loader.Loader.doQuery(Loader.java:701) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.loadCollection(Loader.java:1994) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:565) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) at org.hibernate.collection.PersistentSet.iterator(PersistentSet.java:163) -- 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

16 years, 1 month

8
28
0 / 0

[Hibernate-JIRA] Created: (HHH-3050) Convert usage of Hibernate's FastHashMap to ConcurrentHashMap (Java 1.5)

by Gail Badner (JIRA)

Convert usage of Hibernate's FastHashMap to ConcurrentHashMap (Java 1.5) ------------------------------------------------------------------------ Key: HHH-3050 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3050 Project: Hibernate3 Issue Type: Improvement Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.3 The performance test attached to HHH-2645 shows that java.util.concurrent.ConcurrentHashMap (introduced in Java 1.5) performs nearly as well as org.hibernate.util.FastHashMap. Hibernate needs to move to Java 1.5 before this can be done. As noted in HHH-2645, it might be worthwhile to convert usages of FastHashMap to ConcurrentHashMap so that FastHashMap does not need to be maintained. -- 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

16 years, 1 month

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5005) Column name not prefixed with table name alias

by Jeremy Hindmarsh (JIRA)

Column name not prefixed with table name alias ---------------------------------------------- Key: HHH-5005 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5005 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5 CR2, Oracle 10g Reporter: Jeremy Hindmarsh If a column name annotation contains a full stop, the column name is not prefixed with the table name alias. Some of our database tables contain Oracle spatial data. One in particular has two columns for longitude and latitude, GEOM.SDO_POINT.X and GEOM.SDO_POINT.Y The problem is that the table alias is not added to the column name due to isIdentifier method in the Template class. This method returns false because the column name contains full stops. This means the renderWhereStringTemplate method doesn't prefix the column name with the table alias placeholder. Fortunately for now I can use the following column definition, in order to get the table alias added. @Column(name = "$PlaceHolder$.GEOM.SDO_POINT.X") -- 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

16 years, 2 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4786) SerializableType + custom Serializable class + L2 cache causes problems

by Steve Ebersole (JIRA)

SerializableType + custom Serializable class + L2 cache causes problems ----------------------------------------------------------------------- Key: HHH-4786 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4786 Project: Hibernate Core Issue Type: Bug Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Beta-3 The changes done for HHH-2990 cause an issue when users map non-JDK Serializable classes using SerializableType in combination with attempting to cache those values into second level cache. SerializableType reports the classloader to use for deserialization as the classloader of java.io.Serializable (which is generally null indicating the "bootstrap class loader"). However that classloader will (generally) not have visibility into the classloader needed to see these non-JDK classes. -- 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

16 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-820) TypeDef does not work when used on @Embeddable or @MappedSuperClass classes.

by Ted Bergeron (JIRA)

TypeDef does not work when used on @Embeddable or @MappedSuperClass classes. ---------------------------------------------------------------------------- Key: ANN-820 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-820 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Oracle 11, hibernate 3.4.0 GA Reporter: Ted Bergeron @TypeDefs({ @TypeDef( name = "status", typeClass = EnumUserType.class, parameters = {@Parameter(name = "enumClass", value = "com.acme.common.model.Status")} ) }) I declare various @TypeDefs such as this. They all work fine when used in @Entity classes. When used in a @MappedSuperclass, or an @Embeddable, they fail. I see from the docs that these are global and double checked that I do not have any duplicate @TypeDef definitions. -- 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

16 years, 2 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HV-298) Add a section on using the annotation processor to the HV reference guide

by Gunnar Morling (JIRA)

Add a section on using the annotation processor to the HV reference guide ------------------------------------------------------------------------- Key: HV-298 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-298 Project: Hibernate Validator Issue Type: Improvement Components: documentation Affects Versions: 4.1.0-Beta-1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik A section describing the annotation processor should be added to the HV reference guide. It should cover the following: * Features of the AP * Options that control the AP's behavior * Integrating the AP into the build process: * Plain javac * Maven/Ant * IDE builds -- 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

16 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-168) Add the ability to disable automatic indexing both on a per index level and programmatically

by Eric Winter (JIRA)

Add the ability to disable automatic indexing both on a per index level and programmatically -------------------------------------------------------------------------------------------- Key: HSEARCH-168 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-168 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Eric Winter Priority: Minor It is very resticitive in an application that has multiple indexes to only allow the disabling of automatic indexing on an application wide level (or at least SessionFactory wide...). I can see it being very useful to have auto indexing on a per index basis. Also, it would be nice to be able to turn auto indexing off and on programmatically using something like Search.setAutoIndexing("myIndex", false); //per index and Search.setAutoIndexing(false); //global -- 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

16 years, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-846) Infinite loop occurs while doing findById on a Parent domain Object having OneToMany relationship with child domain with composite primary key

by RAMESH BABU NL (JIRA)

Infinite loop occurs while doing findById on a Parent domain Object having OneToMany relationship with child domain with composite primary key ---------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-846 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-846 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Environment: Hibernate Annotations 3.4.0.GA, HSqlDB and Oracle Reporter: RAMESH BABU NL Attachments: Organization.java, OrganizationApplications.java, OrganizationApplicationsPK.java We are using Hibernate annotations version 3.4.0.G.A We are establishing a OneToMany relationship using the annotation @OnetoMany for a Parent and Child domain objects where the child domain has a composite primary key. We have two domain objects Organization [Parent] OrganizationApplications [Child] We want to have a OnetoMany relationship between Organization and OrganizationApplications. As shown below OrganizationApplications contains a composite primary key, of two columns(Organization Id, ApplicationId[foreignkey from other table called APPLICATIONS]) Organizations.java ------------------- @OneToMany(targetEntity=gov.osc.enrollment.backend.domain.OrganizationApplications.class, cascade=CascadeType.ALL, fetch = FetchType.EAGER, mappedBy="id.organization") private Set<OrganizationApplications> organizationApps = new HashSet<OrganizationApplications>(); OrganizationApplications.java --------------------------------------------------------------------- public class OrganizationApplications extends EnvelopeInfo implements Serializable { private static final long serialVersionUID = 1L; @EmbeddedId private OrganizationApplicationsPK id; public OrganizationApplicationsPK getId() { return id; } public void setId(OrganizationApplicationsPK id) { this.id = id; } OrganizationApplicationsPK.java --------------------------------------------------------------------- @Embeddable public class OrganizationApplicationsPK implements Serializable { private static final Long serialVersionUID = 1L; public OrganizationApplicationsPK() { super(); } @ManyToOne @JoinColumn(name="APPLICATION_ID",nullable=false) private Applications application; @ManyToOne(targetEntity=gov.osc.enrollment.backend.domain.Organization.class, cascade=CascadeType.ALL) @JoinColumn(name="ORGANIZATION_ID", referencedColumnName="ORGANIZATION_ID", nullable=false, insertable=true, updatable=true) private Organization organization; public Applications getApplication() { return application; } public void setApplication(Applications application) { this.application = application; } public Organization getOrganization() { return organization; } public void setOrganization(Organization organization) { this.organization = organization; } @Override public boolean equals(Object o) { if (o == this) { return true; } if ( ! (o instanceof OrganizationApplicationsPK)) { return false; } OrganizationApplicationsPK other = (OrganizationApplicationsPK) o; return (this.getOrganization().getId() == other.getOrganization().getId()) && (this.getApplication().getId() == other.getApplication().getId()); } @Override public int hashCode() { final int prime = 31; int hash = 17; hash = hash * prime + ((int) (this.getOrganization().getId() ^ (this.getOrganization().getId() >>> 32))); hash = hash * prime + ((int) (this.getApplication().getId() ^ (this.getApplication().getId() >>> 32))); return hash; } } Please see the attached java files for complete code and also the exception stack trace. Questions: 1. When we do a findById query on Organization table the system goes into infinite loop and never gets out . How ever we are able to insert a record in Organization and its child OrganizationApplications. 2. In the Organization.java domain, if you notice we are using mappedby="id.organization". Is this a valid mapping ? If not why does this parameter work for insert and not for a entityManager.findById, doing so leads to infinite loop. -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5135) Prefix is missed in HQL query for property mapped to column 'TO_DATE' on Oracle 10g

by Vladimir Ivanov (JIRA)

Prefix is missed in HQL query for property mapped to column 'TO_DATE' on Oracle 10g ----------------------------------------------------------------------------------- Key: HHH-5135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5135 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.0-Final Environment: Hibernate 3.5.1, Oracle 10.2.0.1.0 Reporter: Vladimir Ivanov Attachments: test_case.zip I have entity 'Period' with property 'toDate' mapped to database column with name 'TO_DATE' (Our database is Oracle 10g). When this entity is queried via HQL, prefix for this entity is missed. Following SQL query is produced: Hibernate: /* from Period p */ select * from ( select period0_.ID as ID44_, period0_.TXN_VER as TXN3_44_, period0_.FROM_DATE as FROM4_44_, TO_DATE as TO5_44_, period0_.POSITION_MONTH as POSITION7_44_, period0_.IS_CLOSE as IS12_44_, period0_.IS_OPEN as IS13_44_, period0_.DISC_TYPE as DISC2_44_ from SOME_SCHEMA.T_PERIOD period0_ ) where rownum <= ? This leads to database error in case of more advanced query (with joins etc). For example, we have following error in production: java.sql.SQLException: ORA-00918: column ambiguously defined Probably the reason of this behaviour is that Hibernate tries to interpret 'TO_DATE' as the name of SQL function. In Hibernate 3.3.2.GA prefix is added correctly. Domain object, DAO, Test and Hibernate configuration are in the attachment. I used Spring framework to configure test. -- 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

16 years, 2 months

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5063) Projections that have aliases same as the property name result in invalid sql

by Shawn Clowater (JIRA)

Projections that have aliases same as the property name result in invalid sql ----------------------------------------------------------------------------- Key: HHH-5063 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5063 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.0-Final Reporter: Shawn Clowater I have a criteria query that is using an AliasToBeanTransformer that I'm using to selectively populate some of the properties. It appears that the transformer requires the alias values to match the properties of your bean so that it can call the setters via reflection. The code snippet is similar to the following return (List<DataProvider>) session.createCriteria(DataProvider.class) .setProjection(Projections.projectionList() .add(Projections.property("dataProviderId), "dataProviderId") .add(Projections.property("uuid"), "uuid") .add(Projections.property("name"), "name") .add(Projections.property("dataProviderGroup"), "dataProviderGroup") .add(Projections.property("verifiedFlg"), "verifiedFlg") ) .setResultTransformer(new AliasToBeanResultTransformer(DataProvider.class)) .addOrder(Order.asc("name")) .list(); And is resulting in the following SQL select y0_ as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER this_ order by y2_ asc I can assure you that my column names are not y0_, etc. This worked in 3.3.2 and I am suspecting it might be due to the change for HHH-1088. If I don't specify the alias or even change the value then it will produce a valid query it just won't populate by bean correctly. i.e. if I append anything to the end of the first alias (i.e. "hi") results in: select this_.DATA_PROVIDER_ID as y0_, y1_ as y1_, y2_ as y2_, y3_ as y3_, y4_ as y4_ from DATA_PROVIDER this_ order by y2_ asc -- 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

16 years, 2 months

4
12
0 / 0

[Hibernate-JIRA] Created: (METAGEN-26) Update readme.txt

by Hardy Ferentschik (JIRA)

Update readme.txt ----------------- Key: METAGEN-26 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-26 Project: Hibernate StaticMetamodel Generator Issue Type: Task Components: documentation Affects Versions: 1.0.0-CR-1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.0.0 -- 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

16 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3884) NPE with mutable Natuarl Id's

by Michael Kopp (JIRA)

NPE with mutable Natuarl Id's ----------------------------- Key: HHH-3884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3884 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Michael Kopp When saving an entity with a mutable natural id hibernate throws the following NPE. java.lang.NullPointerException at org.hibernate.engine.StatefulPersistenceContext.getNaturalIdSnapshot(StatefulPersistenceContext.java:267) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:78) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:162) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:113) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) I checked the code and found the reason: - getNaturalIdSnapshot calls getDatabaseSnapshot and checks the result for NO_ROW but not for null - getDatabaseSnapshot will never return NO_ROW but null if nothing was found hence getNaturalIdSnapshot will produce a NPE if the entity is not in the database already. the fix is simple: change: Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == NO_ROW ) { return null; } to Object[] entitySnapshot = getDatabaseSnapshot( id, persister ); if ( entitySnapshot == null ) { return null; } This is still there in trunk as well! -- 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

16 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4971) Findbugs Warnings

by Marco Tulio Valente (JIRA)

Findbugs Warnings ----------------- Key: HHH-4971 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4971 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Reporter: Marco Tulio Valente Priority: Minor Dear all, We are conducting a study about the relevance of the warnings reported by the FindBugs tool when executed over several open-source systems. Particularly, in the case of Hibernate, we would like to confirm the relevance of the following warning reported by the tool (for version 3.5.0.beta1): Location: org.hibernate.engine.StatefulPersistenceContext getNaturalIdSnapshot - Line: 298 Warning: Using pointer equality to compare different types. The method uses using pointer equality to compare two references that seem to be of different types. The result of this comparison will always be false at runtime. Since this warning seemed relevant to us, we would like to confirm our classification with Hibernate's developers. Best regards, Marco Tulio Valente Brazil -- 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

16 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3068) Update of an entity with immutable natural-id and many-to-one relation seems to fail

by Pascal Cohen (JIRA)

Update of an entity with immutable natural-id and many-to-one relation seems to fail ------------------------------------------------------------------------------------ Key: HHH-3068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3068 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Linux Fedora 32bits Postgres 8.2.5 Reporter: Pascal Cohen Priority: Minor I have posted in the forum the following question and someone seems to confirm this might be a bug. http://forum.hibernate.org/viewtopic.php?t=982385&highlight= Thanks in advance for advice -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2041) Update with unaltered natural-id fails

by Jim Pease (JIRA)

Update with unaltered natural-id fails -------------------------------------- Key: HHH-2041 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2041 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: hibernate-3.1.3, mysql-4.1.12 Reporter: Jim Pease This may be a duplicate of http://opensource.atlassian.com/projects/hibernate/browse/HHH-1574. Getting following error: caused by: org.hibernate.HibernateException: immutable natural identifier of an instance of edu.syr.lsb.gmt.impl.LinkImpl was altered at org.hibernate.event.def.DefaultFlushEntityEventListener.checkNaturalId(DefaultFlushEntityEventListener.java:80) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:155) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:106) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) ... This is occurring without modifications to the natural identifier, which is mapped as follows: <natural-id> <property name="activityRef" column="ACTIVITY_REF" length="255" not-null="true" /> <many-to-one name="goal" class="GoalImpl" column="GOAL_ID" not-null="true" cascade="none" /> </natural-id> -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3256) OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)

by Tom Muldoon (JIRA)

OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart) -------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3256 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, MySQL 5 Reporter: Tom Muldoon After a JBoss restart, the in-memory hiValue is -1. As such, the callback.getNextValue( ) method is invoked twice. With an increment size of 50 and a current database next_val of 10000, the PooledOptimizer.generate method returns a value of 10000 (as expected) and sets the in memory hiValue to 10050 (also as expected), however, it sets the db next_val to 10100. Shouldn't the db next_val be kept in sync with the in-memory hiValue (i.e. 10050)? -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5053) Duplicate primary keys when using the SEQUENCE strategy due to underlying sequence not being updated when the SequenceGenerator's allocatedSize is greater than 1

by atomicknight (JIRA)

Duplicate primary keys when using the SEQUENCE strategy due to underlying sequence not being updated when the SequenceGenerator's allocatedSize is greater than 1 ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5053 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2 PostgreSQL 8.4.1 (JDBC driver 8.4-701 JDBC4) Glassfish v3 (build 74.2) JDK 1.6.0_18 Reporter: atomicknight Attachments: jpa-test.war, table1.sql When the SequenceGenerator's allocatedSize is greater than 1, the underlying sequence associated with the table doesn't ever seem to be updated by Hibernate except on application startup. The test case uses an allocatedSize of 3, corresponding to an increment value of 3 in the underlying sequence. Here's how to use the test case (requires EJB 3.1): 1) Set up the database using the attached SQL dump, then load the application 2) Access the test page via http://localhost:8080/jpa-test/test. You should see a page with the word "Done!" 3) Undeploy and redeploy the application 4) Access the test page again. You should encounter an error page indicating that the transaction was aborted. Here's what I observed at the database level while following the above steps: 1) Sequence is created with a start value of 1 and increment value of 3. 2) Hibernate increments the sequence to 4. The application then inserts rows with IDs 12-31. 3) No change - the sequence still has a value of 4. 4) Hibernate increments the sequence to 7. The application attempts to insert a row with ID 21, but fails because the ID was already used in step 2. Setting the SequenceGenerator's allocatedSize to 1 as well as changing the increment value of the sequence to 1 gives the correct behavior. -- 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

16 years, 2 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-324) @DynamicBoost(BoostStrategy.class)

by Emmanuel Bernard (JIRA)

@DynamicBoost(BoostStrategy.class) ---------------------------------- Key: HSEARCH-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-324 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.1, 3.2.0 This sounds like an interesting feature. We could do something very similar to the new AnalyzerDiscriminator approach. The use case is explained http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... Need some analysis before the jump We can do that in 3.1.1, but no hard pressure. -- 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

16 years, 2 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4065) Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed

by Nicklas Nordborg (JIRA)

Incorrect SQL is used for HQL if the number of values for a filter collection parameter is changed -------------------------------------------------------------------------------------------------- Key: HHH-4065 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4065 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Hibernate 3.3.2 Reporter: Nicklas Nordborg Attachments: trace.txt I think that maybe the fix for HHH-530 has introduced a problem with filters that has a collection-type parameter. If the number of parameters in that collection changes during the lifetime of a SessionFactory the SQL that is used becomes incorrect and either has too many or too few parameter placeholders (eg. '?') in the SQL. There was no problem in Hibernate 3.3.1. A typical error message is: java.sql.SQLException: Parameter index out of bounds. 2 is not between valid values of 1 and 1 Below is some pseudo-code that shows what happens when the number of values in a collection is increased from 1 to 2. The 'memberOf' is a simple filter on the `id` column: `id` IN (:items) String hql = "select n from NewsData n"; List idList = new ArrayList(); idList.add(1); Session s = .... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // SQL: select .... `News` newsdata0_ where newsdata0_.`id` IN (?) s.close(); idList.add(2); s = ... // create new session s.enableFilter("memberOf").setParameterList("items", idList); s.createQuery(hql).list(); // <--- error here with 3.3.2 but works with 3.3.1 // SQL (3.3.2): select .... `News` newsdata0_ where newsdata0_.`id` IN (?) // SQL (3.3.1): select .... `News` newsdata0_ where newsdata0_.`id` IN (?, ?) I am attaching a file with TRACE-level output from both Hibernate 3.3.2 and 3.3.1. The relevant difference seems to be that in Hibernate 3.3.2 the query plan is cached with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (?)' but in Hibernate 3.3.1 with: [SQL_TOKEN] SqlFragment: 'newsdata0_.`id` IN (:memberOf.items)' -- 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

16 years, 2 months

5
14
0 / 0

[Hibernate-JIRA] Created: (HV-305) JPATraversableResolver tries to access properties that do not exist

by Stephan Bublava (JIRA)

JPATraversableResolver tries to access properties that do not exist ------------------------------------------------------------------- Key: HV-305 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-305 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0.Beta1 Environment: Hibernate Validator 4.1.0.Beta1, Hibernate 3.5.0-Final Reporter: Stephan Bublava Assignee: Hardy Ferentschik Attachments: validation-test.zip Prerequisites: - two entities that model a bidirectional 1:n relationship - both have class-level constraints - the collection that represent the n-side of the relationship is annotated @Valid - Hibernate 3.5 is in the class path In this case, validation of the entity that represents the 1-side fails, because JPATraversableResolver attempts to access a property that doesn't exist. (It looks for the collection in the wrong entity.) Changing any of the last three conditions makes the problem disappear... I've attached a test-cases that demonstrates this issue in more detail. -- 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

16 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5030) BaseRegionAdapter shouldn't rely on optional Cache#toMap method

by Adrian Hummel (JIRA)

BaseRegionAdapter shouldn't rely on optional Cache#toMap method --------------------------------------------------------------- Key: HHH-5030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5030 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-CR-2 Environment: hibernate-oscache 3.5.0.Beta-1 Reporter: Adrian Hummel Attachments: bugreport.zip Get an {{UnsupportedOperationException}} when checking the L2 cache if it contains an entity: {code} emf.getCache().contains(MyEntity.class, pk); {code} Result: {code} java.lang.UnsupportedOperationException at org.hibernate.cache.OSCache.toMap(OSCache.java:126) at org.hibernate.cache.impl.bridge.BaseRegionAdapter.contains(BaseRegionAdapter.java:62) at org.hibernate.impl.SessionFactoryImpl$CacheImpl.containsEntity(SessionFactoryImpl.java:967) at org.hibernate.impl.SessionFactoryImpl$CacheImpl.containsEntity(SessionFactoryImpl.java:962) at org.hibernate.ejb.EntityManagerFactoryImpl$JPACache.contains(EntityManagerFactoryImpl.java:164) ... {code} The {{Cache#toMap}} method is optional (according to Javadoc), thus, {{BaseRegionAdapter}} shouldn't rely on this method. -- 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

16 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5121) Using Oracle analytical functions causes QuerySyntaxException

by Tarek Nabil (JIRA)

Using Oracle analytical functions causes QuerySyntaxException ------------------------------------------------------------- Key: HHH-5121 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5121 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: Hibernate 3.5.0-Final. Oracle 10g. Reporter: Tarek Nabil Attachments: criteria-bug.zip The CriteriaBuilder.function() method allows the creation of an expression which is supported by the target DB such as DB functions. Using this facility to call Oracle 10g (and above) analytical functions such as "COUNT(*) OVER()" produces a QuerySyntaxException. The attached test case illustrates the problem. It's a minimal Maven2 project which contains one domain class and one DAO. The domain class maps to the REGION entity from the Oracle HR schema which ships with any Oracle XE installation. I still included the script needed to create the table incase the schema is not available on the test environment. The DAO has two methods, one selects all the regions and the other attempts to select all the regions and the count of records returned using "COUNT(*) OVER()". A test class is used to test those two methods; the first test works successfully; the second gives the stack trace provided in "stack-trace.txt". I believe this bug is a major one because: 1- To get the total count of records, the only other option is to do two queries which is a lot more expensive. 2- The count is required for pagination of results which is essential for search screens. 3- Search screens which require dynamic queries are the main reason one would use criteria in the first place. I've provided instructions on the changes required to setup the Maven project in order to run the test case, which are minimal, in "readme.txt". -- 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

16 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5170) Used unsaved-value="any" for <composite-id>, Getting exception Object references an unsaved transient instance - save the transient instance before flushing, even though record exist in the DB

by Deepesh Seetharaman (JIRA)

Used unsaved-value="any" for <composite-id>, Getting exception Object references an unsaved transient instance - save the transient instance before flushing, even though record exist in the DB ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5170 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5170 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: DB2-z Series, Weblogic 10.3 App Server. Reporter: Deepesh Seetharaman Attachments: EventService.hbm.xml, State.hbm.xml, test.zip I have attached the following files. i)EventService.hbm.xml ii)State.hbm.xml While I am trying to persist, EventService, by setting the State object, with only its id fields its giving the folloiwing exception. org.springframework.dao.InvalidDataAccessApiUsageException: object references an unsaved transient instance - save the transient instance before flushing: com.fareis.las.css.sys.rf.domain.State; nested exception is org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: com.fareis.las.css.sys.rf.domain.State Caused by: org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: com.fareis.las.css.sys.rf.domain.State at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:219) at org.hibernate.type.EntityType.getIdentifier(EntityType.java:397) at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:242) at org.hibernate.type.TypeFactory.findDirty(TypeFactory.java:576) at org.hibernate.persister.entity.AbstractEntityPersister.findDirty(AbstractEntityPersister.java:3121) at org.hibernate.event.def.DefaultFlushEntityEventListener.dirtyCheck(DefaultFlushEntityEventListener.java:472) at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:197) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.springframework.orm.hibernate3.HibernateTemplate$29.doInHibernate(HibernateTemplate.java:849) at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:372) at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:840) at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:836) at com.fareis.core.pf.repository.hibernate.GenericHibernateRepository.findByProperty(GenericHibernateRepository.java:417) at com.fareis.las.prc.clb.el.repository.hibernate.EventHibernateRepository.findByClientBillingEventKey(EventHibernateRepository.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy1.findByClientBillingEventKey(Unknown Source) at com.fareis.prc.clb.repository.test.BillableEventRepositoryTestCase.testAddEvent(BillableEventRepositoryTestCase.java:83) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:69) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) I am creating the instance like this. EventService service = new EventService(); State state = new State(); StateId id = new StateId(); id.setStateCode("DAS"); Country country = new Country(); country.setCountryCode("US"); id.setCountryCode(country); state.setId(id); service.setBillingId(10); service.setStatusCode("A"); service.setState(state); service.setClientBillingEventKey(clientBillingEvent); service.setLastUpdateSourceId("TEST"); service.setLastUpdateTimestamp(new java.util.Date()); service.setLastUpdateUserId("sdeepesh"); service.setCorrDate(new Date(System.currentTimeMillis())); service.set ... other not-null fields. State.hbm.xml's <id property is using unsaved-value="any", if you remove that attribute everything works fine, but it will fire a SELECT SQL to the STATE table, to verify the integrity of the <id>. We had explicitly mentioned the unsaved-value="any", in order to prevent the SELECT being fired. Ironicall I found out that when you make unsaved-value="none", everything works perfectly, but then unsaved-value is having this unpredictable behaviour about it's value. We are using unsaved-value attribute for all <id, <composite-id which has <generated-class as "assigned", the values are like below <id unsaved-value="id_value" - id is a String <id unsaved-value="none" - id is a Integer <composite-id unsaved-value="any" For composite-id everywhere we used, unsaved-value="any", the only contradicting place where we found is with State.hbm.xml If possible please provide some guidelines as to use the "unsaved-value", we mainly used that to prevent the SELECT SQLs from executing before performing INSERT. Also while debugging through the hibernate code, I found that it is performing dirtyCheck for EventService instance, where it compares loaded value and current value. I found that loaded value was having State object as null. Please provde your comments. I have also attached the test cases, but you wont able to run it, due to compilation problems, testAddEvent is the one which is failing -- 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

16 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5164) HQL putting quotes around SMALLINT field

by Shawn Kuenzler (JIRA)

HQL putting quotes around SMALLINT field ---------------------------------------- Key: HHH-5164 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5164 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 using org.hibernate.dialect.DB2Dialect against DB2 v9.1 Reporter: Shawn Kuenzler HQL query generating a WHERE clause with a mapped column of java type "int" and datatype "SMALLINT" in DB2. The generated prepared statement inside of AbstractBatcher.class shows single quotes around the value (i.e. '11'). DB2 complains with a "SQL0401N The data types of the operands for the operation "=" are not compatible." error. Running the query in the DB2 Command Center I see it just needs the quotes removed. I see that in SQLServer 2008, where the same legacy database field has a datatype of "TINYINT", SQLServer is accepting of the single quoted value in the HQL statement. -- 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

16 years, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-503) Generated archetype broken for any package name with dot (.)

by G Fernandes (JIRA)

Generated archetype broken for any package name with dot (.) ------------------------------------------------------------ Key: HSEARCH-503 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-503 Project: Hibernate Search Issue Type: Patch Components: build Affects Versions: 3.2.0.Beta1 Reporter: G Fernandes Priority: Minor Steps to reproduce: ===================== $ cd hibernate-search-archetype $ mvn archetype:create-from-project -Darchetype.properties=src/main/archetype/archetype.properties ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 seconds [INFO] Finished at: Sat Apr 10 20:35:58 BST 2010 [INFO] Final Memory: 16M/80M [INFO] ------------------------------------------------------------------------ $ cd target/generate-sources/archetype $ mvn install ... [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3 seconds [INFO] Finished at: Sat Apr 10 20:36:50 BST 2010 [INFO] Final Memory: 18M/80M [INFO] ------------------------------------------------------------------------ $ cd ~/temp $ mvn archetype:generate -DarchetypeGroupId=org.hibernate -DarchetypeArtifactId=hibernate-search-quickstart -DarchetypeVersion=3.2.0-SNAPSHOT -DgroupId=my.company -DartifactId=quickstart -Dversion=1.0-SNAPSHOT ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5 seconds [INFO] Finished at: Sat Apr 10 20:39:17 BST 2010 [INFO] Final Memory: 13M/79M [INFO] ------------------------------------------------------------------------ $ cd quickstart $ mvn install [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[25,11] ';' expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,10] '.' expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,11] ';' expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,19] class, interface, or enum expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Book.java:[37,20] class, interface, or enum expected [ERROR] /Users/gustavo/temp/quickstart/src/main/java/com/mycomany/Author.java:[25,11] ';' expected -- 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

16 years, 2 months

4
21
0 / 0

[Hibernate-JIRA] Created: (HHH-4909) Null Pointer Exception When Usding Spring 3.0 with Hibernate 3.5.0-Beta-x

by Petar Tahchiev (JIRA)

Null Pointer Exception When Usding Spring 3.0 with Hibernate 3.5.0-Beta-x ------------------------------------------------------------------------- Key: HHH-4909 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4909 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1 Environment: Java, 1.6, Spring 3.0.0 (tested also with 3.0.1.SNAPSHOT) Reporter: Petar Tahchiev Priority: Critical Attachments: stacktrace.txt Hi guys, I had an application working fine with OpenJPA, but I decided to migrate to Hibernate and I get a Null pointer exception (see the attached stacktrace). Let me know if you need some other info. My configuration is below: persistence.xml: =========================================== =========================================== <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="frontend-ui"> <class>com.fugsley.beech.betting.db.model.User</class> .........[more here]...................  <properties>    <property name="c3p0.acquire_increment" value="1"/> <property name="c3p0.idle_test_period" value="100"/>  <property name="c3p0.min_size" value="5"/> <property name="c3p0.max_size" value="20"/> <property name="c3p0.timeout" value="1800"/> <property name="c3p0.max_statements" value="50"/>  <property name="hibernate.archive.autodetection" value="class, hbm"/> <property name="hibernate.show_sql" value="false"/> <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/> <property name="hibernate.connection.password" value="r00tka"/> <property name="hibernate.connection.url" value="jdbc:mysql://localhost:3306/fugsley?useUnicode=true&characterEncoding=UTF-8"/> <property name="hibernate.connection.username" value="fugsley"/> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.c3p0.min_size" value="5"/> <property name="hibernate.c3p0.max_size" value="20"/> <property name="hibernate.c3p0.timeout" value="300"/> <property name="hibernate.c3p0.max_statements" value="50"/> <property name="hibernate.c3p0.idle_test_period" value="3000"/> </properties> </persistence-unit> </persistence> ===============spring-application-context=========================== <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> <property name="loadTimeWeaver"> <bean class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver" /> </property> <property name="dataSource" ref="beechDataSource" /> <property name="jpaVendorAdapter"> <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"> <property name="database" value="Mysql" /> <property name="showSql" value="false" /> </bean> </property> </bean> -- 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

16 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-463) Merging of one-to-many relations not JPA spec compliant for lazy relations

by Dirk (JIRA)

Merging of one-to-many relations not JPA spec compliant for lazy relations -------------------------------------------------------------------------- Key: EJB-463 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-463 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate 3.2.6, Hibernate EntityManager 3.4.0, Hibernate Annotations 3.4.0, Oracle Reporter: Dirk Attachments: CascadeTest.zip Topic has been posted to the Hibernate Forum. See https://forum.hibernate.org/viewtopic.php?f=1&t=999398 Summary: Suppose you have an object Master with one-to-many relation to Detail. @Entity public class Master implements Serializable { @OneToMany(mappedBy = "master", cascade={CascadeType.MERGE, CascadeType.PERSIST}) private List<Detail> details = new ArrayList<Detail>(); ... } Master is loaded without fetching Detail (= lazy) and EntityManager is closed. Master is now in detached state. Merging Master causes Hibernate EntityManager to eagerly load the Detail collection although it is in lazy state. This is not JPA spec compliant. JPA spec states: The persistence provider must not merge fields marked LAZY that have not been fetched: it must ignore such fields when merging. See 3.2.4.1 Merging Detached Entity State, p.51. Tested also with the latest version of EclipseLink. EclipseLink behaves as expected. Testcase attached (Netbeans 6.7). -- 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

16 years, 2 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-333) Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId

by Hardy Ferentschik (JIRA)

Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId ------------------------------------------------------------------------------- Key: HSEARCH-333 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-333 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 http://forum.hibernate.org/viewtopic.php?t=993097 -- 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

16 years, 2 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-486) Review the getting started section's pom and archetype creation

by Emmanuel Bernard (JIRA)

Review the getting started section's pom and archetype creation --------------------------------------------------------------- Key: HSEARCH-486 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-486 Project: Hibernate Search Issue Type: Task Components: documentation Affects Versions: 3.2.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 3.2.0 HSEARCH-428 has been done but a second polish is likely required. -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-515) Lucene AlreadyClosedExceptions During Batch Processing With ASYNC Workers

by j nadler (JIRA)

Lucene AlreadyClosedExceptions During Batch Processing With ASYNC Workers ------------------------------------------------------------------------- Key: HSEARCH-515 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-515 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: j nadler We have a batch job that updates 10,000 preexisting User entities in a single transaction; each User has an @IndexedEmbedded UserDetails entity which is also updated during the job run. When run with hibernate.search.worker.execution=sync, life is good. When we run with async, indexing intermittently fails with a Lucene AlreadyClosedException. There is no other exception logged even with TRACE logging enabled. We did not see this issue with 3.1.1GA but Sanne has noted that it is possible the exceptions were occurring and were not being logged in that version; I cannot exclude this possibility. Posted a log file to http://www.attensa.com/download/files/attensa.log the first exception is at timestamp [2010-04-21 11:23:45.992,236829] Associated forum discussion here: https://forum.hibernate.org/viewtopic.php?f=9&t=1004022&p=2429214#p2429214 -- 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

16 years, 2 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-506) Suggest dependency to core 3.5.1

by Sanne Grinovero (JIRA)

Suggest dependency to core 3.5.1 -------------------------------- Key: HSEARCH-506 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-506 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0 The release pom should suggest a dependency to core version 3.5.1 , but it would be nice to start defining support for ranges of versions. I'd propose something like {{<version>[3.5.0,3.6.0)</version>}} but have to try to see how this interacts with the {{.FINAL}} postfix -- 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

16 years, 2 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-512) Associate with two open session issue and subsequent hang

by Marc Schipperheyn (JIRA)

Associate with two open session issue and subsequent hang --------------------------------------------------------- Key: HSEARCH-512 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-512 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1 Environment: Hibernate 3.5.1, MySQL 5.1.44, Lucene 2.9.2 Reporter: Marc Schipperheyn I've noticed the issue described in http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-490. It seems to happen sometimes, especially when threads pause for a debugging break and I don't immediately continue them. But I also notice that then the MassIndexer just doesn't finish and hangs with all the threads still in running state. Nothing seems to be happening or completing. I think that HSEARCH-490 has prevented the threads from completing at this point. The system/website then becomes completely unresponsive. -- 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

16 years, 2 months

2
16
0 / 0

[Hibernate-JIRA] Created: (HHH-1992) Some cascade actions should not trigger a property access on lazy properties

by Emmanuel Bernard (JIRA)

Some cascade actions should not trigger a property access on lazy properties ---------------------------------------------------------------------------- Key: HHH-1992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1992 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Critical Fix For: 3.2.0.ga -- 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

16 years, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HV-310) Define, which parts of HV constitute its public API

by Gunnar Morling (JIRA)

Define, which parts of HV constitute its public API --------------------------------------------------- Key: HV-310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-310 Project: Hibernate Validator Issue Type: Improvement Reporter: Gunnar Morling Assignee: Hardy Ferentschik Fix For: 4.1.0 Background: Mostly users interact only indirectly with Hibernate Validator through the Bean Validation API. But there are also some classes within HV, which are intended to be directly accessed by users (@Email, ResourceBundleMessageInterpolator etc). Right now it is not obvious, which parts (packages, classes) of Hibernate Validator make up this public API. To do: * Identify and mark those parts of HV, which constitute its public, user-accessible API. The following rules should apply: *# It seems useful to let complete packages be part of the API or not (instead of single classes) *# Non-public packages shouldn't contain public packages *# Whether a package is public or not should be stated in the package's JavaDoc. *# The fewer public classes there are, the better, as it will be way harder to modify those in future versions. * The following packages/classes are candidates for the public API: ** org.hibernate.validator ** org.hibernate.validator.constraints ** org.hibernate.validator.engine.resourceloading (should be moved due to 2.; maybe CachingResourceBundleLocator should be excluded?) ** org.hibernate.validator.engine.ResourceBundleMessageInterpolator (should be moved due to 1.) * Add a section to the HV ref guide describing the public API. In that context it should be defined and documented, which rules apply to the further development of this API (especially with respect to changes breaking backward-compatibility) * Modify the HV OSGi manifest in order to export only the public packages -- 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

16 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-314) Add @List annotations to the HV-specific constraints

by Gunnar Morling (JIRA)

Add @List annotations to the HV-specific constraints ---------------------------------------------------- Key: HV-314 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-314 Project: Hibernate Validator Issue Type: Improvement Components: validators Affects Versions: 4.1.0.Beta1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik Priority: Minor Background: The BV spec (chapter 2.2) recommends, that each constraint annotation should be accompanied by an inner multi-valued annotation @List, which allows to specify the same constraint multiple times at one element. This can be useful for instance to let the same constraint have different error messages for different validation groups. Todo: Add @List annotations as inner annotations to the HV-specific constraint annotations. -- 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

16 years, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5179) Criteria Projections.countDistinct() does not work for composite IDs or components for some dialects

by Gail Badner (JIRA)

Criteria Projections.countDistinct() does not work for composite IDs or components for some dialects ---------------------------------------------------------------------------------------------------- Key: HHH-5179 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5179 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Affects Versions: 3.5.1 Environment: hsqldb, mssql Reporter: Gail Badner Assignee: Gail Badner Priority: Minor Criteria Projections.countDistinct() does not work for composite IDs or compenents if the dialect only supports SELECT COUNT( DISTINCT ... ) with only 1 argument. According to http://msdn.microsoft.com/en-us/library/ms175997.aspx , a SQL workaround is: SELECT COUNT(*) FROM (SELECT DISTINCT authorFirstName, authorLastName, authorMiddleName, authorId from Authors) as foo -- 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

16 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ] Gail Badner updated HHH-1015: ----------------------------- Affects Version/s: 3.5.1 > Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table > ----------------------------------------------------------------------------------------- > > Key: HHH-1015 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 beta 2, 3.5.1 > Environment: Hibernate versions 3.1 beta 3 and 3.0.5 > Reporter: Steven Grimm > Priority: Minor > Attachments: 3.3.2.GA-HHH-1015-v1.patch, hhh-1015-version2.patch, hhh-1015.patch > > > I have the following mappings describing a hierarchy of events and a class that the events refer to: > <hibernate-mapping package="com.xyz"> > <class name="Event" table="event" discriminator-value="-1"> > <id name="Id" type="long" column="event_id"/> > <discriminator column="event_type_id" type="integer" /> > <subclass name="EventPayer" discriminator-value="-3"> > <join table="event_payer"> > <key column="event_id" /> > <many-to-one name="payer" column="payer_id" class="Payer" /> > </join> > <subclass name="EventPayerCreated" discriminator-value="1" /> > </subclass> > </class> > <class name="Payer" table="payer"> > <id name="payerId" column="payer_id" type="java.lang.Long"/> > <set name="eventPayers" inverse="true" cascade="save-update"> > <key column="payer_id"/> > <one-to-many class="EventPayer"/> > </set> > </class> > </hibernate-mapping> > When I fetch the Payer.eventPayers collection, Hibernate generates this SQL: > select eventpayer0_.payer_id as payer7_1_, > eventpayer0_.event_id as event1_1_, > eventpayer0_.event_id as event1_5_0_, > eventpayer0_1_.payer_id as payer2_6_0_, > eventpayer0_.event_type_id as event2_5_0_ > from event eventpayer0_ > inner join event_payer eventpayer0_1_ > on eventpayer0_.event_id=eventpayer0_1_.event_id > where eventpayer0_.payer_id=? > The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do. > I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element. -- 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

16 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010