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, 9 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, 10 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, 10 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

[Hibernate-JIRA] Created: (HHH-3420) MatchMode doesn't escape wildcard characters

by Hontvári József (JIRA)

MatchMode doesn't escape wildcard characters -------------------------------------------- Key: HHH-3420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3420 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.2 Environment: MySQL Reporter: Hontvári József Priority: Minor One can think that by specifying e.g. MatchMode.START in a "like" restriction Hibernate takes care of escaping SQL LIKE wildcard characters in the supplied pattern. It doesn't, actually Hibernate only inserts a % before the first character. I am not sure what was the intent of the original author (Gavin King), so the issue may only be missing documentation. However I don't see any other useful purpose of this class then providing database independent escaping. It seems that all databases use the % wildcard, so there is no need to provide database indpeendence to that. It can be argued that this might create a security problem for an unaware developer, so I set issue type to 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

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-489) add @AttributeOverride with formula support

by Amir Pashazadeh (JIRA)

add @AttributeOverride with formula support ------------------------------------------- Key: ANN-489 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-489 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.0.ga Reporter: Amir Pashazadeh @AttributeOverride currently just have name and column properties, there can be an alternative with formula support (instead of column support). -- 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: (HBX-1035) Safety: 'Run SchemaExport' menu option

by Karel-Henk Nijhuis (JIRA)

Safety: 'Run SchemaExport' menu option -------------------------------------- Key: HBX-1035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1035 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Reporter: Karel-Henk Nijhuis The 'Run SchemaExport' option that is accessible from the configuration context menu inside the Eclipse 'Hibernate Configurations' view does not give any feedback. Choosing this option, however, results in executing DDL on the database which erases all data inside the configured database. The schema export option could also be interpreted as a way to get the schema's SQL without executing the DDL. I would suggest to give more appropriate feedback before this operation is run. -- 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-3499) NamingStrategy should support naming foreign keys and indexes

by Geoffrey De Smet (JIRA)

NamingStrategy should support naming foreign keys and indexes ------------------------------------------------------------- Key: HHH-3499 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3499 Project: Hibernate Core Issue Type: Improvement Components: metamodel Affects Versions: 3.3.1 Reporter: Geoffrey De Smet hbm2ddl always generates foreign key constraints based on hashcodes, like this: alter table apple add index FK365FA4BB24B1D45C (lemon_id), add constraint FK365FA4BB24B1D45C foreign key (lemon_id) references lemon (id); Some databases don't support enough characters for foreign key names to generate a readable foreign key name, so that's a sensible default. However, those of use that use databases like MySQL etc, would like a readable foreign key name, such as: alter table apple add index FK_Apple_lemon (lemon_id), add constraint FK365FA4BB24B1D45C foreign key (lemon_id) references lemon (id); We can do that by annotating every entity with @Index in JPA, or specifying it in a hbm file, but we can't do it generally, by extending DefaultNamingStrategy or ImprovedNamingStrategy. Here's a proposition on how we could do it: - In the NamingStrategy interface, next to the method foreignKeyColumnName, add a method: public String foreignKeyConstraintName(String propertyName, String propertyEntityName, String propertyTableName, String referencedColumnName - DefaultNamingStrategy and ImprovedNamingStrategy should implement it as it is now, based on hashcodes. - If a mapping has an @Index JPA annotation or it's specified in a hbm file, that override counts. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2355) CGLIBLazyInitializer can not access a public member if parent class is not public

by Daniel Beland (JIRA)

CGLIBLazyInitializer can not access a public member if parent class is not public --------------------------------------------------------------------------------- Key: HHH-2355 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2355 Project: Hibernate3 Type: Bug Versions: 3.2.1 Reporter: Daniel Beland In hibernate 3.2.1, CGLIBLazyInitializer cannot acces a public method if it has been inherited from a parent class that is not public. Let's say we have a class A, modifier = default (package) with a public method getName() (and setName(String name)). Then I create a public class B that extends A. in my code I can retrieve B from the database: B b = session.load(B.class, new Integer(1), LockMode.NONE); I receive b with all the values set correctly (So at this point, Hibernate was able to use the method setName() correctly). In my code if I then try to use b.getName(), I receive and error: java.lang.IllegalAccessException-->Class org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer can not access a member of class A with modifiers "public" But I am not trying to access A.getName(), but B.getName() (which is a public method in a public class). This was working perfectly with Hibernate 2.1.7c and 3.1.3. The full information about my problem can be found here: http://forum.hibernate.org/viewtopic.php?t=969453 -- 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: (HSEARCH-330) NegativeArraySizeException if you use FullTextQuery.setMaxResults(Integer.MAX_VALUE)

by Hardy Ferentschik (JIRA)

NegativeArraySizeException if you use FullTextQuery.setMaxResults(Integer.MAX_VALUE) ------------------------------------------------------------------------------------ Key: HSEARCH-330 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-330 Project: Hibernate Search Issue Type: Bug Reporter: Hardy Ferentschik Seems to be a Lucene bug, but maybe we should add a work around? http://forum.hibernate.org/viewtopic.php?p=2401667 -- 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
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2745) NullPointerException when eager fetching joined many-to-many with native SQL query

by Mihail Fridliand (JIRA)

NullPointerException when eager fetching joined many-to-many with native SQL query ---------------------------------------------------------------------------------- Key: HHH-2745 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2745 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.1 Environment: Hibernate 3.2.1, DB2 Reporter: Mihail Fridliand NullPointerException when joining many-to-many assoziation with native SQL query: java.lang.NullPointerException at org.hibernate.loader.custom.sql.SQLQueryParser.resolveProperties(SQLQueryParser.java:182) at org.hibernate.loader.custom.sql.SQLQueryParser.resolveCollectionProperties(SQLQueryParser.java:135) at org.hibernate.loader.custom.sql.SQLQueryParser.substituteBrackets(SQLQueryParser.java:98) at org.hibernate.loader.custom.sql.SQLQueryParser.process(SQLQueryParser.java:51) at org.hibernate.loader.custom.sql.SQLCustomQuery.<init>(SQLCustomQuery.java:110) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:43) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:114) at org.hibernate.impl.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:444) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:351) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1291) The SQLQueryReturnProcessor ignores many-to-many assoziations: private void addCollection(String role, String alias, Map propertyResults) { SQLLoadableCollection collectionPersister = ( SQLLoadableCollection ) factory.getCollectionPersister( role ); alias2CollectionPersister.put( alias, collectionPersister ); String suffix = generateCollectionSuffix(); log.trace( "mapping alias [" + alias + "] to collection-suffix [" + suffix + "]" ); alias2CollectionSuffix.put( alias, suffix ); collectionPropertyResultMaps.put( alias, propertyResults ); if ( collectionPersister.isOneToMany() ) { SQLLoadable persister = ( SQLLoadable ) collectionPersister.getElementPersister(); addPersister( alias, filter( propertyResults ), persister ); } } Mapping of a many-to-many: <hibernate-mapping> <class name="A" table="A" schema="TEST" > <set name="manyToMany" inverse="true" table="AC" > <key> <column name="A_OID" not-null="true" /> </key> <many-to-many class="C"> <column name="C_OID" not-null="true" /> </many-to-many> </set> </class> <class name="C" table="C" schema="TEST"> </class> <resultset name="AandC"> <return alias="a" class="A"/> <return-join alias="c" property="a.manyToMany"/> </resultset> <sql-query name="getAandC" resultset-ref="AandC" > <![CDATA[ select DISTINCT {a.*},{c.*} from A a join AC ac on a.OID = ac.A_OID join C c on c.C_OID=ac.C_OID ]]> </sql-query> </hibernate-mapping> -- 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, 12 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2276) Can not get N first results of query with DB2 dialect (neither with setMaxResults nor with setFetchSize)

