December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2656) Using EntityMode.DOM4J results in an exception when mapping more than one collection to the root node (node=".")

by Andries Schutte (JIRA)

Using EntityMode.DOM4J results in an exception when mapping more than one collection to the root node (node=".") ---------------------------------------------------------------------------------------------------------------- Key: HHH-2656 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2656 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4 SP1, tested with MySQL 5.0. Reporter: Andries Schutte When mapping multiple collections to the root node, an exception results (mapping and exception stack trace is shown below). This works fine if only one collection is mapped to the root node, or if one explicitly specifies unique names for each collection parent node. We are unfortunately restricted by having to use customer-defined XSDs, so this is a show-stopper for us. <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class entity-name="ProcessImpl" table="PROCESSES" node="Process"> <id name="sysID" column="PROCESS_ID" node="sysID" type="string"/> <property name="version" column="PROCESS_VERSION" node="version" type="string"/> <property name="processType" column="PROCESS_TYPE" node="processType" type="string"/> <property name="status" column="PROCESS_STATE" node="status" type="string"/> <property name="createDate" column="PROCESS_CREATE_DATE" node="createDate" type="timestamp"/> <property name="creator" column="PROCESS_CREATOR" node="creator" type="string"/> <property name="transactionNumber" column="PROCESS_TX_NUMBER" node="transactionNumber" type="long"/> <property name="modifiedDate" column="PROCESS_MOD_DATE" node="modifiedDate" type="timestamp"/> <property name="modifier" column="PROCESS_MODIFIER" node="modifier" type="string"/> <property name="title" column="PROCESS_TITLE" node="title" type="string"/> <property name="timer" column="PROCESS_TIMER" node="timer" type="string"/> <property name="currentCSTime" column="PROCESS_CS_TIME" node="currentCSTime" type="timestamp"/> <bag name="requiredActivities" table="REQ_ACTIVITIES" node = "." embed-xml="true" lazy="false" cascade="all"> <key column="PROCESS_ID" not-null="true"/> <element column="REQ_ACTIVITY" type="text" node="requiredActivity"/> </bag> <bag name="retractedGuidelines" table="RET_GUIDELINES" node = "." embed-xml="true" lazy="false" cascade="all"> <key column="PROCESS_ID" not-null="true"/> <element column="RET_GUIDELINE" type="text" node="retractedGuideline"/> </bag> <set name="suspendedGuidelines" node = "." embed-xml="true" lazy="false" cascade="all"> <key column="PROCESS_ID" not-null="true"/> <one-to-many entity-name="SuspendedGuidelineImpl" embed-xml="true" node="suspendedGuideline"/> </set> </class> </hibernate-mapping> Exception stack trace: [6/6/07 22:11:41:246 GMT] 00000012 SystemErr R org.hibernate.HibernateException: Found shared references to a collection: ProcessImpl.retractedGuidelines at org.hibernate.engine.Collections.processReachableCollection(Collections.java:163) at org.hibernate.event.def.FlushVisitor.processCollection(FlushVisitor.java:37) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:101) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:61) at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:55) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:131) 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) at com.resonant.persistence.ExternalDataMgrHibernateDom4jImpl.persistHibernateEntity(ExternalDataMgrHibernateDom4jImpl.java:194) at com.resonant.persistence.ExternalDataMgrHibernateDom4jImpl.store(ExternalDataMgrHibernateDom4jImpl.java:172) at com.resonant.persistence.PersistenceHibernateDom4jImpl.storeObject(PersistenceHibernateDom4jImpl.java:215) at com.resonant.persistence.ejb.PersistenceLocalBean.storeObject(PersistenceLocalBean.java:192) at com.resonant.persistence.ejb.EJSLocalStatelessPersistenceLocalEJB_68e55914.storeObject(EJSLocalStatelessPersistenceLocalEJB_68e55914.java:1179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.springframework.ejb.access.LocalSlsbInvokerInterceptor.invoke(LocalSlsbInvokerInterceptor.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy2.storeObject(Unknown Source) at com.resonant.hub.processmanager.ProcessHubImpl.startProcess(ProcessHubImpl.java:179) at com.resonant.hub.processmanager.ejb.ProcessHubBean.startProcess(ProcessHubBean.java:138) at com.resonant.hub.processmanager.ejb.EJSRemoteStatelessProcessHubEJB_f45832db.startProcess(EJSRemoteStatelessProcessHubEJB_f45832db.java:208) at com.resonant.hub.processmanager.ejb._EJSRemoteStatelessProcessHubEJB_f45832db_Tie.startProcess(_EJSRemoteStatelessProcessHubEJB_f45832db_Tie.java:261) at com.resonant.hub.processmanager.ejb._EJSRemoteStatelessProcessHubEJB_f45832db_Tie._invoke(_EJSRemoteStatelessProcessHubEJB_f45832db_Tie.java:122) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:613) at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:466) at com.ibm.rmi.iiop.ORB.process(ORB.java:503) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1552) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2673) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2551) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510) -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2140) SQLQueryParser throws ArrayIndexOutOfBoundsException: -1 for SQL query with join mapped as set of string elements

by Artur Jonak (JIRA)

SQLQueryParser throws ArrayIndexOutOfBoundsException: -1 for SQL query with join mapped as set of string elements ----------------------------------------------------------------------------------------------------------------- Key: HHH-2140 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2140 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.1.3 Reporter: Artur Jonak I have the following mapping: <class name="GCPSimpleDocumentImpl" table="GCP_Node" mutable="false"> <id name="DocumentId" /> ... <set name="ApplicationAreas" table="GCP_ApplicationArea" cascade="none" order-by="Name" sort="natural" mutable="false"> <key column="DocumentId"/> <element type="string" column="Name"/> </set> </class> and I try to run an SQL query: List result = session.createSQLQuery( "select distinct {node.*}, {areas.*} from GCP_Node node join GCP_ApplicationArea areas on node.DocumentId=areas.DocumentId " + "where areas.Name like 'BS - CF%'") .addEntity("node", GCPSimpleDocumentImpl.class) .addJoin("areas", "node.ApplicationAreas") .list(); Unfortunately I get the following exception: java.lang.ArrayIndexOutOfBoundsException: -1 at org.hibernate.loader.custom.SQLQueryParser.substituteBrackets(SQLQueryParser.java:133) at org.hibernate.loader.custom.SQLQueryParser.process(SQLQueryParser.java:85) at org.hibernate.loader.custom.SQLCustomQuery.<init>(SQLCustomQuery.java:157) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:20) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:113) at org.hibernate.impl.AbstractSessionImpl.getNativeSQLQueryPlan(AbstractSessionImpl.java:137) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:164) ... -- 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, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3488) CascadingAction.PERSIST.getCascadableChildrenIterator method loading uninitialized collections

by Debra Zarley (JIRA)

