March 2008 - hibernate-issues - Jboss List Archives

[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

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

6
12
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

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

4
10
0 / 0

[Hibernate-JIRA] Créée: (HHH-2060) To be able to use <generator> with <composite-id>

by Xavier Brénuchon (JIRA)

To be able to use <generator> with <composite-id> ------------------------------------------------- Key: HHH-2060 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr4 Environment: Hibernate 3.x Reporter: Xavier Brénuchon Hello, This is the continuation of HB-389 We develop an application which has very strong need for performance with several tens of million recordings. Partitioning is a need. So for that, I use <composite-id>. But my primary key is not a natural key, but a real technical key : - column of partitioning for optimization of the data base - column of technical id So I need to have a generator, for exemple : <composite-id name="id" class="IdPartition"> <key-property name="org" type="string" column="ORG"/> <key-property name="id" type="long" column="ID"/> <generator class="fr.test.xavier.IdPartitionGenerator"> <param name="table">TAB_SEQ</param> <param name="column">LAST</param> </generator> </composite-id> The good news is that Hibernate can use that (HB-389). In fact, it is enough to modify the DTD to authorize <generator> in <composite-id> and it is all. The current code of Hibernate manages it very well. Is it possible that Hibernate is enriched by this functionality? -- 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

7
17
0 / 0

[Hibernate-JIRA] Created: (EJB-254) Allow DataSource overriding through createEntityManager(String, Map override)

by Emmanuel Bernard (JIRA)

Allow DataSource overriding through createEntityManager(String, Map override) ----------------------------------------------------------------------------- Key: EJB-254 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-254 Project: Hibernate Entity Manager Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.1 -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3204) core-manual-parent pom doesn't build because core-parent doesn't contain the jboss repo

by Geoffrey De Smet (JIRA)

core-manual-parent pom doesn't build because core-parent doesn't contain the jboss repo --------------------------------------------------------------------------------------- Key: HHH-3204 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3204 Project: Hibernate3 Issue Type: Bug Components: build Reporter: Geoffrey De Smet to reproduce: mv ~/.m2/repository ~/.m2/backup_local_repository cd core-parent mvn clean install cd core-manual-parent mvn clean install result ===== Reason: POM 'org.jboss.maven.plugins:maven-jdocbook-plugin' not found in repository: Unable to download the artifact from any repository org.jboss.maven.plugins:maven-jdocbook-plugin:pom:2.1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.jboss.maven.plugins:maven-jdocbook-plugin solution ======= Just add this in the core-parent pom: <repositories> <repository> <id>jboss</id> <url>http://repository.jboss.com/maven2/</url> </repository> <repository> <id>jboss-snapshot</id> <url>http://snapshots.jboss.org/maven2</url> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>false</enabled> </releases> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss</id> <url>http://repository.jboss.com/maven2/</url> </pluginRepository> </pluginRepositories> -- 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: (EJB-294) Hibernate throwing QueryException when using alias for aggregate functions in named queries

by Saravanabavagugan Vengadasundaram (JIRA)

Hibernate throwing QueryException when using alias for aggregate functions in named queries ------------------------------------------------------------------------------------------- Key: EJB-294 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-294 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.2.0.ga Environment: Hibernate 3.2 GA, Reporter: Saravanabavagugan Vengadasundaram Hibernate throwing QueryException when using alias for aggregate functions in named queries. The following query does not work: select sum(emp.salary) as totalSalary from Employee as emp select sum(emp.salary) totalSalary from Employee as emp but this works: select sum(emp.salary) from Employee as emp -- 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
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3053) Left Outer Join on Unmapped Tables

by Ravi Bala (JIRA)

Left Outer Join on Unmapped Tables ---------------------------------- Key: HHH-3053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3053 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.1 Environment: Hibernate 3, Oracle 10g Reporter: Ravi Bala I am trying to use left outer join on two unmapped tables. How is this possible in HQL? I tried to see if there is any such problem submitted already from the forums, but I could not find one. Please let me know the link if this is already discussed. Here is the problem: Table A Table B I want to use Select a.field1, b.field2 from A a left outer join B b on a.field1 = b.field1 Thanks, Ravi -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2920) Polymorphic association with explicit table_per_class strategy: properties of subclass are not retrieved by queries.

by Andrea Silva (JIRA)

Polymorphic association with explicit table_per_class strategy: properties of subclass are not retrieved by queries. -------------------------------------------------------------------------------------------------------------------- Key: HHH-2920 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2920 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Java 1.5 - Hypersonic DB - Standalone application Reporter: Andrea Silva Priority: Minor Attachments: src.zip Item class has a one-to-many association to Bid. Bid class has a subclass called CashBid (meaningless design I know, but that's not the point). If I create and save an instance of Item with an associated CashBid, when I query for items the properties defined in CashBid are not retrieved. NB Bid is not mapped as abstract. Here is a code snippet: ... // First Session Session session = sessionFactory.openSession(); Transaction transaction = session.beginTransaction(); Bid bid = new CashBid(new BigDecimal(100.0d), "euro"); Item item = new Item("pc"); Serializable bidId = session.save(bid); item.addBid(bid); session.save(item); transaction.commit(); session.close(); // Second Session session = sessionFactory.openSession(); transaction = session.beginTransaction(); //session.load(CashBid.class, bidId); Query query = session.createQuery("from Item"); List<Item> list = query.list(); for (Item item_ : list) { System.out.println(item_); } transaction.commit(); session.close(); ... The bid in the item retrieved by the query is a CashBid (that's correct) but the properties that are defined in CashBid and not in Bid are null. If I uncomment the line //session.load(CashBid.class, bidId); the problem is not there anymore. If Bid is not mapped as abstract the problem doesn't show. My apologies if I'm just missing something very obvious. Please find the source code and the mappings 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

4
5
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 March 2008