by Fred (JIRA)

Can not get N first results of query with DB2 dialect (neither with setMaxResults nor with setFetchSize) -------------------------------------------------------------------------------------------------------- Key: HHH-2276 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2276 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.1.2 Environment: DB2 V7 version = DSN07012 DB OS = zOS IBM DB2 JDBC Universal Driver Architecture Version du pilote JDBC : 2.1.34 Using dialect: org.hibernate.dialect.DB2Dialect Reporter: Fred I can't get the N first records from a select request using the setMaxResults method. HB generates a request that can not be understood by DB2 (select * from ( select rownumber() over() as rownumber etc.... see first stacktrace below) Moreover, using setFetchSize does not work (see second stack trace below the first one). Is there a way to tell HB to append " fetch first 10 rows only" to the query (as a workaround) ? Because my DB2 can understand that one : select * from MYTABLE where numseq = '2' fetch first 10 rows only thanks ! Fred STACK WITH SETMAXRESULTS : Hibernate: select * from ( select rownumber() over() as rownumber_, * from A165D.TB3PARCV where TVOY='D' ) as temp_ where rownumber_ <= ? [01/12/06 12:03:17:516 CET] 2d68c035 SystemOut O 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -104, SQLState: 42601 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -104, SQLState: 42601 12:03:17,516 67422 ERROR JDBCExceptionReporter (logExceptions, 72 ) - ILLEGAL SYMBOL "(". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO 12:03:17,516 67422 ERROR JDBCExceptionReporter (logExceptions, 72 ) - ILLEGAL SYMBOL "(". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -516, SQLState: 26501 12:03:17,516 67422 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -516, SQLState: 26501 12:03:17,547 67453 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT 12:03:17,547 67453 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE DESCRIBE STATEMENT DOES NOT SPECIFY A PREPARED STATEMENT 12:03:17,547 67453 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -514, SQLState: 26501 12:03:17,547 67453 WARN JDBCExceptionReporter (logExceptions, 71 ) - SQL Error: -514, SQLState: 26501 12:03:17,578 67484 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE CURSOR SQL_CURLN300C4 IS NOT IN A PREPARED STATE 12:03:17,578 67484 ERROR JDBCExceptionReporter (logExceptions, 72 ) - THE CURSOR SQL_CURLN300C4 IS NOT IN A PREPARED STATE 12:03:17,578 67484 ERROR WAction (execute, 56 ) - org.hibernate.exception.SQLGrammarException: could not execute query org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:65) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2153) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) at org.hibernate.loader.Loader.list(Loader.java:2024) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:117) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1607) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:121) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:169) [...] Caused by: com.ibm.db2.jcc.a.SqlException: ILLEGAL SYMBOL "(". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO at com.ibm.db2.jcc.a.cy.e(cy.java:1507) at com.ibm.db2.jcc.a.cy.a(cy.java:1117) at com.ibm.db2.jcc.a.cy.a(cy.java:1103) at com.ibm.db2.jcc.b.bd.h(bd.java:131) at com.ibm.db2.jcc.b.bd.a(bd.java:42) at com.ibm.db2.jcc.b.r.a(r.java:31) at com.ibm.db2.jcc.b.bs.g(bs.java:149) at com.ibm.db2.jcc.a.cy.l(cy.java:1097) at com.ibm.db2.jcc.a.cz.bb(cz.java:1554) at com.ibm.db2.jcc.a.cz.d(cz.java:1986) at com.ibm.db2.jcc.a.cz.S(cz.java:424) at com.ibm.db2.jcc.a.cz.executeQuery(cz.java:407) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:426) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2150) ... 52 more _____________________________________________________________________________________________________ STACK WITH SETFETCHSIZE() : [01/12/06 12:20:57:250 CET] 28ea8033 SystemOut O 11:20:57,250 403719 ERROR WAction (execute, 56 ) - org.hibernate.MappingException: No Dialect mapping for JDBC type: 3 org.hibernate.MappingException: No Dialect mapping for JDBC type: 3 at org.hibernate.dialect.TypeNames.get(TypeNames.java:56) at org.hibernate.dialect.TypeNames.get(TypeNames.java:81) at org.hibernate.dialect.Dialect.getHibernateTypeName(Dialect.java:192) at org.hibernate.loader.custom.CustomLoader.getHibernateType(CustomLoader.java:170) at org.hibernate.loader.custom.CustomLoader.autoDiscoverTypes(CustomLoader.java:138) at org.hibernate.loader.Loader.getResultSet(Loader.java:1678) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2150) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) at org.hibernate.loader.Loader.list(Loader.java:2024) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:117) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1607) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:121) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:169) -- 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, 12 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3044) Dialect.getSchemaSeparator() defined as char whereas sybase uses '..' as schema delimiter

by Alexis Haumont (JIRA)

Dialect.getSchemaSeparator() defined as char whereas sybase uses '..' as schema delimiter ----------------------------------------------------------------------------------------- Key: HHH-3044 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3044 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.0.5 Environment: Hibernate 3.0.5 used with Sybase ASE 12.5.4 Reporter: Alexis Haumont With Sybase ASE, the naming pattern for schema indexes objects is : schema..tableName But the abstract class org.hibernate.dialect.Dialect has the following method signature : /** * The separator between the schema/catalog/tablespace name and the table name. */ public char getSchemaSeparator() { return '.'; } It should be : public String getSchemaSeparator() { return "."; } and as such could ne overriden in SybaseDialect as : public String getSchemaSeparator() { return ".."; } -- 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, 12 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2877) native query (createSQL) cannot map the JDBC type text

by Bas van den Berg (JIRA)

native query (createSQL) cannot map the JDBC type text ------------------------------------------------------- Key: HHH-2877 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2877 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: MySQL 5.0.45, InnoDB Schema. Hibernate 3.2.5, Hibernate Annotations 3.3.0 Reporter: Bas van den Berg Priority: Minor When you invoke a SQLQuery in which a column of JDBC type text is queried an exception is thrown: org.hibernate.MappingException: No Dialect mapping for JDBC type: -1 see topic http://forum.hibernate.org/viewtopic.php?p=2366178#2366178 -- 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, 12 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2707) supports on-delete set-null (like in MySql 5)

by Emmanuel Bernard (JIRA)

supports on-delete set-null (like in MySql 5) --------------------------------------------- Key: HHH-2707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2707 Project: Hibernate3 Issue Type: New Feature Components: core 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, 12 months

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-598) Add ON clause to @ForeignKey

by Christian Bauer (JIRA)

Add ON clause to @ForeignKey ---------------------------- Key: ANN-598 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-598 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Christian Bauer More important than it sounds: @org.hibernate.annotations.ForeignKey(name = "FK_FEED_DIRECTORY_ID") I need ON CASCADE DELETE on many of my foreign keys, so I have to do this right now via: <hibernate-mapping> <database-object> <create> alter table FEED drop constraint FK_FEED_DIRECTORY_ID; alter table FEED add constraint FK_FEED_DIRECTORY_ID foreign key (DIRECTORY_ID) references NODE on delete cascade; </create> <drop></drop> </database-object> </hibernate-mapping> This is a bit annoying, especially since @JoinColumn(columnDefinition) is also not an option - I don't want to hardcode my HSQL datatypes. So we should accept a parameter on @ForeignKey (I know that the Hibernate binder doesn't have that notion at all, we need it in native Hibernate as well) that accepts "[ON {DELETE | UPDATE} {CASCADE | SET DEFAULT | SET NULL}];" and does the right thing during schema export. -- 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, 12 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3662) Merging read-only entities causes AssertionError("Merged entity does not have status set to MANAGED...")