CascadingAction.PERSIST.getCascadableChildrenIterator method loading uninitialized collections ---------------------------------------------------------------------------------------------- Key: HHH-3488 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3488 Project: Hibernate Core Issue Type: Bug Components: core, documentation Affects Versions: 3.3.1 Environment: Hibernate version 3.3.1 GA, DB2 version 9 Reporter: Debra Zarley public Iterator getCascadableChildrenIterator(EventSource session, CollectionType collectionType, Object collection) { // persists don't cascade to uninitialized collections return CascadingAction.getAllElementsIterator(session, collectionType, collection); } Looks like either the javadoc or the code is incorrect. I am guessing the code, since it makes sense that only loaded collections should be affected. I think it should be: public Iterator getCascadableChildrenIterator(EventSource session, CollectionType collectionType, Object collection) { // persists don't cascade to uninitialized collections return CascadingAction.getLoadedElementsIterator(session, collectionType, collection); } -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-982) HBM2JAVA w/ ejb3=true does not generate @IndexColumn annotation

by Parker Whirlow (JIRA)

HBM2JAVA w/ ejb3=true does not generate @IndexColumn annotation --------------------------------------------------------------- Key: HBX-982 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-982 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2beta10 Environment: HibernateTools 3.2beta10 Reporter: Parker Whirlow When using the HBM2JAVA tool with 'ejb3=true' to generate EJB annotations, a hibernate mapping consisting of an ordered List doesn't generate the @IndexColumn annotation in the resulting java class. See below: Mapping document: <hibernate-mapping package="com.company.ejb3.entity"> <union-subclass name="Person" table="person" extends="AbstractEntity"> <property name="firstName" column="first_name" not-null="true" type="string" length="150"></property> <list name="addresses" table="person_addresses"> <key column="person" /> <list-index column="address_index" /> <many-to-many column="address" class="Address" /> </list> </union-subclass> </hibernate-mapping> Resulting Person.java snippet: @ManyToMany(fetch=FetchType.LAZY) @JoinTable(name="person_addresses", joinColumns = { @JoinColumn(name="person", nullable=false, updatable=false) }, inverseJoinColumns = { @JoinColumn(name="address", nullable=false, updatable=false) }) public List<Address> getAddresses() { return this.addresses; } public void setAddresses(List<Address> addresses) { this.addresses = addresses; } The above should contain: @IndexColumn(name="address_index") -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1034) Need a way to have a "native-if-not-assigned" IdentifierGenerator

by Paul Shemansky (JIRA)

Need a way to have a "native-if-not-assigned" IdentifierGenerator ----------------------------------------------------------------- Key: HBX-1034 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1034 Project: Hibernate Tools Issue Type: New Feature Reporter: Paul Shemansky Attachments: hibernate-native-or-assigned-patch.diff NOTE: I believe I have explored every documented possibility in achieving the desired functionality. If I have misused Hibernate, the forum, or Google, I humbly apologize and stand to be corrected. With that being said, I believe this may be desired: -------------------------------------------------------------------- By setting the Hibernate configuration's primary key column to use a "native" implementation, Hibernate ALWAYS generates the entity's id when a save() is being called. There is no way to "override" the generated id. The attached patch creates an IdentityGenerator which allows a programmer to override the "generated" id, with an "assigned" id at runtime simply by setting the primary key property. The patch also changes the IdentifierGeneratorFactory to allow the short-name selection of the generator via a configuration file. Furthermore, the English documentation is patched to describe the generator, accordingly. Possibly related issues and reference material: The documentation does not seem to provide a solution for a native-if-not-assigned generator; you seem to only have one, or the other: http://www.hibernate.org/hib_docs/reference/en/html/mapping.html#mapping-... A scenario which describes a typical use case that warrants the proposed new feature: http://forum.hibernate.org/viewtopic.php?t=982560&highlight=native+id+gen... -- 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2823) non-primary-key attribute 'id' mapped to primary-key

by Wolfgang Hollweck (JIRA)

non-primary-key attribute 'id' mapped to primary-key ----------------------------------------------------- Key: HHH-2823 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2823 Project: Hibernate3 Issue Type: Bug Components: core, metamodel, query-hql, query-sql Affects Versions: 3.2.5 Reporter: Wolfgang Hollweck When querying an entity that got a non-primary-key attribute 'id', 'id' is not mapped to 'id' but to the entity's primary-key attribute, though Hibernate doc claims "The special property (lowercase) id may be used to reference the identifier property of an entity (!!!) provided that entity does not define a non-identifier property named id." see the hibernate forum for details: http://forum.hibernate.org/viewtopic.php?t=979124 -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-313) delete twice triggers detached entity error, but change to composite primary key and the exception is gone.

by Simon Ng (JIRA)

delete twice triggers detached entity error, but change to composite primary key and the exception is gone. ----------------------------------------------------------------------------------------------------------- Key: EJB-313 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-313 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.2.0.cr3 Environment: Windows XP Professional + Postgres 8.1 + Spring 2 + JPA + Hibernate 3.2.3 Reporter: Simon Ng Attachments: DeleteTwice.zip The attached file DeleteTwice.zip has the entire project; and the primary key is a composite primary key. Run the unit test and there is no exception, just an INFO level message of "handling transient entity in delete processing". Next, delete RestaurantPK.java, and change Restaurant.java to use a simple primary key: package blog.jpa.domain; import java.util.Set; import javax.persistence.CascadeType; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.JoinColumn; import javax.persistence.JoinTable; import javax.persistence.ManyToMany; import javax.persistence.OneToOne; @Entity public class Restaurant { @Id @GeneratedValue(strategy = GenerationType.AUTO) private long id; private String name; public long getId() { return id; } public void setId(long id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } } Change the onSetUpInTransaction to use different SQL statement to reflect a different table protected void onSetUpInTransaction() throws Exception { jdbcTemplate.execute("insert into restaurant (id, name) values (1, 'Burger Barn')"); jdbcTemplate.execute("insert into restaurant (id, name) values (2, 'Veggie Village')"); jdbcTemplate.execute("insert into restaurant (id, name) values (3, 'Dover Diner')"); } drop the table restaurant and run the unit test again. Now there is an exception [junit] Testcase: testDeleteRestaurant(blog.jpa.dao.JpaRestaurantDaoTests): Caused an ERROR [junit] Removing a detached instance blog.jpa.domain.Restaurant#3; nested exception is java.lang.IllegalArgumentExce ption: Removing a detached instance blog.jpa.domain.Restaurant#3 [junit] org.springframework.dao.InvalidDataAccessApiUsageException: Removing a detached instance blog.jpa.domain.Res taurant#3; nested exception is java.lang.IllegalArgumentException: Removing a detached instance blog.jpa.domain.Restaura nt#3 [junit] Caused by: java.lang.IllegalArgumentException: Removing a detached instance blog.jpa.domain.Restaurant#3 [junit] at org.hibernate.ejb.event.EJB3DeleteEventListener.performDetachedEntityDeletionCheck(EJB3DeleteEventLis tener.java:45) The java.lang.IllegalArgumentException is specified in the JPA spec. -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-45) @AssertFalse message interpolation is broken

by Olle Hallin (JIRA)

@AssertFalse message interpolation is broken -------------------------------------------- Key: HV-45 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-45 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.0.0.ga Reporter: Olle Hallin I have an Address domain object, which shall contain at least one of the fields street, zip, city and so on. A completely empty address is not valid. So I added a validator method that checks the entire object: @AssertFalse(message = "The address is empty") @Transient public boolean isEmpty() { // return true if all fields are null or empty } The InvalidValue generated when validating an empty Address contains "empty The address is empty", where the prefix "empty " is derived from the method name isEmpty(). I had expected the value "The address is empty". -- 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2401) CLOB truncation on DB2 when using 2 or 3 byte chars (UTF8)

by Simon Jongsma (JIRA)

CLOB truncation on DB2 when using 2 or 3 byte chars (UTF8) ---------------------------------------------------------- Key: HHH-2401 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2401 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0 GA + JBoss 4.0.4.GA on Windows XP + DB2 UDB for ISeries V5R3 + IBM JT Open driver 4.9 Reporter: Simon Jongsma Priority: Minor Attachments: ClobTruncated.zip A CLOB column is used in DB2 mapped to a String in Java with the Hibernate "Text" mapping. The column in DB2 has a CCSID 1208 which means "UTF8" (= Unicode). The CLOB truncation occurs when characters are used that are UTF8 coded in more than one byte. In that the string is truncated when persisted in the database. For example the string "Granpré Molière†; 0123456789". This string has three diacritical marks in it. The é and è are coded in two bytes in UTF8 and the † in three bytes. This string will be stored as "Granpré Molière†; 012345". So "6789" is not stored. It appears as though Hibernate does not take into account that a character can be more than 1 byte in UTF8. The number of missing char's at the end is exactly: string.getBytes("UTF-8").length minus string.length() It is not a problem of DB2 or the JT Open driver: Storing and retrieving (from a Java program) the same String directly via Jdbc into the DB2 table and retrieving it, works 100% fine. So this clearly points to a problem somewhere in Hibernate. -- 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, 9 months

3
6
0 / 0

[Hibernate-JIRA] Créée: (HHH-2086) Patch for bug HHH-2076 and to be able to use <formula> in <key> for <one-to-many>

by Xavier Brénuchon (JIRA)

Patch for bug HHH-2076 and to be able to use <formula> in <key> for <one-to-many> --------------------------------------------------------------------------------- Key: HHH-2086 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2086 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.cr4 Reporter: Xavier Brénuchon Attachments: formula_one_to_many.patch Hello, There is a patch to correct bug HHH-2076 and make an improvement for HHH-944. In fact, theses 2 cases are linked. They need, amongst other things, a formula in the right part of outer join. This patch is simple but many class concerns (to propagate formula templates). About formula in one-to-many : You must have at least a column (not only formula), because it's not possible to have an Update order without at least a column. If it is the case, hibernate patch will raise an MappingException rightly. This patch add two TestCase : org.hibernate.test.onetoone.bidirectionnalformula. OneToOneBidirectionalFormulaTest org.hibernate.test.onetomany.formula. OneToManyFormulaTest Would it be possible to integrate this patch into Hibernate 3.2 ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3585) Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3

by Brian Stansberry (JIRA)

Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3 ----------------------------------------------------------------- Key: HHH-3585 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3585 Project: Hibernate Core Issue Type: Task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.4 JBoss Cache 3 is the main development branch for JBC. It introduces MVCC locking, which should help the Hibernate 2LC use case. Integration with JBoss Cache 3 and use of MVCC has already been tested against the Hibernate Core 3.3.1.GA tag, on the https://svn.jboss.org/repos/hibernate/core/branches/JBOSS_CACHE_3/ branch. Task here is to port the changes (all in cache-jbosscache2 testsuite) to trunk. -- 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, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3492) Bug: SingleTableEntityPersister - generateSequentialSelect()

by Michael Kohlhuber (JIRA)

Bug: SingleTableEntityPersister - generateSequentialSelect() ------------------------------------------------------------ Key: HHH-3492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3492 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: hibernate 3.2.5.ga oracle 9i Reporter: Michael Kohlhuber http://forum.hibernate.org/viewtopic.php?t=990850 -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-812) Fetching Children of Database _crawls_.

by Syd Poetry (JIRA)

Fetching Children of Database _crawls_. --------------------------------------- Key: HBX-812 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-812 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8 Environment: MySQL 5.0, Eclipse 3.2, JDK 1.5, Beta8 for Hibernate Tools Reporter: Syd Poetry I just updated a bunch of components for Eclipse (mostly related to Visual Editor); added a couple of tables to my database, went to regenerate all the POJO clases .hbm.xml mapping files, and found that anything that queries the database schema runs abysmally slow. Updated the tools from beta6 to beta8 thinking it might be a conflict with one of the updates that was performed, still very slow (5+ minutes to retrieve a list of tables!). Deleted all my hibernate-related XML files thinking it might be a parsing error, went to generate a new console file, and revenge.xml, found out that any listbox that tried to access the schema appeared to be hanging. It finishes after much hard-drive crunching. I have 2.2 GBs free running windows XP, MEM usage is 856 MB out of 1.5 GB physical memory. Just out of curiousity, is *anyone* else having this slow response for schema detection? I'm wondering if I have to update another component like a driver or something like that. -- 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, 10 months

6
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3362) NullPointerException in org.hibernate.dialect.Dialect$2.getReturnType

by Istvan Kovacs (JIRA)

NullPointerException in org.hibernate.dialect.Dialect$2.getReturnType --------------------------------------------------------------------- Key: HHH-3362 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3362 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate Core 3.6.2 GA, hsqldb Reporter: Istvan Kovacs Attachments: bug_src.zip java.lang.NullPointerException at org.hibernate.dialect.Dialect$2.getReturnType(Dialect.java:85) at org.hibernate.hql.ast.util.SessionFactoryHelper.findFunctionReturnType(SessionFactoryHelper.java:382) at org.hibernate.hql.ast.tree.AggregateNode.getDataType(AggregateNode.java:21) at org.hibernate.hql.ast.tree.SelectClause.initializeExplicitSelectClause(SelectClause.java:143) at org.hibernate.hql.ast.HqlSqlWalker.useSelectClause(HqlSqlWalker.java:705) at org.hibernate.hql.ast.HqlSqlWalker.processQuery(HqlSqlWalker.java:529) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:645) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at org.hibernate.console.HQLQueryPage.setSession(HQLQueryPage.java:106) at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:388) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65) at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:383) [...] 3 classes: Employee: Long ID; String name; Shop shop Shop: Long ID; String name; Set<Employee> employees; Map<Product, Integer> stock Product: Long ID; String name I mapped them to RDBMS using Hibernate. There's a table to hold stock info: SHOP_PRODUCT_STOCK - has fields SHOP_ID, PRODUCT_ID, AMOUNT SQL to query the average stock of each product: select p.name as name, avg(sps.amount) as avg_stock from Shop s, Shop_Product_Stock sps, Product p where sps.product_id=p.product_id and sps.product_id=p.product_id group by p.name order by p.name; Attempt in HQL that the produces exception: select p, avg(s.stock[p]) from Shop s, Product p group by p I've also tried SELECTing and GROUPing BY p.id and p.name. None of the three variants work. -- 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, 10 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1082) Creating a formula property when reverse engineering