by jpk (JIRA)

Merging read-only entities causes AssertionError("Merged entity does not have status set to MANAGED...") -------------------------------------------------------------------------------------------------------- Key: HHH-3662 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3662 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Windows XP Reporter: jpk What worked for me in 3.2.6 now doesn't: merging read-only entities. The following error now occurs when attempting to merge an entity: org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY Note this entity class of mine has the @Immutable annotation and removing it prevents this AssertionError from occurring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2766) many-to-one with property-ref run into an recursive issue

by René Fuchs (JIRA)

many-to-one with property-ref run into an recursive issue --------------------------------------------------------- Key: HHH-2766 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2766 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Informix 10 Reporter: René Fuchs With many-to-one and property-ref, hibernate resolve always the whole referenced entity. So we have alway an eager issue. If the resolved entity includes one or more other references to non primary keys, these entities will be also resolved and so on. In a big legacy database, if I read only one entity, I get 100 selects or a very very long joined sql (fetch="join"). I think the problem ist located in: org.hibernate.type.EntityType public Object resolve(Object obj, SessionImplementor sessionimplementor, Object obj1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3677) g

by pioneer (JIRA)

g - Key: HHH-3677 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3677 Project: Hibernate Core Issue Type: Sub-task Reporter: pioneer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-310) Out of Mem on Sorted ScrollableResults

by Sanne Grinovero (JIRA)

Out of Mem on Sorted ScrollableResults -------------------------------------- Key: HSEARCH-310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.0.1.GA Environment: Java SE, 3.0.1.GA Reporter: Sanne Grinovero Fix For: 3.1.0 http://forum.hibernate.org/viewtopic.php?p=2400452 I think this is more appropriate for 3.1.1 Emmanuel said: "The implementation suffers several flows: - we do create an EntityInfo[] as big as the number of hits - we lazily load this array but we never release "old content" - we lazily load the content (ie objects) by window but we never release it Some Soft reference based cache can help." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2882) QueryKey.equals() returning false with distributed caching

by Daniel Campagnoli (JIRA)

QueryKey.equals() returning false with distributed caching ---------------------------------------------------------- Key: HHH-2882 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2882 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Reporter: Daniel Campagnoli We noticed some issues recently with the query cache when using Coherence as the cache provider. This was due to instances of org.hibernate.cache.QueryKey not being equal after being serialized then deserialized. The equals check was failing on the [ResultTransformer customTransformer] field which in our case had an instance of RootEntityResultTransformer (which comes from the field CriteriaSpecification.ROOT_ENTITY). This is because RootEntityResultTransformer doesnt override equals, so the check is done by reference equality. When the QueryKey has been serialized and deserialized out of the cache, the instance will always be different, so the equals check will fail. A fix for this to be implement equals for RootEntityResultTransformer (and possibly the other ResultTransformer's). I used the following which worked fine. public boolean equals(Object obj) { return obj != null && this.getClass() == obj.getClass(); } ps. I created HHH-1665 a while ago, a real simple fix, could that be looked at :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3035) could not read column value from result set: MEDFAC1_14_0_; Invalid column name SQL Error: 17006, SQLState: null

by sanjeev singh (JIRA)

could not read column value from result set: MEDFAC1_14_0_; Invalid column name SQL Error: 17006, SQLState: null ---------------------------------------------------------------------------------------------------------------- Key: HHH-3035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3035 Project: Hibernate3 Issue Type: Bug Components: core, query-criteria, query-hql, query-sql Affects Versions: 3.2.2 Environment: JDK5 , Hibernate Junit Test case,WIndows XP Reporter: sanjeev singh The following is my section of hibernate mapping file. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="gov.njdhss.hippocrates.ems.valueobjects"> <class name="HeprEmsMedfacFacilityVO" table="HEPR_MEDFAC"> <id name="medfacId" column="MEDFAC_ID" type="java.lang.Long"> <generator class="sequence"> <param name="sequence">HEPR_MEDFAC_SEQ</param> </generator> </id> <property name="medfacName" type="java.lang.String" column="MEDFAC_NAME" update="true" insert="true"> </property> <property name="facCode" type="java.lang.String" column="FAC_CODE" update="true" insert="true"> </property> </class> <sql-query name="allfacility"> <return alias="facilities" class="HeprEmsMedfacFacilityVO" > <return-property name="medfacName" column="MEDFAC_NAME"/> </return> <![CDATA[ select facilities.MEDFAC_NAME AS medfacName from HEPR_MEDFAC facilities ]]> </sql-query> </hibernate-mapping> I am trying to execute the query using the following client code: public List getAllFacility() { List listAllFacilities = null; listAllFacilities = getHibernateTemplate().findByNamedQuery( "allfacility"); return listAllFacilities; } The following is the error: Hibernate: select facilities.MEDFAC_NAME AS medfacName from HEPR_MEDFAC facilities - could not read column value from result set: MEDFAC1_14_0_; Invalid column name - SQL Error: 17006, SQLState: null - Invalid column name - Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] - SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase] Any idea if it is a bug or there is any error in my 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

17 years

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-554) NPE with @Id on @OneToOne

by Loïc Minier (JIRA)

NPE with @Id on @OneToOne ------------------------- Key: ANN-554 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-554 Project: Hibernate Annotations Type: Bug Versions: 3.2.1 Environment: Hibernate 3.2.2 GA, Hibernate Annotations 3.2.1, J2SE 1.6.0-b105 on Debian GNU/Linux sid, PostgreSQL 7.4 Reporter: Loïc Minier Priority: Minor Hi, (Note: I originally reported this on the forum, but the lack of response suggests this might be a bug in Hibernate Annotations or Hibernate; the forum topic is at: http://forum.hibernate.org/viewtopic.php?t=970823) I hope it's not a misuse of Hibernate, but I'm trying to use @Id on @OneToOne, and this causes the following NPE when running hbm2ddl: java.lang.NullPointerException at org.hibernate.util.StringHelper.qualify(StringHelper.java:264) at org.hibernate.cfg.OneToOneSecondPass.doSecondPass(OneToOneSecondPass.java:196) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:296) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:56) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:287) at org.hibernate.tool.ant.Hbm2DDLExporterTask.execute(Hbm2DDLExporterTask.java:45) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:171) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) What I'm trying to do at the application level is: Foo class and table long foo_id, primary key FooData fooData, nulllable=true FooData class and table foo_id references Foo(foo_id), nullable=false This is expressed in Java as: @Entity @Table(name = "foo") public class Foo { @Id @GeneratedValue @Column(name = "foo_id") Long id; @OneToOne(mappedBy = "foo", cascade = CascadeType.ALL) FooData fooData; ... @Entity @Table(name = "foo_data") public class FooData { @Id @OneToOne @JoinColumn(name = "foo_id", nullable = false) Foo foo; This causes a NPE here. If I use a real Id on FooData, e.g.: @Id @Column(name = "foo_data_id") Long id; it works, and I end up with: - foo_id in table foo as a primary key - foo_data_id in table foo_data as a primary key - foo_id in table foo_data not null - foo_id in table foo_data references foo_id in table foo I don't want a foo_data_id, I don't need it, hence the lack of it which leads to the NPE. Bye, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2669) Unequivocally map MySQL LOB types to the LONG variant

by Steve Ebersole (JIRA)

Unequivocally map MySQL LOB types to the LONG variant ----------------------------------------------------- Key: HHH-2669 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2669 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 MySQL differentiates different "sizes" of LOBs. Apparently, the smaller types offer no storage benefit nor performance gain. So we should consider mapping the LOB types in the MySQL dialect to the LON variants in all cases. The current setup causes truncation headaches for users, apparently unnecessarily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1032) HibernateConsoleRuntimeException: "Could not load JPA Configuration" for JavaSE JPA project

by Donatas Ciuksys (JIRA)

HibernateConsoleRuntimeException: "Could not load JPA Configuration" for JavaSE JPA project ------------------------------------------------------------------------------------------- Key: HBX-1032 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1032 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.0.GA Environment: Eclipse 3.3.1.1, HibernateTools 3.2.0 GA, JDK 1.6.0_03 Reporter: Donatas Ciuksys Priority: Blocker I have Java SE (not EE) project in Eclipse with standard structure like: /src /META-INF/persistence.xml /bin ... I try to create new Hibernate Configuration in "Hibernate Configurations" pannel. I choose project, select JPA (jdk 1.5+) option, fill in persistence unit "InventorizacijaPU", check whether Classpath tab is OK (it contains my project). Press OK. Trying to expand configuration created, I get this exception: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:142) at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:496) at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:484) at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:203) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:185) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:106) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:38) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:97) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:103) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:196) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.hibernate.console.HibernateConsoleRuntimeException: Persistence unit not found: 'InventorizacijaPU'. at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:134) ... 11 more This is my persistence.xml: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="InventorizacijaPU" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <class>lt.mitsoft.inventorizacija.domain.BuvimoVieta</class> <class>lt.mitsoft.inventorizacija.domain.Inventorizacija</class> <class>lt.mitsoft.inventorizacija.domain.Irasas</class> <class>lt.mitsoft.inventorizacija.domain.IrasuBlokas</class> <class>lt.mitsoft.inventorizacija.domain.Preke</class> <class>lt.mitsoft.inventorizacija.domain.Skanuotojas</class> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect" />  <property name="hibernate.connection.url" value="jdbc:derby://localhost:1527/InventorizacijaDB" />  <property name="hibernate.connection.driver_class" value="org.apache.derby.jdbc.ClientDriver" /> <property name="hibernate.connection.username" value="admin" /> <property name="hibernate.connection.password" value="admin" /> <property name="hibernate.cache.provider_class" value="org.hibernate.cache.NoCacheProvider" />  </properties> </persistence-unit> </persistence> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
10
0 / 0

[Hibernate-JIRA] Created: (EJB-403) QueryTest - Native Query for Update using alias causes failure

by Juraci Paixao Krohling (JIRA)

QueryTest - Native Query for Update using alias causes failure -------------------------------------------------------------- Key: EJB-403 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-403 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL 8.2.3 and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest.diff Even though it says in documentation that it supports table aliases in "update" clauses[1], the below test fails when using it. Removing the table alias is enough to make it successful. org.hibernate.ejb.test.QueryTest#testUpdateQuery [1] http://www.postgresql.org/docs/8.2/interactive/sql-update.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

17 years

4
13
0 / 0

[Hibernate-JIRA] Created: (ANN-779) Test EmbeddedGenericsTest generates a table name "too long" for DB2

by Juraci Paixao Krohling (JIRA)

Test EmbeddedGenericsTest generates a table name "too long" for DB2 ------------------------------------------------------------------- Key: ANN-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-779 Project: Hibernate Annotations Issue Type: Bug Environment: Annotations Trunk / DB2 v9.1 Reporter: Juraci Paixao Krohling Annotations test EmbeddedGenericsTest#testWorksWithGenericCollectionOfElements generates the table name "EmbeddedGenericsTest$PopularBook_editions", but DB2 complains about its lengh: DB2 SQL error: SQLCODE: -107, SQLSTATE: 42622, SQLERRMC: EMBEDDEDGENERICSTEST$POPULARBOOK_ID;30 This error message says that the name exceeds the 30 characters limit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3554) Investigate how bulk updates can be supported

by Adam Warski (JIRA)

Investigate how bulk updates can be supported --------------------------------------------- Key: HHH-3554 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3554 Project: Hibernate Core Issue Type: Task 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

17 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2317) CGLIB unable to lazy load classes in diff. classloader than hibernate jars

by Jason Novotny (JIRA)

CGLIB unable to lazy load classes in diff. classloader than hibernate jars --------------------------------------------------------------------------- Key: HHH-2317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2317 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Jason Novotny Please see http://forum.hibernate.org/viewtopic.php?p=2334617#2334617 for more details and possible fix -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3229) Make cascade rules more transparent/explicit/deterministic

by Chris Bredesen (JIRA)

Make cascade rules more transparent/explicit/deterministic ---------------------------------------------------------- Key: HHH-3229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3229 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6, 3.2.5, 3.2.4.sp1 Reporter: Chris Bredesen Cascade rules are prone to different behavior based on the order in which properties appear in mapping XML. It is possible that an unexpected TransientObjectException may arise from certain operations when an object graph with circular references is merged (and possibly persisted/updated, etc). For example, if a transient instance is reachable through more than once path from a root entity, it is not clear whether operations will be cascaded to it. The order in which the properties are mapped plays a part in determining cascade paths, but the rules are not documented. Possible resolutions include: 1. Documenting the rules so that a programmer can make educated decisions about mapping. 2. Enhancing the algorithm such that order no longer matters and the rules are deterministic. 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

17 years

6
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-329) Workers ThreadPools breaks ThreadLocals

by Grégoire Rolland (JIRA)

Workers ThreadPools breaks ThreadLocals --------------------------------------- Key: HSEARCH-329 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-329 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.1.0.GA Reporter: Grégoire Rolland When Implementing multi-domains (multi-databases) FSDirectory based on thread local (to get the thread environment, database name, etc...), the threadpool used by workers "forgot" the thread local variables on the second call (for searching, indexing). Works great with 3.0.1 release, but not with 3.1.0.GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3095) Invalid queries when using subclasses and one-to-many associations

by Sebastien Blind (JIRA)

Invalid queries when using subclasses and one-to-many associations ------------------------------------------------------------------ Key: HHH-3095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3095 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, bug identified on sybase Reporter: Sebastien Blind Priority: Blocker Attachments: src-cat.zip This bug report builds on top of the topic found in the forum at http://forum.hibernate.org/viewtopic.php?t=977453 Basically, there seems to be an issue in the way hibernate treats a collections of objects that extend a base class. The attached example has: a Cat class a DomesticCat class (extends Cat) a Cage class (can contain multiple DomesticCat) The generated SQL is below - the filter cats0_.CAGE_ID=? should really be cats0_1_.CAGE_ID=? select cats0_.CAGE_ID as CAGE3_1_, cats0_.CAT_ID as CAT1_1_, cats0_.CAT_ID as CAT1_0_0_, cats0_1_.CAGE_ID as CAGE2_2_0_ from CAT cats0_ inner join DCAT cats0_1_ on cats0_.CAT_ID=cats0_1_.CAT_ID where cats0_.CAGE_ID=? As of now, I am not aware of any configuration that would work around this problem. Please let me know if you know otherwise. Thanks, Sebastien -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-790) ImmutableTest leaves an active transaction

by Juraci Paixao Krohling (JIRA)

ImmutableTest leaves an active transaction ------------------------------------------ Key: ANN-790 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-790 Project: Hibernate Annotations Issue Type: Patch Environment: PostgreSQL 8.2.3 and Annotations from trunk Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: ImmutableTest.java.diff ImmutableTest leaves an active transaction and makes PostgreSQL waits until it is finished (which never occurs). The attached patch fixes it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
3
0 / 0

[Hibernate-JIRA] Created: (HBX-779) jdbc reengineer sql-type problem with oracle 9i

by jacky hua (JIRA)