by Anders Reinhardt Hansen (JIRA)

Creating a formula property when reverse engineering ---------------------------------------------------- Key: HBX-1082 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1082 Project: Hibernate Tools Issue Type: Improvement Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: All environments Reporter: Anders Reinhardt Hansen Priority: Minor Having lots of formula properties in mapping files is quite frustrating when reverse engineering database changes. Therefore it would be a big help if there was a way to write formula properties in the Hibernate Reverse Engineering files. A property formula is a property of a mapping file which is calculated by hibernate. I.e. <class name="XXX"> <column name="xxx" type="xxx" formula="(coloumn1+coloumn2)/coloumn3"/> </class> the reveng file could look like this <hibernate-reverse-engineering> ... <formula name="xxx" type="xxx" formula="(coloumn1+coloumn2)/coloumn3"/> </hibernate-reverse-engineering> Maybe the reverse engineering file is not the correct place for this feature. Suggestions are welcome -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-746) Implemented BigDecimalRange Validator for BigDecimals with precision range and scale

by Priya M (JIRA)

Implemented BigDecimalRange Validator for BigDecimals with precision range and scale ------------------------------------------------------------------------------------ Key: ANN-746 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-746 Project: Hibernate Annotations Issue Type: New Feature Reporter: Priya M Attachments: BigDecimalRange.java, BigDecimalRangeValidator.java Currently, hibernate validator's do not have @Range or @Length for decimal numbers (like float, double and BigDecimal) for validating precision and scale simultaneously. Also, Hibernate doesn't generate correct db column types as Number(x,y) if Java Type is Float or Double. However it works only for BigDecimal. I've added the annotation for BigDecimalRange and BigDecimalRangeValidator for the same Usage @BigDecimalRange(minPrecision=0, maxPrecision=13, scale=2) public BigDecimal getFoo() { return this.foo; } It works for my app. -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-12) <T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique

by Emmanuel Bernard (JIRA)

<T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique --------------------------------------------------------------------------------------------------- Key: BVAL-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-12 Project: Bean Validation Issue Type: Sub-task Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik In ValidatorImpl.validate() T Generic of ValidatorContext<T> and InvalidConstraint<T> are likely to be different than the Validator<T> A context can be created in a validator (T are equal). but the same context (a clone really) can be passed to a sub validator. Ts are then different. I believe it's the same for InvalidConstraints. An IC created by a subvalidator<U> will craete IC<U>, you will need to convert them in IC<T> when coming to the root validator<T>. So we need something like private <U> List<InvalidConstraintImpl<T>> validate(ValidationContext<U> context, List<String> groups) { } same for similar methods. -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3233) Integer overflow in TableHiLoGenerator

by Hauke Rabe (JIRA)

Integer overflow in TableHiLoGenerator --------------------------------------- Key: HHH-3233 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3233 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Hauke Rabe The TableGenerator use for id generation the type INTEGER. The subclass TableHiLoGenerator use these id for multiplication with the maxLo value. But if you mutiply two int and assign the result to a long you can get an integer overflow. The TableGenerator should work with long values, or must be able to configure. -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2983) Properties of a Map key not consistently populated before being put into the Map

by Dobes Vandermeer (JIRA)

Properties of a Map key not consistently populated before being put into the Map -------------------------------------------------------------------------------- Key: HHH-2983 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2983 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Glassfish v2 b58, PostgreSQL 8.2, running in Windows XP Reporter: Dobes Vandermeer I'm getting weird behavior where my map correctly has two entries when fetched as part of a list, and only one entry when I fetch it using EntityManager.get(). Here's an abbreviated version of the mapping for the class that contains the Map: @Entity(name="Account") public class Account implements Comparable<Account>, SecurityChecks { private Long id; private Map<Currency, Balance> balances = new HashMap<Currency, Balance>(); // Current balance in each currency public Account() { } @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @OneToMany(cascade={CascadeType.ALL}, mappedBy="account") @MapKey(name="currency") public Map<Currency, Balance> getBalances() { return balances; } public void setBalances(Map<Currency, Balance> balances) { this.balances = balances; } } And the class that it contains: @Entity(name="Balance") @Table(uniqueConstraints={@UniqueConstraint(columnNames={ "account_id", "currency_id" })}) public class Balance implements SecurityChecks { private Long id; private Account account; private Currency currency; private long amount; @ManyToOne(cascade=CascadeType.PERSIST, optional=false) public Account getAccount() { return account; } public void setAccount(Account account) { this.account = account; } @Column(nullable=false) public long getAmount() { return amount; } public void setAmount(long amount) { this.amount = amount; } @ManyToOne(cascade=CascadeType.PERSIST, optional=false) @JoinColumn(name="currency_id") public Currency getCurrency() { return currency; } public void setCurrency(Currency currency) { this.currency = currency; } @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } } And a class that has a list of Accounts: @Entity(name="Business") public class Business implements SecurityChecks { private Long id; private String name; private List<Account> accounts = new ArrayList<Account>(); @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @OneToMany(mappedBy="business", cascade={CascadeType.ALL}) public List<Account> getAccounts() { return accounts; } public void setAccounts(List<Account> accounts) { this.accounts = accounts; } @Column(nullable=false) public String getName() { return name; } public void setName(String name) { this.name = name; } } Here's the definition of Currency: package com.habitsoft.books.model; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.Id; import javax.persistence.Transient; import com.habitsoft.books.service.client.CurrencyFormatter; @Entity(name="Currency") public class Currency implements Comparable<Currency> { private Long id; private String currencyCode; private String name; private String prefix = ""; private String suffix = ""; private int decimalPlaces; @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Override public int hashCode() { final int PRIME = 31; int result = 1; result = PRIME * result + ((getCurrencyCode() == null) ? 0 : getCurrencyCode().hashCode()); return result; } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (getClass() != obj.getClass()) return false; final Currency other = (Currency) obj; if (getCurrencyCode() == null) { if (other.getCurrencyCode() != null) return false; } else if (!getCurrencyCode().equals(other.getCurrencyCode())) return false; return true; } public int compareTo(Currency obj) { if (this == obj) return 0; if (obj == null) return -1; final Currency other = (Currency) obj; return getCurrencyCode().compareTo(other.getCurrencyCode()); } public String getCurrencyCode() { return currencyCode; } public void setCurrencyCode(String currencyCode) { this.currencyCode = currencyCode; } public String getName() { return name; } public void setName(String name) { this.name = name; } } Here's a line of code I use to fetch the Account directly: return em.find(Account.class, accountId); Here's how I fetch the list of accounts for a business: Business business = em.find(Business.class, businessId); return business.getAccounts().subList(offset, offset+limit); What is very, very odd to me is that the Accounts returned by the first form have just a single Balance instance in the map, when there should be two, whereas the ones returned by the second form have both entries I'm expecting. Hibernate prints the following SQL queries: Hibernate: select account0_.id as id270_0_, account0_.business_id as business5_270_0_, account0_.description as descript2_270_0_, account0_.name as name270_0_, account0_.type as type270_0_ from Account account0_ where account0_.id=? Hibernate: select balances0_.account_id as account3_2_, balances0_.id as id2_, balances0_.currency_id as formula5_2_, balances0_.id as id271_1_, balances0_.account_id as account3_271_1_, balances0_.amount as amount271_1_, balances0_.currency_id as currency4_271_1_, currency1_.id as id275_0_, currency1_.currencyCode as currency2_275_0_, currency1_.decimalPlaces as decimalP3_275_0_, currency1_.name as name275_0_, currency1_.prefix as prefix275_0_, currency1_.suffix as suffix275_0_ from Balance balances0_ inner join Currency currency1_ on balances0_.currency_id=currency1_.id where balances0_.account_id=? If I execute these queries against the database manually, the correct number of results is returned, so it seems likely that hibernate is generating the correct query, but then populating the map incorrectly. I took a guess that hashCode() and equals() in Currency were the most likely cause of the issue and indeed if I change them to use id instead of currencyCode the problem goes away. So, for some odd reason hibernate is populating the id field and not the other fields, and then putting it into the Map, but only when the object is fetched directly. This seems to point to some inconsistency in the way hibernate is initializing the objects and maps, somewhere. The workaround is to not use any fields except id in hashCode() and equals() for an entity used as a map key, and to ensure you call persist() on the key objects before putting them into the map. This seems like a reasonable constraint to me, but it would be nice if the behavior was more consistent to avoid excessive head-scratching. -- 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, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2574) Upload to maven2 repository

by David J. M. Karlsen (JIRA)

Upload to maven2 repository --------------------------- Key: HHH-2574 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2574 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.2.3 Environment: N/A Reporter: David J. M. Karlsen Attachments: hibernate-3.2.3.ga.pom Package 3.2.3ga to http://repo1.maven.org/maven2/org/hibernate/hibernate/ (Ideally source + javadocs, but at least pom and jar). pom attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-386) Deploy 3.4.0 GA to the maven2 central repo

by Steven Cummings (JIRA)

Deploy 3.4.0 GA to the maven2 central repo ------------------------------------------ Key: EJB-386 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-386 Project: Hibernate Entity Manager Issue Type: Task Components: EntityManager Affects Versions: 3.4.0.GA Reporter: Steven Cummings The JPA/Hibernate page [1] lists 3.4.0.GA as the latest version of entitymanager. Please deploy the artifacts (including source and javadoc jars) to the maven2 central repo. Thanks. [1] http://www.hibernate.org/397.html -- 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, 10 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2976) Documentation of Native SQLQuery contains errors

by Philippe Mouawad (JIRA)

Documentation of Native SQLQuery contains errors ------------------------------------------------ Key: HHH-2976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2976 Project: Hibernate3 Issue Type: Bug Components: documentation Affects Versions: 3.2.5 Environment: Hibernate 3.x to 3.2.5 Reporter: Philippe Mouawad Priority: Minor http://www.hibernate.org/hib_docs/reference/en/html/querysql.html This code is wrong: String sql = "SELECT ID as {c.id}, NAME as {c.name}, " + "BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} " + "FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID"; List loggedCats = sess.createSQLQuery(sql) .addEntity("cat", Cat.class) .addEntity("mother", Cat.class).list() See: HHH-2974 -- 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, 10 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3190) Correction in "Hibernate Core for Java"->"Reference Documentation" in chapter 7.6

by David Pinho (JIRA)

Correction in "Hibernate Core for Java"->"Reference Documentation" in chapter 7.6 --------------------------------------------------------------------------------- Key: HHH-3190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3190 Project: Hibernate3 Issue Type: Bug Components: documentation Reporter: David Pinho Priority: Trivial In http://www.hibernate.org/hib_docs/v3/reference, the first snippet in chapter 7.6 "More complex association mappings", contains: ... <property name="effectiveEndDate" type="date"/> <property name="effectiveStateDate" type="date" not-null="true"/> Shouldn' it be effectiveStartDate instead of effectiveStateDate? -- 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, 10 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3080) its just a typo

by mohammad hassan shamsi (JIRA)

its just a typo ---------------- Key: HHH-3080 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3080 Project: Hibernate3 Issue Type: Improvement Components: documentation Affects Versions: 3.2.5 Reporter: mohammad hassan shamsi Priority: Trivial document : hibernate_reference.pdf page : 27 in this sentence : Hibernate can automatically bind these ojects to the current thread of execution. objects is typed ojects. -- 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, 10 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3049) Add the performance test attached to HHH-2645 to test suite

by Gail Badner (JIRA)

Add the performance test attached to HHH-2645 to test suite ----------------------------------------------------------- Key: HHH-3049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3049 Project: Hibernate3 Issue Type: Improvement Components: testsuite Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.3 The performance test attached to HHH-2645 compares the following Map implementations used by org.hibernate.tuple.EntityModeToTuplizerMapping.: Collections.synchronizedMap( new org.apache.commons.collections.SequencedHashMap() ) <= used in pre-3.2.6 org.apache.commons.collections.FastHashMap() org.hibernate.util.FastHashMap <= used in 3.2.6 java.util.concurrent.ConcurrentHashMap() <= need Java 1.5 for this new EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap() EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap() This test should be added to the test suite as an integration test. Reminder: Read Paul Cowan's comment from 16/Nov/07 for corrections to the attached 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, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3397) reopening #HHH-2755 "wrong jsdk.jar referenced in the tutorial"

by Panos (JIRA)

reopening #HHH-2755 "wrong jsdk.jar referenced in the tutorial" --------------------------------------------------------------- Key: HHH-3397 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3397 Project: Hibernate3 Issue Type: Improvement Components: documentation Environment: Hibernate v3 Reporter: Panos Priority: Minor The problem appears again (as described in #HHH-2755) at http://www.hibernate.org/hib_docs/v3/reference/en/html/tutorial.html -- 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, 10 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3276) review proposed new doc styling

by Steve Ebersole (JIRA)

review proposed new doc styling ------------------------------- Key: HHH-3276 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3276 Project: Hibernate3 Issue Type: Improvement Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.0.CR2 http://www.jboss.org/files/jbosslabs/design/hibernate/index.htm -- 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, 10 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3352) HQL bulk update on JOINED inheritance tree improvement

by Anthony Patricio (JIRA)

HQL bulk update on JOINED inheritance tree improvement ------------------------------------------------------ Key: HHH-3352 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3352 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.4.sp1 Reporter: Anthony Patricio Priority: Minor Updating of entities in an inheritance hierarchy with the JOINED strategy. Trying to update all entities of this hierarchy using a hql statement that affects attributes/columns of the base entity only doesn't need the insert into TEMP / Update BASE_TABLE / delete TEMP logic Update BASE_TABLE is sufficient and more efficient. -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-895) Content assist doesn't work when an entity alias is not preceded by whitespace

by Joseph Marques (JIRA)

Content assist doesn't work when an entity alias is not preceded by whitespace ------------------------------------------------------------------------------ Key: HBX-895 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-895 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques In an HQL editor: If I type - "count(col." - and press ctrl+space, I don't get the content assist for col If I type - "count( col." - and press ctrl+space, I do Similarly, If I type - "select a,b." - and press ctrl+space, I don't get the content assist for b If I type - "select a, b." - and press ctrl+space, I do It's pretty clear that the lexing is a little bit too tight here, and that for better usability it should be relaxed. The second case isn't as big a deal as the first (because I don't know a single person that doesn't comma-space delimit the select clause, but I'm thinking that some people that don't realize that they have to put a space in front of it might think that the tools simply can't auto-complete inside functions. -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-858) wizard does not enable cfg.xml when it should

by Max Rydahl Andersen (JIRA)