jdbc reengineer sql-type problem with oracle 9i ----------------------------------------------- Key: HBX-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-779 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8 Environment: windowsxp sp2, jdk 1.4.2, eclipse 3.1.2 Reporter: jacky hua I used the ant task hibernate-tools provided like the below to generate hbms xml <target name="default" description="generate hbm"> <delete dir="./generate"/> <mkdir dir="./generate"/> <hibernatetool destdir="./generate"> <jdbcconfiguration configurationfile="./metadata/hibernate.cfg.xml" revengfile="./metadata/hibernate.reveng.xml" packagename="net.ema.examples.sa" detectmanytomany="true" detectoptimisticlock="true"> </jdbcconfiguration> <hbm2hbmxml destdir="./generate" /> </hibernatetool> </target> the ./metadata/hibernate.cfg.xml like the below: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering SYSTEM "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" > <hibernate-reverse-engineering> <schema-selection match-catalog="TITAN" match-schema="TITAN" /> <type-mapping>   <sql-type jdbc-type="NUMERIC" precision="1" hibernate-type="boolean" />  <sql-type jdbc-type="NUMERIC" precision="19" hibernate-type="long" /> <sql-type jdbc-type="TIMESTAMP" hibernate-type="java.util.Date" /> </type-mapping>  <table-filter match-name="BIN$.*" exclude="true" /> </hibernate-reverse-engineering> But the <sql-type jdbc-type="NUMERIC" precision="19" hibernate-type="long" /> didn't work, also generate big_decimal type not long type, otherwise the others two sql-type rules worked. the not affected column:USER_ID was pk of my table. the generated hbm file is like the below: <class name="net.ema.examples.sa.UserModel" table="T_SA_USER" schema="TITAN"> <id name="userId" type="big_decimal"> <column name="USER_ID" scale="0" /> <generator class="assigned" /> </id> <property name="logonName" type="string"> <column name="LOGON_NAME" length="60" /> </property> <property name="password" type="string"> <column name="PASSWORD" length="80" /> </property> <property name="isOrgAdmin" type="java.lang.Boolean"> <column name="IS_ORG_ADMIN" precision="1" scale="0" /> </property> <property name="remark" type="string"> <column name="REMARK" length="400" /> </property> <property name="createDate" type="java.util.Date"> <column name="CREATE_DATE" length="11" /> </property> <property name="status" type="string"> <column name="STATUS" length="2" /> </property> </class> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3620) Oracle - testWithClause fails due to "Missing IN or OUT parameter at index:: 1"

by Juraci Paixao Krohling (JIRA)

Oracle - testWithClause fails due to "Missing IN or OUT parameter at index:: 1" ------------------------------------------------------------------------------- Key: HHH-3620 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3620 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.3.x Environment: Oracle 9i, Branch_3_3 Reporter: Juraci Paixao Krohling Test testWithClause (org.hibernate.test.hql.WithClauseTest) fails due to "Missing IN or OUT parameter at index:: 1" Stack trace: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:364) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.test.hql.WithClauseTest.testWithClause(WithClauseTest.java:112) 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 junit.framework.TestCase.runTest(TestCase.java:168) at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:125) at junit.framework.TestCase.runBare(TestCase.java:134) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:63) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:115) at junit.framework.TestSuite.run(TestSuite.java:227) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:84) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76) 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) Caused by: java.sql.SQLException: Missing IN or OUT parameter at index:: 1 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1711) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3311) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3361) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 31 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

17 years

1
6
0 / 0

[Hibernate-JIRA] Created: (EJB-381) EntityManager doesn't care about INSERT trigger of Oracle XE

by Juergen Zimmermann (JIRA)

EntityManager doesn't care about INSERT trigger of Oracle XE ------------------------------------------------------------ Key: EJB-381 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-381 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate EM 3.4.0, Hibernate Annotations 3.4.0, Hibernate Commons Annotations 3.1.0, Hibernate 3.3.0.SP1, Hibernate Validator 3.1.0.CR2, JDK 1.6.0_07 Reporter: Juergen Zimmermann I have an abstract entity class with 2 derived concrete classes: @Entity @Table(name="kunde") @Inheritance @DiscriminatorColumn(name="art", length=1) @XmlRootElement @XmlSeeAlso({ Firmenkunde.class, Privatkunde.class }) @XmlAccessorType(XmlAccessType.FIELD) public abstract class Kunde implements java.io.Serializable { @Id @GeneratedValue(generator="kunde_sequence_name") @SequenceGenerator(name="kunde_sequence_name", sequenceName="kunde_k_id_seq", allocationSize=1) @Column(name="k_id", nullable=false) @XmlAttribute(name="id", required=true) protected Long id = KEINE_ID; @Version @XmlTransient protected int version = ERSTE_VERSION; @Column(length=32, nullable=false) @XmlElement(required=true) protected String nachname = ""; ... @Column(length=32, unique=true) protected String username = ""; ... } The table is created as follows: CREATE TABLE kunde( k_id NUMBER(16) NOT NULL PRIMARY KEY, version NUMBER(8) DEFAULT 0, nachname VARCHAR2(32) NOT NULL, ... art VARCHAR2(2) DEFAULT 'P', ... username VARCHAR2(32) NOT NULL UNIQUE, ... ); Additionally there is this sequence and insert trigger for column username. CREATE SEQUENCE kunde_k_id_seq START WITH 200 NOMAXVALUE / CREATE OR REPLACE TRIGGER kunde_trigger_insert BEFORE INSERT ON kunde FOR EACH ROW BEGIN :NEW.username := TO_CHAR(:NEW.k_id); END; / New objects are inserted into the database using this code which works fine with PostgreSQL. However, using Oracle XE the insert trigger isn't considered: public List<Kunde> insertKunden(List<Kunde> kunden) { if (kunden == null || kunden.isEmpty()) { return new ArrayList<Kunde>(0); } for (Kunde k: kunden) { em.persist(k); } return kunden; } The attribute "username" is null using Oracle XE, but using PostgreSQL it has the value produced by the INSERT trigger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-404) QueryTest - PostgreSQL - "ERROR: operator does not exist: character varying = bytea"

by Juraci Paixao Krohling (JIRA)

QueryTest - PostgreSQL - "ERROR: operator does not exist: character varying = bytea" ------------------------------------------------------------------------------------ Key: EJB-404 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-404 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest_2.diff Test org.hibernate.ejb.test.QueryTest#testIsNull fails due to this query: select i from Item i where (i.descr is null and :descr is null) or i.descr = :descr When changing the query to what it reads below, it works properly: select i from Item i where i.descr = :descr or (i.descr is null and :descr is null) As this happened only with PostgreSQL, I assume this is an issue with either the driver or with the database itself. Will dig into pgsql's site to find out more about this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
8
0 / 0

[Hibernate-JIRA] Created: (EJB-407) Some tests are not closing the EM or finishing transactions

by Juraci Paixao Krohling (JIRA)

Some tests are not closing the EM or finishing transactions ----------------------------------------------------------- Key: EJB-407 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-407 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: UnclosedEM-UnfinishedTransactions.diff The below tests are not closing the EM or not finishing transactions (committing/rolling back), causing the test to hang indefinitely when the EM tries to drop the database entities after the test finishes: org/hibernate/ejb/test/callbacks/CallbacksTest.java org/hibernate/ejb/test/emops/FlushTest.java org/hibernate/ejb/test/lock/LockTest.java org/hibernate/ejb/test/exception/ExceptionTest.java org/hibernate/ejb/test/transaction/FlushAndTransactionTest.java The attached patch closes the EM and/or rolls back the unfinished transaction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
5
0 / 0