wizard does not enable cfg.xml when it should --------------------------------------------- Key: HBX-858 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-858 Project: Hibernate Tools Type: Bug Components: consoleconfiguration Versions: 3.2beta9 Reporter: Max Rydahl Andersen when creating cfg.xml and afterwards in same wizard console config and etc/persistence.xml exists the cfg.xml cannot be enabled again...(jpa is chosen automatically) -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-880) Support sorting/grouping of the items in the Session Factory section of the Hiberate Configurations view

by Joseph Marques (JIRA)

Support sorting/grouping of the items in the Session Factory section of the Hiberate Configurations view -------------------------------------------------------------------------------------------------------- Key: HBX-880 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-880 Project: Hibernate Tools Type: New Feature Versions: 3.2beta8 Reporter: Joseph Marques I'm working with a domain model that has over 100 entities. It would be nice to have a consistent ordering of these items...maybe based off of the fully-qualified class name? It would be even nicer if they could be grouped by their different packages, which is how I've more naturally navigated to them in the past. Of course the packages should also be alpha-sorted, and each each of entities within a package sorted 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3445) Single Table Inheritence Broken for non table-unique keys

by Todd Tidwell (JIRA)

Single Table Inheritence Broken for non table-unique keys --------------------------------------------------------- Key: HHH-3445 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3445 Project: Hibernate3 Issue Type: Bug Environment: Hibernate Core: 3.2.6.ga Hibernate Annotations: 3.3.1.ga Hibernate EntityManager: 3.3.2.ga DB2 Linux 9.1 Reporter: Todd Tidwell I have an interesting mapping case that is causing me some very odd low-level errors. In this particular case, I'm working with a table that contains multiple objects and I can use a DiscriminatorColumn to differentiate. However, the "primary key" for the child objects is not guaranteed to be uniqe table-wide. For example, DiscriminatorColumn value '013' may have a unique-key value of 'A', DiscriminatorColumn '014' may have the same unique-key value. To map this, I created a base class, gave it the DiscriminatorColumn annotation, and then extended it with my various types. Here are the classes: @Entity @Table(name="WTTBLE") @DiscriminatorColumn(name="PTBLE") public abstract class MetaData { @Id @Basic(fetch=FetchType.EAGER) @Column(name="PCODE", nullable=false, insertable=false, updatable=false) private String code = null; @Basic(fetch=FetchType.EAGER) @Column(name="DEF", nullable=false, insertable=false, updatable=false) private String value = null; .... } @Entity @DiscriminatorValue(value = "015") public class AddressType extends MetaData { // No fields here, they're all mapped in MetaData } @Entity @DiscriminatorValue(value = "016") public class CustomerType extends MetaData { // No fields here, they're all mapped in MetaData } Now, this works great until they both have the same value for the "code" property. At that point, I get the following logging and exception: org.hibernate.impl.SessionImpl - initializing proxy: [com.wiley.permissions.domain.persistence.wintouch.metadata.AddressType#A] .... org.hibernate.event.def.DefaultLoadEventListener - load request found matching entity in context, but the matched entity was of an inconsistent return type; returning null .... javax.persistence.EntityNotFoundException: Unable to find test.AddressType with id A at org.hibernate.ejb.Ejb3Configuration$Ejb3EntityNotFoundDelegate.handleEntityNotFound(Ejb3Configuration.java:107) at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:79) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:68) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:150) at test.AddressType$$EnhancerByCGLIB$$16d4c983.getValue(<generated>) After some serious research, I found that org.hibernate.engine.StatefulPersistenceContext is returning the wrong object from it's getEntity method. It's returning a CustomerType object, which was added to the session's cache after the address type. On furthur examination, this seems to be because org.hibernate.engine.EntityKey.equals() is returning the same value for both objects. EntityKey's code for lines 95 -99 is: public boolean equals(Object other) { EntityKey otherKey = (EntityKey) other; return otherKey.rootEntityName.equals(this.rootEntityName) && identifierType.isEqual(otherKey.identifier, this.identifier, entityMode, factory); } Examination of the values of EntityKey for my objects show that rootEntityName for both objects is test.MetaData. That means that this method is going to return true. That, in turn, means that StatefulPersistenceContext's entitiesByKey HashMap is going to return the first one that equals the one passed into the get() 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, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3119) LazyInitializationException from 3.2.4+ onward

by Nick de Graeve (JIRA)

LazyInitializationException from 3.2.4+ onward ---------------------------------------------- Key: HHH-3119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3119 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6, 3.2.5, 3.2.4.sp1, 3.2.4 Reporter: Nick de Graeve Priority: Blocker We used to run JBoss 4.0.4.GA and we included Hibernate 3.2.0CR2 ourselves. Now we migrated to JBoss 4.2.2.GA and in that one Hibernate 3.2.4.sp1 is included by default. Unfortunately, we're getting LazyInitializationException when the object graph is more than 2 levels deep. E.g. RtTask --[OK]--> Priority --[FAIL]--> DictionaryEntry We haven't changed anything to our beans or configuration files. I did find out that v.3.2.4 is the first version that throws the exception. Example stack trace: 2008-02-18 13:52:35,425 ERROR [org.hibernate.LazyInitializationException] could not initialize proxy - no Session org.hibernate.LazyInitializationException: could not initialize proxy - no Session at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:57) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:166) at com.fpc.nokeos.core.common.beans.persistent.Priority_$$_javassist_13.getEntryName(Priority_$$_javassist_13.java) 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:585) at com.fpc.nokeos.core.server.dictionary.DictionaryContext.getField(DictionaryContext.java:319) at com.fpc.nokeos.core.server.dictionary.DictionaryContext.preparePojoAfterGetting(DictionaryContext.java:276) at com.fpc.nokeos.component.controlpanel.task.server.business.ControlPanelPluginTaskHelper.cleanRtTask(ControlPanelPluginTaskHelper.java:184) at com.fpc.nokeos.component.controlpanel.task.server.business.ControlPanelPluginTaskHelper.executeQueryToGetCPItem(ControlPanelPluginTaskHelper.java:575) at com.fpc.nokeos.component.controlpanel.task.server.business.ControlPanelPluginTaskHelper.getControlPanelItemsByFilter(ControlPanelPluginTaskHelper.java:525) at com.fpc.nokeos.component.controlpanel.task.server.ejb.ControlPanelPluginTaskBean.getControlPanelItemsByFilter(ControlPanelPluginTaskBean.java:59) 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:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) 2008-02-18 13:52:35,534 ERROR [com.fpc.nokeos.core.server.dictionary.DictionaryContext] Could not get field 'NAME'. java.lang.reflect.InvocationTargetException 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:585) at com.fpc.nokeos.core.server.dictionary.DictionaryContext.getField(DictionaryContext.java:319) at com.fpc.nokeos.core.server.dictionary.DictionaryContext.preparePojoAfterGetting(DictionaryContext.java:276) at com.fpc.nokeos.component.controlpanel.task.server.business.ControlPanelPluginTaskHelper.cleanRtTask(ControlPanelPluginTaskHelper.java:184) at com.fpc.nokeos.component.controlpanel.task.server.business.ControlPanelPluginTaskHelper.executeQueryToGetCPItem(ControlPanelPluginTaskHelper.java:575) at com.fpc.nokeos.component.controlpanel.task.server.business.ControlPanelPluginTaskHelper.getControlPanelItemsByFilter(ControlPanelPluginTaskHelper.java:525) at com.fpc.nokeos.component.controlpanel.task.server.ejb.ControlPanelPluginTaskBean.getControlPanelItemsByFilter(ControlPanelPluginTaskBean.java:59) 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:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) Caused by: org.hibernate.LazyInitializationException: could not initialize proxy - no Session at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:57) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:166) at com.fpc.nokeos.core.common.beans.persistent.Priority_$$_javassist_13.getEntryName(Priority_$$_javassist_13.java) ... 46 more -- 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, 11 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-251) add IndexShardingStrategy.getDirectoryProviderForSearch(Query query) method

by Jerry (JIRA)

add IndexShardingStrategy.getDirectoryProviderForSearch(Query query) method --------------------------------------------------------------------------- Key: HSEARCH-251 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-251 Project: Hibernate Search Issue Type: Improvement Components: directory provider Affects Versions: 3.1.0.Beta1 Reporter: Jerry Please getDirectoryProviderForSearch(Query query) method increase in the IndexShardingStrategy interface , and modify FullTestQueryImpl class buildSearcher way to call 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, 11 months

3
6
0 / 0

[Hibernate-JIRA] Created: (BVAL-26) The test suite assumes Hibernate Validator as the BV provider

by Emmanuel Bernard (JIRA)

The test suite assumes Hibernate Validator as the BV provider ------------------------------------------------------------- Key: BVAL-26 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-26 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard The test suite must be generic enough to test all BV providers, this will be the TCK. I check the bootstrap tests and they have this assumption big time: - hardcoded implementation - tests relying on specific exception messages - has some implementation specific assumptions on the framework -- 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, 11 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2498) Lazy Inverse Map Bug?

by CannonBall (JIRA)