[Hibernate-JIRA] Created: (EJB-337) Entity scaning failing when path protocol is "file:" (not jar) and it contains spaces

by valery gorbunov (JIRA)

Entity scaning failing when path protocol is "file:" (not jar) and it contains spaces ------------------------------------------------------------------------------------- Key: EJB-337 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-337 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: OS Linux Hibernate 3.2.5ga HiberanteEM -3.3.1ga Reporter: valery gorbunov Priority: Critical Entity scanning failed when path contains spaces Stack trace is: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:74) at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48) at org.jboss.util.file.FileProtocolArchiveBrowserFactoryTest.testCreate(FileProtocolArchiveBrowserFactoryTest.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) 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: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.jar.JarFile.<init>(JarFile.java:133) at java.util.jar.JarFile.<init>(JarFile.java:97) at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:69) ... 24 more Problem in FileProtocolArchiveBrowserFactory class see test: package org.jboss.util.file; import static org.junit.Assert.assertNotNull; import static org.junit.Assert.assertTrue; import java.io.File; import java.net.MalformedURLException; import java.net.URI; import java.net.URISyntaxException; import junit.framework.Assert; import org.junit.Test; /** * * @author Valery Gorbunov <a href=mailto:vgorbunov@comodo.com.ua>vgorbunov(a)comodo.com.ua</a> */ public class FileProtocolArchiveBrowserFactoryTest { @Test public void testCreate() throws MalformedURLException, URISyntaxException { URI uri = new URI("file:/tmp/Path%20with%20space"); File f = new File(uri); if (!f.exists()) { Assert.assertTrue(f.mkdir()); } FileProtocolArchiveBrowserFactory factory = new FileProtocolArchiveBrowserFactory(); Object ab = factory.create(f.toURI().toURL(), null); assertNotNull(ab); assertTrue(ab instanceof DirectoryArchiveBrowser); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2782) Component getType caches the type value

by Kiss Zoltán (JIRA)

Component getType caches the type value --------------------------------------- Key: HHH-2782 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2782 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: all Reporter: Kiss Zoltán Component class caches the value of the type attribute: public Type getType() throws MappingException { // added this caching as I noticed that getType() is being called multiple times... if ( type == null ) { type = buildType(); } return type; } This forbids the use of 'dynamic attributes'. For eg. if you try to add new properties to an existing dynamic-component with the addProperty method, then the rebuild of the session factory will failed, because the Component property will be invalid during the validation (in the Component there will be a different column span value, then in the cached ComponentType). There should be a method like this in the Component class: public void rebuildType() { type = buildType(); } With the help of this the type could be rebuild if it is necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-770) Confusing error when missing default constructor

by Miguel Griffa (JIRA)

Confusing error when missing default constructor ------------------------------------------------ Key: ANN-770 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-770 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Reporter: Miguel Griffa if a persistent class X is missing the default constructor, instead of reporting the missing default constructor in class X, I obtained a noclassdeffound for a class Y, referenced in class X, which was oviously in classpath. this incorrect error message is very misleading in a debug session. if this problem can't be reproduced easily in current test base please indicate so, I'll try to reproduce my environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3128) NullPointerException while building SessionFactory when using native sql query for loading many-to-many mapped collections

by Juergen Denzel (JIRA)

NullPointerException while building SessionFactory when using native sql query for loading many-to-many mapped collections -------------------------------------------------------------------------------------------------------------------------- Key: HHH-3128 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3128 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6, 3.2.5 Environment: Hibernate 3.2.6 Reporter: Juergen Denzel Attachments: src.zip Hi, I am trying to load a many-to-many mapped collection using a sql query like this: <sql-query name="loadItems"> <load-collection alias="item" role="test.Test.items"/> select {item.*} from Items item where item.id = :id </sql-query> This always fails due to a NullPointerException: java.lang.NullPointerException at org.hibernate.loader.custom.sql.SQLQueryParser.resolveProperties(SQLQueryParser.java:182) at org.hibernate.loader.custom.sql.SQLQueryParser.resolveCollectionProperties(SQLQueryParser.java:135) at org.hibernate.loader.custom.sql.SQLQueryParser.substituteBrackets(SQLQueryParser.java:98) at org.hibernate.loader.custom.sql.SQLQueryParser.process(SQLQueryParser.java:51) at org.hibernate.loader.custom.sql.SQLCustomQuery.<init>(SQLCustomQuery.java:110) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:43) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:114) at org.hibernate.impl.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:446) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:352) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at test.HibernateTest.testSessionFactory(HibernateTest.java:18) I provided a very simple TestCase + Mappings to illustrate the problem. The exception does not occur for one-to-many mappings. Just for your information, we need this functionality in order to deal with DB2 problems we have. I ran this TestCase against 3.2.5 and 3.2.6 and both failed. Thanks. Juergen Denzel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-374) persistence.xml <jar-file> not following JSR220 spec

by Jeff Ferber (JIRA)

persistence.xml <jar-file> not following JSR220 spec ---------------------------------------------------- Key: EJB-374 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-374 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.CR2 Environment: regression: 3.3.2.GA, 3.4.0.CR2 Reporter: Jeff Ferber JSR220 says <jar-file> is relative to the root of the persistence unit, which is the place containing the META-INF/persistence.xml This is not the case. Instead, it looks for the jar relative to the JVM working directory. (see JarVisitorFactory.java) So providing an absolute file path in <jar-file> works, but not a relative path because the root changes changes based on the situation and environment. E.g., the directory you run ant, when running tomcat, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3148) Exception thrown by debug trace code: ComponentType toLoggableString

by Pete Geraghty (JIRA)

Exception thrown by debug trace code: ComponentType toLoggableString -------------------------------------------------------------------- Key: HHH-3148 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3148 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga HibernateAnnotations 3.3.0.ga Oracle 10g Express Edition Reporter: Pete Geraghty Priority: Minor Attachments: ToLoggableStringExample.txt The method toLoggableString in ComponentType is used to provide tracing output when running with log level DEBUG. In some circumstances it throws a ClassCastException. This is not a good idea in tracing code and obscures underlying problems. In my case the underlying problem was a previous incorrect call to set a parameter value in a query. I saw that previous JIRA issues have mentioned this ClassCastException as a side effect of other underlying problems - it is a distraction and time-waster. Lines 375-378 read: EntityMode entityMode = tuplizerMapping.guessEntityMode( value ); if ( entityMode == null ) { throw new ClassCastException( value.getClass().getName() ); } A better solution would be to just us String.valueOf EntityMode entityMode = tuplizerMapping.guessEntityMode( value ); if ( entityMode == null ) { return String.valueOf(value); } Another possibility would be to concatenate some diagnostic message with String.valueOf, but personally I don't think that be helpful. Stack trace is: Exception in thread "main" java.lang.ClassCastException: java.lang.String at org.hibernate.type.ComponentType.toLoggableString(ComponentType.java:377) at org.hibernate.pretty.Printer.toString(Printer.java:76) at org.hibernate.engine.QueryParameters.traceParameters(QueryParameters.java:277) at org.hibernate.engine.query.HQLQueryPlan.performIterate(HQLQueryPlan.java:210) at org.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1192) at org.hibernate.impl.QueryImpl.iterate(QueryImpl.java:46) at hib.example.EntityWithEmbeddable.main(EntityWithEmbeddable.java:44) Example code for the classes and schema to reproduce is pasted into the attachment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2112) ClassCastException in StatefulPersistenceContext.getCachedDatabaseSnapshot(...)

by Aleksei Valikov (JIRA)