Lazy Inverse Map Bug? --------------------- Key: HHH-2498 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2498 Project: Hibernate3 Type: Bug Versions: 3.2.1, 3.2.2 Environment: Hibernate 3.2.2, Java5, MySQL 5 (InnoDB) Reporter: CannonBall Priority: Minor Mapping documents: <hibernate-mapping> <class name="scratchpad.hibernate.A"> <id name="id"> <generator class="assigned"/> </id> <map name="bs" cascade="all-delete-orphan" inverse="true"> <key column="aId"/> <map-key type="long" column="cId"/> <one-to-many class="scratchpad.hibernate.B"/> </map> </class> <class name="scratchpad.hibernate.B"> <id name="id"> <generator class="assigned"/> </id> <many-to-one name="a" class="scratchpad.hibernate.A" column="aId"/> <many-to-one name="c" class="scratchpad.hibernate.C" column="cId" not-null="true"/> </class> <class name="scratchpad.hibernate.C"> <id name="id"> <generator class="assigned"/> </id> </class> </hibernate-mapping> Code between sessionFactory.openSession() and session.close(): long aId = 1l; long bId = 2l; long cId = 3l; SessionFactory factory = new Configuration().configure() .buildSessionFactory(); try { Session s = factory.openSession(); try { Transaction tx = s.beginTransaction(); try { C c = new C(cId); s.save(c); A a = new A(aId); B b = new B(bId); b.setC(c); b.setA(a); a.getBs().put(cId, b); s.save(a); tx.commit(); } catch (Exception e) { try { tx.rollback(); } catch (Exception e2) { // do nothing } throw e; } } finally { s.close(); } s = factory.openSession(); try { Transaction tx = s.beginTransaction(); try { A a = (A) s.load(A.class, aId); a.getBs().remove(cId); tx.commit(); } catch (Exception e) { try { tx.rollback(); } catch (Exception e2) { // do nothing } throw e; } } finally { s.close(); } } finally { factory.close(); } Name and version of the database you are using: MySQL 5.0.33 The generated SQL (show_sql=true): Hibernate: select b_.id, b_.aId as aId1_, b_.cId as cId1_ from B b_ where b_.id=? Hibernate: insert into C (id) values (?) Hibernate: insert into A (id) values (?) Hibernate: insert into B (aId, cId, id) values (?, ?, ?) Hibernate: select a0_.id as id0_0_ from A a0_ where a0_.id=? Hibernate: select bs0_.aId as aId1_, bs0_.id as id1_, bs0_.cId as cId1_, bs0_.id as id1_0_, bs0_.aId as aId1_0_, bs0_.cId as cId1_0_ from B bs0_ where bs0_.aId=? I've been having a confusing problem shown above, whereby A has a Map of Bs indexed using the id from an association with C. This Map is inversely mapped for A and with 'Cascade Delete Orphan'. In the second opened session above, where B is removed from A's Map and thus orphaned, B will not be deleted. I have observed B is only deleted if I either set 'lazy="false"' for A's Map or make an interaction with A's Map in the code (before B's removal) like 'a.getBs().get(cId)'. I suspect the lazy intializer is not initializing correctly in the above scenario. The above scenario does not happen if A's Map is not inversely mapped but B's many-to-one with A is. Can somebody shed some light on whether this is me using Hibernate incorrectly or is a bug? -- 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, 11 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3504) Hibernate 3.3.1GA issue when using CGLIB

by Montagnon Cyril (JIRA)

Hibernate 3.3.1GA issue when using CGLIB ---------------------------------------- Key: HHH-3504 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3504 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Database : hsqldb/Sybase Reporter: Montagnon Cyril When forcing hibernate to use CGLIB (by the way javassist is still slower than CGLib), I get the following exception (at the end of the post) It seems that the repackaging of the CGLIB project (hibernate-cglib-repack) doesn't behave as expected : Shouldn't it look up for the org.hibernate.repackage.cglib.proxy.Callback class instead of the net.sf.cglib.proxy.Callback class. java.lang.NoClassDefFoundError: net.sf.cglib.proxy.Callback at org.hibernate.repackage.cglib.proxy.Enhancer.class$(Enhancer.java:68) at org.hibernate.repackage.cglib.proxy.Enhancer.getCallbacksSetter(Enhancer.java:627) at org.hibernate.repackage.cglib.proxy.Enhancer.setCallbacksHelper(Enhancer.java:615) at org.hibernate.repackage.cglib.proxy.Enhancer.setThreadCallbacks(Enhancer.java:609) at org.hibernate.repackage.cglib.proxy.Enhancer.registerCallbacks(Enhancer.java:578) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyInstance(CGLIBLazyInitializer.java:133) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxy(CGLIBLazyInitializer.java:116) at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.getProxy(CGLIBProxyFactory.java:72) at org.hibernate.tuple.entity.AbstractEntityTuplizer.createProxy(AbstractEntityTuplizer.java:402) at org.hibernate.persister.entity.AbstractEntityPersister.createProxy(AbstractEntityPersister.java:3483) at org.hibernate.event.def.DefaultLoadEventListener.createProxyIfNecessary(DefaultLoadEventListener.java:298) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:219) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:905) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:822) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:815) at org.springframework.orm.hibernate3.HibernateTemplate$3.doInHibernate(HibernateTemplate.java:566) at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:419) at org.springframework.orm.hibernate3.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:374) at org.springframework.orm.hibernate3.HibernateTemplate.load(HibernateTemplate.java:560) at org.springframework.orm.hibernate3.HibernateTemplate.load(HibernateTemplate.java:554) at north.stardust2.core.test.unit.dao.listed.IndexCompositionDaoTest.findIndexCompositionByListedIndexAt(IndexCompositionDaoTest.java:36) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.junit.internal.runners.CompositeRunner.runChildren(CompositeRunner.java:33) at org.junit.runners.Suite.access$000(Suite.java:26) at org.junit.runners.Suite$1.run(Suite.java:93) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.runners.Suite.run(Suite.java:91) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) 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) -- 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, 11 months

16
36
0 / 0

[Hibernate-JIRA] Created: (ANN-782) InterceptFieldCallback is being mapped again since its package changed in Hibernate core 3.3.1

by Alex Gitelman (JIRA)

InterceptFieldCallback is being mapped again since its package changed in Hibernate core 3.3.1 ---------------------------------------------------------------------------------------------- Key: ANN-782 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-782 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Reporter: Alex Gitelman Hibernate-core generate fields of type 'org.hibernate.repackage.cglib.transform.impl.InterceptFieldCallback' instead of net.sf package, therefore fix from ANN-133 can't work >From AnnotationBinder: {code} private static boolean mustBeSkipped(XProperty property, ExtendedMappings mappings) { //TODO make those hardcoded tests more portable (through the bytecode provider?) return property.isAnnotationPresent( Transient.class ) || "net.sf.cglib.transform.impl.InterceptFieldCallback".equals( property.getType().getName() ) || "org.hibernate.bytecode.javassist.FieldHandler".equals( property.getType().getName() ); } {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, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3523) org.hibernate.id.enhanced.SequenceStyleGenerator causes org.hibernate.MappingException with SAPDB and DB2Dialect

by Damir Malenicic (JIRA)

org.hibernate.id.enhanced.SequenceStyleGenerator causes org.hibernate.MappingException with SAPDB and DB2Dialect ---------------------------------------------------------------------------------------------------------------- Key: HHH-3523 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3523 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1.GA Generation of DDL scripts for DB2Dialect and SAPDBDialect Reporter: Damir Malenicic Attachments: db2-sapdb-bug.zip While generating DDL scripts for mapping files that declare id <generator class="org.hibernate.id.enhanced.SequenceStyleGenerator"> the following exception is thrown: org.hibernate.MappingException: Dialect does not support pooled sequences at org.hibernate.dialect.Dialect.getCreateSequenceString(Dialect.java:701) at org.hibernate.dialect.Dialect.getCreateSequenceStrings(Dialect.java:659) at org.hibernate.id.enhanced.SequenceStructure.sqlCreateStrings(SequenceStructure.java:139) at org.hibernate.id.enhanced.SequenceStyleGenerator.sqlCreateStrings(SequenceStyleGenerator.java:328) at org.hibernate.cfg.Configuration.generateSchemaCreationScript(Configuration.java:945) at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:129) at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:91) I suspect the cause is in org.hibernate.dialect.Dialect#getCreateSequenceString(String sequenceName, int initialValue, int incrementSize) if ( supportsPooledSequences() ) { return getCreateSequenceString( sequenceName ) + " start with " + initialValue + " increment by " + incrementSize; } throw new MappingException( "Dialect does not support pooled sequences" ); This call requires not just that dialect supports sequences but that dialect supports pooled sequences. But the algorithm that tries to determine whether the table should be used to emulate the sequence lets the dialects that supports sequences but not pooled sequences to slip through. It looks like the DB2 and SAPDB dialects fail in this category because of: org.hibernate.id.enhanced.SequenceStyleGenerator#configure(Type type, Properties params, Dialect dialect) ... if ( dialect.supportsSequences() && !forceTableUse ) { if ( OptimizerFactory.POOL.equals( optimizationStrategy ) && !dialect.supportsPooledSequences() ) { forceTableUse = true; log.info( "Forcing table use for sequence-style generator due to pooled optimizer selection where db does not support pooled sequences" ); } } To workaround the problem I have created my generator that overrides SequenceStyleGenerator#configure, somethng like: public void configure(Type type, Properties params, Dialect dialect) throws MappingException { if (dialect.supportsSequences() && !dialect.supportsPooledSequences()) { params.setProperty(FORCE_TBL_PARAM, "true"); } super.configure(type, params, dialect); Attached is a zip file with a small maven project with unit-test that replicates the problem. It generates DDL for different databases: Hipersonic, Derby, Oracle, MySql, PostgreSQL, MSSQL, DB2, and SAPDB. The data-model contains 2 tables Person and Event in many-to-many relation. -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3497) Criteria row count return value in the type of Integer, not Long

by Yang Lifan (JIRA)

Criteria row count return value in the type of Integer, not Long ---------------------------------------------------------------- Key: HHH-3497 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3497 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: MySQL and Postgres Reporter: Yang Lifan I know the type of the return value of row count with HQL query is Long, to be compatible with JPA. But the Criteria is still return in the type of Integer, not in Long. So if there are a huge amount of data in the database, how can we get the right row count value with Criteria. ================================================= criteria.setProjection(Projections.rowCount()); Long result = Long.valueOf(criteria.uniqueResult().toString()); ================================================= I have to write like that to return the type of Long. But I know it is not real. -- 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, 11 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2881) PersistantBag.initializeFromCache can be intercepted by CollectionLoadContext.getLoadingCollection and so corrupt the collection

by Pavol Zibrita (JIRA)

PersistantBag.initializeFromCache can be intercepted by CollectionLoadContext.getLoadingCollection and so corrupt the collection -------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2881 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2881 Project: Hibernate3 Issue Type: Bug Environment: Hibernate Entity Manager 3.3.1 GA, oracle, Reporter: Pavol Zibrita It can occur that while PersistenBag.initializeFromCache is called to populate the collection from cache, the collection is populated also from CollectionLoadContext.getLoadingCollection, and so, the collection is filled with more data than needed. As the initializeFromCache uses direct access to the property this.bag, it will continue loading the collection. Here is the stack trace of what happens: PersistentBag.beforeInitialize(CollectionPersister, int) line: xx //here is the same collection reinitialized again, and loaded again CollectionLoadContext.getLoadingCollection(CollectionPersister, Serializable) line: 127 EntityLoader(Loader).readCollectionElement(Object, Serializable, CollectionPersister, CollectionAliases, ResultSet, SessionImplementor) line: 1003 EntityLoader(Loader).readCollectionElements(Object[], ResultSet, SessionImplementor) line: 646 EntityLoader(Loader).getRowFromResultSet(ResultSet, SessionImplementor, QueryParameters, LockMode[], EntityKey, List, EntityKey[], boolean) line: 591 EntityLoader(Loader).doQuery(SessionImplementor, QueryParameters, boolean) line: 701 EntityLoader(Loader).doQueryAndInitializeNonLazyCollections(SessionImplementor, QueryParameters, boolean) line: 236 EntityLoader(Loader).loadEntity(SessionImplementor, Object, Type, Object, String, Serializable, EntityPersister) line: 1860 EntityLoader(AbstractEntityLoader).load(SessionImplementor, Object, Object, Serializable) line: 48 EntityLoader(AbstractEntityLoader).load(Serializable, Object, SessionImplementor) line: 42 SingleTableEntityPersister(AbstractEntityPersister).load(Serializable, Object, LockMode, SessionImplementor) line: 3044 DefaultLoadEventListener.loadFromDatasource(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 395 DefaultLoadEventListener.doLoad(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 375 DefaultLoadEventListener.load(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 139 DefaultLoadEventListener.proxyOrLoad(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 195 DefaultLoadEventListener.onLoad(LoadEvent, LoadEventListener$LoadType) line: 103 SessionImpl.fireLoad(LoadEvent, LoadEventListener$LoadType) line: 878 SessionImpl.internalLoad(String, Serializable, boolean, boolean) line: 846 ManyToOneType(EntityType).resolveIdentifier(Serializable, SessionImplementor) line: 557 ManyToOneType.assemble(Serializable, SessionImplementor, Object) line: 196 TypeFactory.assemble(Serializable[], Type[], SessionImplementor, Object) line: 420 CacheEntry.assemble(Serializable[], Object, Serializable, EntityPersister, Interceptor, EventSource) line: 96 CacheEntry.assemble(Object, Serializable, EntityPersister, Interceptor, EventSource) line: 82 DefaultLoadEventListener.assembleCacheEntry(CacheEntry, Serializable, EntityPersister, LoadEvent) line: 553 DefaultLoadEventListener.loadFromSecondLevelCache(LoadEvent, EntityPersister, LoadEventListener$LoadType) line: 508 DefaultLoadEventListener.doLoad(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 357 DefaultLoadEventListener.load(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 139 DefaultLoadEventListener.proxyOrLoad(LoadEvent, EntityPersister, EntityKey, LoadEventListener$LoadType) line: 195 DefaultLoadEventListener.onLoad(LoadEvent, LoadEventListener$LoadType) line: 103 SessionImpl.fireLoad(LoadEvent, LoadEventListener$LoadType) line: 878 SessionImpl.internalLoad(String, Serializable, boolean, boolean) line: 846 ManyToOneType(EntityType).resolveIdentifier(Serializable, SessionImplementor) line: 557 ManyToOneType.assemble(Serializable, SessionImplementor, Object) line: 196 PersistentBag.initializeFromCache(CollectionPersister, Serializable, Object) line: xxx //NOW HERE IS THE Bag initializing from cache, it fails, see top of the stack!! CollectionCacheEntry.assemble(PersistentCollection, CollectionPersister, Object) line: 35 DefaultInitializeCollectionEventListener.initializeCollectionFromCache(Serializable, CollectionPersister, PersistentCollection, SessionImplementor) line: 130 DefaultInitializeCollectionEventListener.onInitializeCollection(InitializeCollectionEvent) line: 48 SessionImpl.initializeCollection(PersistentCollection, boolean) line: 1716 PersistentBag(AbstractPersistentCollection).forceInitialization() line: 454 StatefulPersistenceContext.initializeNonLazyCollections() line: 794 QueryLoader(Loader).doQueryAndInitializeNonLazyCollections(SessionImplementor, QueryParameters, boolean) line: 241 QueryLoader(Loader).doList(SessionImplementor, QueryParameters) line: 2220 QueryLoader(Loader).listIgnoreQueryCache(SessionImplementor, QueryParameters) line: 2104 QueryLoader(Loader).list(SessionImplementor, QueryParameters, Set, Type[]) line: 2099 QueryLoader.list(SessionImplementor, QueryParameters) line: 378 QueryTranslatorImpl.list(SessionImplementor, QueryParameters) line: 338 HQLQueryPlan.performList(QueryParameters, SessionImplementor) line: 172 SessionImpl.list(String, QueryParameters) line: 1121 QueryImpl.list() line: 79 QueryImpl.getResultList() line: 66 //some stack before, uninportant Small fix to the PersistantBag has resolved this issue, however I cannot tell if it is correct by some hibernate principles: public void initializeFromCache(CollectionPersister persister, Serializable disassembled, Object owner) throws HibernateException { Serializable[] array = (Serializable[]) disassembled; int size = array.length; List<Object> elements = new ArrayList<Object>(size); for ( int i = 0; i < size; i++ ) { Object element = persister.getElementType().assemble( array[i], getSession(), owner ); if ( element!=null ) { elements.add( element ); } } beforeInitialize( persister, size ); for ( Object element : elements ) { this.bag.add( element ); } } Difference is, before the this.bag.add(element) was called in first cycle, where the line of getting the element could cause reinitializing the collection and filling it up. There are various possibilities how to fix the problem, but I don't know if the fix is at the right place! -- 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, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3046) Merge fails on complicated data structure because of cycle references

by Pavol Zibrita (JIRA)