ClassCastException in StatefulPersistenceContext.getCachedDatabaseSnapshot(...) ------------------------------------------------------------------------------- Key: HHH-2112 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2112 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Aleksei Valikov StatefulPersistenceContext.getCachedDatabaseSnapshot(EntityKey key) causes ClassCastException when NO_ROW was put for the certain entity key. Please see the discussion here: http://forum.hibernate.org/viewtopic.php?t=959868&highlight=getcacheddata... In these situations, this method should probably return null. It is very likely since other calling methods check for the returned value to be null . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

7
15
0 / 0

[Hibernate-JIRA] Created: (HHH-2703) Investigate integration between Spring and WAS TM

by Steve Ebersole (JIRA)

Investigate integration between Spring and WAS TM ------------------------------------------------- Key: HHH-2703 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2703 Project: Hibernate3 Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3 Supposedly as a result of Spring and IBM's blood pact, Spring has tight integration with the WAS TM (not sure how that is possible since IBM continually claims that TM access is unsupported whenever this is asked in relation to Hibernate). Anyway, there may be some stuff we could use here... http://blog.interface21.com/main/2007/06/21/spring-framework-certified-on... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-742) Primary key should not be set on nullable column

by Miroslav Havram (JIRA)

Primary key should not be set on nullable column ------------------------------------------------ Key: ANN-742 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-742 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.1.GA Environment: hibernate core 3.2.6.GA Reporter: Miroslav Havram Attachments: create_scripts.zip, test_case.zip After switching to hibernate-annotations 3.3.1.GA, DDL generated for intermediate table for optional one-to-one association tries to set primary key on nullable column. Problem is that some DBMSs (e.g. MS SQL) do not allow that. Using hibernate-annotations-3.3.0.GA: create table personAddress (address_id bigint not null, person_id bigint not null, primary key (person_id)) Using hibernate-annotations-3.3.1.GA: create table personAddress (person_id bigint, address_id bigint, primary key (person_id)) Simple test case and generated DDLs are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-2124) HibernateException hidden during flush using XA with WAS6

by Ole Dalgaard (JIRA)

HibernateException hidden during flush using XA with WAS6 --------------------------------------------------------- Key: HHH-2124 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2124 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.2, 3.1.3 Environment: Hibernate 3.1.3 Oracle 10G Websphere Application Server 6 Reporter: Ole Dalgaard In an XA environment, using WebSphereExtendedJTATransactionLookup, HibernateExceptions are hidden during flush in this code in CacheSynchronization.java try { if (flush) { log.trace("automatically flushing session"); ctx.managedFlush(); } } catch (RuntimeException re) { setRollbackOnly(); throw re; } After adding some logging to CacheSynchronization.beforeCompletion I got this error message: org.hibernate.HibernateException: Illegal attempt to associate a collection with two open sessions at org.hibernate.collection.AbstractPersistentCollection.setCurrentSession(AbstractPersistentCollection.java:410) at org.hibernate.event.def.OnUpdateVisitor.processCollection(OnUpdateVisitor.java:40) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java(Compiled Code)) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java(Compiled Code)) at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java(Compiled Code)) at org.hibernate.event.def.AbstractVisitor.process(AbstractVisitor.java:123) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:267) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:216) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:93) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:502) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:494) at org.hibernate.engine.CascadingAction$5.cascade(CascadingAction.java:134) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java(Inlined Compiled Code)) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java(Compiled Code)) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java(Compiled Code)) at org.hibernate.engine.Cascade.cascade(Cascade.java(Compiled Code)) at org.hibernate.event.def.AbstractFlushingEventListener.cascadeOnFlush(AbstractFlushingEventListener.java:130) at org.hibernate.event.def.AbstractFlushingEventListener.prepareEntityFlushes(AbstractFlushingEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:65) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:985) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:333) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:60) at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter$TransactionAdapter$1.invoke(WebSphereExtendedJTATransactionLookup.java:136) at $Proxy11.beforeCompletion(Unknown Source) at com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCompletion(SynchronizationCallbackWrapper.java:65) at com.ibm.ws.Transaction.JTA.RegisteredSyncs.distributeBefore(RegisteredSyncs.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.prePrepare(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.stage1CommitProcessing(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.processCommit(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.commit(TransactionImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TranManagerImpl.commit(TranManagerImpl.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TranManagerSet.commit(TranManagerSet.java(Compiled Code)) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:716) at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:167) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:569) at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3801) at com.ibm.ws.webservices.dispatchers.ejb.WSEJBWrapper.postInvoke(WSEJBWrapper.java:153) at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.cleanupEnvironment(J2ee14EJBDispatcher.java:197) at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invoke(JAXRPCHandler.java:148) at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:64) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:225) at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:225) at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:279) at com.ibm.ws.webservices.engine.transport.http.WebServicesServlet.doPost(WebServicesServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at com.ibm.ws.webservices.engine.transport.http.WebServicesServletBase.service(WebServicesServletBase.java:341) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1282) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:673) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1804) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:84) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:469) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:408) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:101) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:566) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:619) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:952) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1039) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code)) Without modifying CacheSynchronization I only get this: WTRN0074E: Exception caught from before_completion synchronization operation: java.lang.UnsupportedOperationException at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter$TransactionAdapter.setRollbackOnly(WebSphereExtendedJTATransactionLookup.java:211) at org.hibernate.transaction.CacheSynchronization.setRollbackOnly(CacheSynchronization.java:77) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:67) at org.hibernate.transaction.WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter$TransactionAdapter$1.invoke(WebSphereExtendedJTATransactionLookup.java:136) at $Proxy11.beforeCompletion(Unknown Source) at com.ibm.ws.jtaextensions.SynchronizationCallbackWrapper.beforeCompletion(SynchronizationCallbackWrapper.java:65) at com.ibm.ws.Transaction.JTA.RegisteredSyncs.distributeBefore(RegisteredSyncs.java(Compiled Code)) at com.ibm.ws.Transaction.JTA.TransactionImpl.prePrepare(TransactionImpl.java(Compiled Code)) ..... I use these transaction settings for hibernate: <property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.WebSphereExtendedJTATransactionLookup</property> <property name="hibernate.transaction.flush_before_completion">true</property> <property name="hibernate.transaction.auto_close_session">true</property> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-778) Test hangs if an exception is thrown, due to unclosed transaction

by Juraci Paixao Krohling (JIRA)

Test hangs if an exception is thrown, due to unclosed transaction ----------------------------------------------------------------- Key: ANN-778 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-778 Project: Hibernate Annotations Issue Type: Patch Environment: Annotations from trunk on DB2 v91 Reporter: Juraci Paixao Krohling Attachments: ANN-778.diff The test EmbeddedGenericsTest#testWorksWithGenericCollectionOfElements fails on DB2 v91, and the transaction which was started in the "setup" method blocks the execution of any other SQL Statement sent to the server. Thus, the tests needs to be enclosed by a try/catch to issue a rollback in case of failure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3350) Error in creating Schema update script: if exist a view in Oracle db and exist a class with @Entity for this, then raises the "ORA-01702: a view is not appropriate here" exception

by Béla Berecz (JIRA)

Error in creating Schema update script: if exist a view in Oracle db and exist a class with @Entity for this, then raises the "ORA-01702: a view is not appropriate here" exception ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3350 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Béla Berecz (sorry for my bad english) When deploying: 16:28:03,737 INFO [SchemaUpdate] Running hbm2ddl schema update 16:28:03,737 INFO [SchemaUpdate] fetching database metadata 16:28:04,128 INFO [SchemaUpdate] updating schema ... 16:28:59,565 WARN [JDBCExceptionReporter] SQL Error: 1702, SQLState: 42000 16:28:59,565 ERROR [JDBCExceptionReporter] ORA-01702: a view is not appropriate here 16:28:59,565 ERROR [SchemaUpdate] could not complete schema update org.hibernate.exception.SQLGrammarException: could not get table metadata: TABLE_VIEW at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:105) at org.hibernate.cfg.Configuration.generateSchemaUpdateScript(Configuration.java:954) at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:140) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:314) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:713) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy66.start(Unknown Source) at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120) at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:551) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:333) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy33.start(Unknown Source) at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:619) Caused by: java.sql.SQLException: ORA-01702: nézet itt nem fordulhat elő at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:946) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168) at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1614) at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1579) at oracle.jdbc.OracleDatabaseMetaData.getIndexInfo(OracleDatabaseMetaData.java:3485) at com.p6spy.engine.spy.P6DatabaseMetaData.getIndexInfo(P6DatabaseMetaData.java:210) at org.hibernate.tool.hbm2ddl.TableMetadata.initIndexes(TableMetadata.java:130) at org.hibernate.tool.hbm2ddl.TableMetadata.<init>(TableMetadata.java:35) at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:90) ... 150 more Problem with TableMetadata.java row 35: initIndexes(meta); I couldn't create index for view in Oracle, hence (I think) drop a SQLGrammarException when running initIndexes(meta). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2599) Inconsistent behaviour with Cascade Refresh and lazy loaded collections

by Guy Chua (JIRA)

Inconsistent behaviour with Cascade Refresh and lazy loaded collections ----------------------------------------------------------------------- Key: HHH-2599 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2599 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: 3.2.3, hsqldb/mysql Reporter: Guy Chua Attachments: cascadeTest.zip According to the specs for session.refresh(), the state of the given instance will be re-read from the database. I have a model 'Company' that has 2 lazy collections, departments and employees. Snippet of class Company -------------------------------------------------------------------- @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 Snippet of class CascadeTestRunner -------------------------------------------------------------------- public void doRefreshTest() { session = sessionFactory.openSession(); session.getTransaction().begin(); Company loadedCompany = (Company)session.get(Company.class, companyId); logger.debug(loadedCompany); // session.refresh(loadedCompany); // POINT A session.close(); Set<Department> loadedDepartments = loadedCompany.getDepartments(); logger.debug("TEST for LAZY DEPARTMENTS [START]"); for (Department tmpDepartment : loadedDepartments) { logger.debug(tmpDepartment); // POINT B } logger.debug("TEST for LAZY DEPARTMENTS [END]"); Set<Employee> loadedEmployees = loadedCompany.getEmployees(); logger.debug("TEST for LAZY EMPLOYEES [START]"); for (Employee tmpEmployee : loadedEmployees) { logger.debug(tmpEmployee); // POINT C } logger.debug("TEST for LAZY EMPLOYEES [END]"); } If I run the above code, Point B will give me LazyInitializationException which is the expected behavior. But if i uncomment POINT A, the LazyInitializationException happens at POINT C instead of POINT B. Why should POINT B pass and POINT C fail? Furthermore, with POINT A still uncommented and when I swap the position of POINT 1 with POINT 2, the LazyInitializationException happens at POINT B now. I am wondering why the position of the fields produce the exception at a different location. What happens when a lazy collection annotated with CascadeType.Refresh is refreshed? I am getting varied results, sometimes the collection is initialized, sometimes it is not. Is it supposed to cascade the refresh to lazy elements in the first place? Hope someone can shed some light on this. Test Results ------------------ 1. LazyInitializationException at POINT B @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 // session.refresh(loadedCompany); // POINT A logger.debug(tmpDepartment); // POINT B logger.debug(tmpEmployee); // POINT C 2. LazyInitializationException at POINT C @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 session.refresh(loadedCompany); // POINT A logger.debug(tmpDepartment); // POINT B logger.debug(tmpEmployee); // POINT C 2. LazyInitializationException at POINT B when positions of POINT 1 and POINT 2 are swapped @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 2 private Set<Employee> employees; // POINT 2 @OneToMany (mappedBy="company", cascade={ CascadeType.ALL }) // POINT 1 private Set<Department> departments; // POINT 1 session.refresh(loadedCompany); // POINT A logger.debug(tmpDepartment); // POINT B logger.debug(tmpEmployee); // POINT C -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3642) EJB3 inheritance strategy TABLE_PER_CLASS does not work on HSQLDB

by Wolfgang Knauf (JIRA)

EJB3 inheritance strategy TABLE_PER_CLASS does not work on HSQLDB ----------------------------------------------------------------- Key: HHH-3642 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3642 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: JBoss 5.0GA, Java 1.6, Hypersonic 1.8.0.8 Reporter: Wolfgang Knauf Attachments: InheritanceTablePerClass.ear I use an EJB3 entity bean with inheritance strategy "TABLE_PER_CLASS": @Entity @Inheritance(strategy=InheritanceType.TABLE_PER_CLASS) public abstract class Base implements Serializable { ... When loading a list of base classes, all subclass fields are null. The union subclause in the query does not work on HSQLDB. Attached is a full EJB sample, runnable on JBoss 4.2/5.0 (project export of Eclipse 3.4/WebTools 3.0 with sources). After deploying, it can be tested by browsing to http://localhost:8080/InheritanceTablePerClassWeb/ See this output: ... Loading ALL Item: Child 1, child field 1: null Item: Child 2, child field 2: null Item: Child 3, child field 3: Field of Child3 ... Here, all childs are loaded. The fields of type "Child1" and "Child2" are null, fields of type "Child3" are filled. This is probably a duplicate of http://opensource.atlassian.com/projects/hibernate/browse/HHH-2920 The described workaround to change all NULL expressions to "cast (null as VARCHAR)" results in a working query, but I see no chance to pre-configure this query in the entity manager. I created another bug, because the impact is different (it breaks a feature of EJB3), and so I consider severity to be higher. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-41) Support BeanInfo implementation to receive property names

by Emmanuel Bernard (JIRA)

Support BeanInfo implementation to receive property names --------------------------------------------------------- Key: BVAL-41 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-41 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard Michael - Why section 3.1.2 requires properties to follow the JavaBeans naming convention? In many non-English speaking countries (and projects with ridiculous managers/code standards), other prefixes are used and proper BeanInfo implementations are supplied. Although it is not pretty at all, since they are following the JavaBean spec, I don't think Bean Validation shouldn't work out-of-the-box for them; Emmanuel I reused the Java Persistence wording actually and I explicitly reference the Introspector class. Do people think we should be more cautious here? Speaking for France, I've never seen a project bothering about get/is/set and BeanInfo. People happily used frenglish: getCafeAuLait() Actually I've never seen anybody from the server side bothering about BeanInfos ;) Michael I've got an interesting case for that one: in some JVM languages, another standard is used to represent properties. Let's take, for instance, Scala. In Scala, one could write a bean like: @BeanInfo class Person(var id : Long, var name : String, var surname : String) Scala already maps vars as properties creating a private var, a public getter method named like the var and a setter like var_=. Something like: private var _id : Long def id = _id def id_=(newId: Long) = _id = newId that would translate to Java methods id and id_$eq (since = cannot be used in method names). So, when one use @BeanInfo, a proper BeanInfo subclass is generated by the compiler providing that mapping. Given how popular JVM languages are getting, not following a spec in another one and causing property support in those languages to fail to work doesn't seem nice. BTW, please let the JPA EG know about his 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

17 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-82) Migrate ant build to maven2

by Hardy Ferentschik (JIRA)

Migrate ant build to maven2 --------------------------- Key: HSEARCH-82 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-82 Project: Hibernate Search Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Switch from ant to maven2 as build tool. Initally just try to build HSearch with maven. Once it works we can see if we can extract a common HibernateExt parent pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

4
10
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