Merge fails on complicated data structure because of cycle references --------------------------------------------------------------------- Key: HHH-3046 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3046 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4 Environment: Hibernate-3.2.4.ga, db-platform any (h2 & oracle tested) Reporter: Pavol Zibrita On complicated object structure, hibernate was unable to merge it correctly because of attaching ID's to the new objects in the tree of the persistent entity. Hibernate cannot cope with cyclic references in this case and it fails with: javax.persistence.PersistenceException: org.hibernate.PropertyValueException: not-null property references a null or transient value: org.hibernate.bugtests.data.Transport.pickupNode at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:630) at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:237) at org.hibernate.bugtests.merge.MergeBug.mergeData(MergeBug.java:131) at org.hibernate.bugtests.merge.MergeBug.testBug(MergeBug.java:149) 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:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) 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) Caused by: org.hibernate.PropertyValueException: not-null property references a null or transient value: org.hibernate.bugtests.data.Transport.pickupNode at org.hibernate.engine.Nullability.checkNullability(Nullability.java:72) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:290) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:121) at org.hibernate.ejb.event.EJB3MergeEventListener.saveWithGeneratedId(EJB3MergeEventListener.java:43) at org.hibernate.event.def.DefaultMergeEventListener.entityIsTransient(DefaultMergeEventListener.java:186) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:123) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:687) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:669) at org.hibernate.engine.CascadingAction$6.cascade(CascadingAction.java:245) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:296) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:242) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:219) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:456) at org.hibernate.event.def.DefaultMergeEventListener.entityIsTransient(DefaultMergeEventListener.java:194) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:123) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:687) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:669) at org.hibernate.engine.CascadingAction$6.cascade(CascadingAction.java:245) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:296) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:242) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:219) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:456) at org.hibernate.event.def.DefaultMergeEventListener.entityIsTransient(DefaultMergeEventListener.java:194) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:123) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:687) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:669) at org.hibernate.engine.CascadingAction$6.cascade(CascadingAction.java:245) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.event.def.AbstractSaveEventListener.cascadeBeforeSave(AbstractSaveEventListener.java:431) at org.hibernate.event.def.DefaultMergeEventListener.entityIsTransient(DefaultMergeEventListener.java:178) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:123) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:687) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:669) at org.hibernate.engine.CascadingAction$6.cascade(CascadingAction.java:245) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:296) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:242) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:219) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.event.def.DefaultMergeEventListener.cascadeOnMerge(DefaultMergeEventListener.java:407) at org.hibernate.event.def.DefaultMergeEventListener.entityIsPersistent(DefaultMergeEventListener.java:152) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:126) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665) at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:228) ... 20 more However the value is set correctly. -- 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, 11 months

3
25
0 / 0

[Hibernate-JIRA] Created: (HHH-3532) schema update task should look for foreign key signature

by Dan Allen (JIRA)

schema update task should look for foreign key signature -------------------------------------------------------- Key: HHH-3532 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3532 Project: Hibernate Core Issue Type: Improvement Components: metamodel Affects Versions: 3.3.1 Reporter: Dan Allen Priority: Minor When the schema update task runs, it attempts to locate a foreign key in the database that matches the name provided in the Hibernate mapping information for that particular association. (The name of the foreign key is specified either in the foreign-key attribute in a mapping file or the @ForeignKey annotation). That much works fine. It's when a foreign key name is not provided, common in the case when standard JPA mappings are used, that problems arise. When a foreign key name is not provided, Hibernate generates a key name as follows: "FK" + hash code of referenced entity name + hash codes of columns The chances of an existing foreign key in the database using this generated name is slim to none (every DBA has their own conventions that they follow). Thus, as soon as the scheme update task hits a database under these conditions, duplicate foreign key definitions appear all over the place. If a foreign key name is not provided in the mapping, Hibernate should be looking instead to see if the signature of the foreign key matches that which is required to fulfill the mapping. In fact, I would even argue that the name is irrelevant and should only be used when actually *creating* the foreign key. Here is the existing logic in the generateSchemaUpdateScript in Configuration: ForeignKey fk = (ForeignKey) subIter.next(); boolean create = tableInfo == null || tableInfo.getForeignKeyMetadata( fk.getName() ) == null; It should be like this instead: ForeignKey fk = (ForeignKey) subIter.next(); boolean create = tableInfo == null || tableInfo.getForeignKeyMetadata( fk ) == null; getForeignKeyMetadata should retrieve based on the fk signature rather than the fk name. -- 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, 11 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3401) H2 Database Dialect Fixes

by Thomas Mueller (JIRA)

H2 Database Dialect Fixes ------------------------- Key: HHH-3401 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3401 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Thomas Mueller Attachments: H2Dialect.java.patch, test.zip There are a few bugs in the H2 Dialect: - There is no native BIT data type in H2. - The database function DATEDIFF does have parameters - There is a typo in function QUARTER I have created a patch and a simple test case: The problem with the BIT / BOOLEAN data type appears if you run the test twice. Please tell me if you need more information. Regards, Thomas -- 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, 11 months

9
17
0 / 0

[Hibernate-JIRA] Created: (ANN-698) @Transient property leads to org.hibernate.AnnotationException: Property has an unbound type

by Sebastian Baltes (JIRA)

@Transient property leads to org.hibernate.AnnotationException: Property has an unbound type -------------------------------------------------------------------------------------------- Key: ANN-698 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-698 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: hibernate3.jar: 3.2.5.ga hibernate-annotations.jar: 3.3.0.GA hibernate-commons-annotations.jar: 3.0.0.GA hibernate-validator.jar: 3.0.0.GA MySQL Reporter: Sebastian Baltes Attachments: log.txt Transient fields are not ignored in Hibernate. I got an "Property has an unbound type" exception and found no workaround. Entity: import javax.persistence.Entity; import javax.persistence.Id; import javax.persistence.Transient; @Entity public class Dummy<K> { @Id private Long id; @Transient transient private K dummyField; public Long getId() { return id; } public void setId(Long id) { this.id = id; } public K getDummyField() { return dummyField; } public void setDummyField(K dummyField) { this.dummyField = dummyField; } } Test Code: EntityManager em = EntityManagerSingleton.get(); EntityTransaction tx = em.getTransaction(); tx.begin(); Dummy a = new Dummy(); em.persist(a); tx.commit(); Exception: java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at junit.framework.TestSuite.createTest(TestSuite.java:54) at junit.framework.TestSuite.addTestMethod(TestSuite.java:280) at junit.framework.TestSuite.<init>(TestSuite.java:140) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader.getTest(JUnit3TestLoader.java:102) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader.loadTests(JUnit3TestLoader.java:59) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:445) 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) Caused by: javax.persistence.PersistenceException: org.hibernate.AnnotationException: Property de.neise.gena.model.file.Dummy.dummyField has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:258) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:120) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:33) at de.neise.gena.model.testbase.BaseTest.<clinit>(BaseTest.java:19) ... 13 more Caused by: org.hibernate.AnnotationException: Property de.neise.gena.model.file.Dummy.dummyField has an unbound type and no explicit target entity. Resolve this Generic usage issue or set an explicit target attribute (eg @OneToMany(target=) or use an explicit @Type at org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(AnnotationBinder.java:993) at org.hibernate.cfg.AnnotationBinder.getElementsToProcess(AnnotationBinder.java:833) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:645) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:498) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:277) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:186) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:246) ... 17 more -- 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, 11 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3559) Possibility to do versioning and non-versioning commits as required

by Adam Warski (JIRA)

Possibility to do versioning and non-versioning commits as required ------------------------------------------------------------------- Key: HHH-3559 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3559 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (EJB-358) Upgrade to ASM 3.1

by Juergen Zimmermann (JIRA)

Upgrade to ASM 3.1 ------------------ Key: EJB-358 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-358 Project: Hibernate Entity Manager Issue Type: New Feature Components: EntityManager Affects Versions: 3.3.2.GA Reporter: Juergen Zimmermann Hibernate EntityManager depends on ASM 2.2.3 JAX-RS will be the new spec for RESTful web services in Java. The reference implementation (aka Jersey) is available at https://jersey.dev.java.net and uses ASM 3.1. Therefore, Hibernate cannot be combined with the reference implementation of JAX-RS. -- 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, 11 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-369) Upgrade to CGLIB 2.2 (and thus ASM 3.1)

by Juergen Zimmermann (JIRA)

Upgrade to CGLIB 2.2 (and thus ASM 3.1) --------------------------------------- Key: EJB-369 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-369 Project: Hibernate Entity Manager Issue Type: Task Affects Versions: 3.4.0.CR1 Reporter: Juergen Zimmermann CGLIB 2.2 is now available and integrates with ASM 3.1 -- instead of the old, incompatible 2.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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-178) Some collection lazy loading lead to AssertionFailure

by Emmanuel Bernard (JIRA)

Some collection lazy loading lead to AssertionFailure ----------------------------------------------------- Key: HSEARCH-178 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-178 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.1.GA Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

6
25
0 / 0

[Hibernate-JIRA] Created: (HBX-947) When generating @Version annotation reveng tools should provide ability to set @Generated(GenerationTime.ALWAYS) and insertable = false, updatable = false for @Column

by MG (JIRA)

When generating @Version annotation reveng tools should provide ability to set @Generated(GenerationTime.ALWAYS) and insertable = false, updatable = false for @Column ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HBX-947 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-947 Project: Hibernate Tools Issue Type: Improvement Components: hbm2java, hbm2seam, reverse-engineer Affects Versions: 3.2beta9, 3.2beta10, 3.2LATER Environment: all Reporter: MG Priority: Minor When generating @Version annotation reveng tools should provide ability to set @Generated(GenerationTime.ALWAYS) and insertable = false, updatable = false for @Column. This behavior sould be configurable via reveng file (I think) This is needed in case version or timestamp is maintained by DB and not hibernate. (Ex: sybase timestamp) hbm.xml have also similar constructs for that, so reveng into hbm.xml might be also impacted. Thanks -- 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, 11 months

2
1
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 December 2008