Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Maarten W. (JIRA) <no...@at...> - 2006-06-11 11:31:33
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=comments#action_23312 ] Maarten Winkels commented on HHH-1829: -------------------------------------- I started working on a patch to solve this issue. Cannot mark this issue as in progress. > Allow join on any property using property-ref > --------------------------------------------- > > Key: HHH-1829 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 > Project: Hibernate3 > Type: New Feature > Components: core > Versions: 3.2.0 cr1, 3.2.0.cr2 > Reporter: Maarten Winkels > > > Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Maarten W. (JIRA) <no...@at...> - 2006-06-11 11:31:33
|
Allow join on any property using property-ref
---------------------------------------------
Key: HHH-1829
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829
Project: Hibernate3
Type: New Feature
Components: core
Versions: 3.2.0 cr1, 3.2.0.cr2
Reporter: Maarten Winkels
Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 05:20:31
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-197?page=all ] Emmanuel Bernard resolved EJB-197: ---------------------------------- Resolution: Duplicate Dupe of EJB-198 > Bug in HEM synchronization registration in E-EJB3 > ------------------------------------------------- > > Key: EJB-197 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-197 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Reporter: Gavin King > Assignee: Emmanuel Bernard > > > Caused by: java.lang.RuntimeException: org.hibernate.TransactionException: Could not register synchronization > at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:274) > at org.jboss.ejb3.AbstractPool.remove(AbstractPool.java:171) > at org.jboss.ejb3.cache.NoPassivationCache.remove(NoPassivationCache.java:143) > at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:89) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:189) > at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:98) > at $Proxy65.ship(Unknown Source) > 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 com.sun.el.parser.AstValue.invoke(AstValue.java:151) > at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) > at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) > at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69) > ... 27 more > Caused by: org.hibernate.TransactionException: Could not register synchronization > at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159) > at org.hibernate.ejb.EntityManagerImpl.close(EntityManagerImpl.java:59) > at org.jboss.ejb3.stateful.StatefulBeanContext.closeExtendedPCs(StatefulBeanContext.java:285) > at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:269) > ... 48 more > Caused by: javax.transaction.RollbackException: Already marked for rollback, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1149964756546/52, BranchQual=null:1149964756546, localId=0:52] > at org.jboss.tm.TransactionImpl.checkStatus(TransactionImpl.java:2753) > at org.jboss.tm.TransactionImpl.registerSynchronization(TransactionImpl.java:1531) > at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:156) > ... 51 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 05:18:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-198?page=all ] Emmanuel Bernard resolved EJB-198: ---------------------------------- Resolution: Fixed > on em.close(), tries to register the transaction even if the transaction is marked for rollback > ----------------------------------------------------------------------------------------------- > > Key: EJB-198 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-198 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Versions: 3.2.0.cr1 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: 3.2.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 05:18:35
|
on em.close(), tries to register the transaction even if the transaction is marked for rollback
-----------------------------------------------------------------------------------------------
Key: EJB-198
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-198
Project: Hibernate Entity Manager
Type: Bug
Components: EntityManager
Versions: 3.2.0.cr1
Reporter: Emmanuel Bernard
Assigned to: Emmanuel Bernard
Fix For: 3.2.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 05:18:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-198?page=all ] Emmanuel Bernard updated EJB-198: --------------------------------- Summary: On em.close(), tries to register the transaction even if the transaction is marked for rollback (was: on em.close(), tries to register the transaction even if the transaction is marked for rollback) > On em.close(), tries to register the transaction even if the transaction is marked for rollback > ----------------------------------------------------------------------------------------------- > > Key: EJB-198 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-198 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Versions: 3.2.0.cr1 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: 3.2.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 03:52:32
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-368?page=all ] Emmanuel Bernard resolved ANN-368: ---------------------------------- Resolution: Fixed > Keywords first letter is not decapilalized > ------------------------------------------ > > Key: ANN-368 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-368 > Project: Hibernate Annotations > Type: Bug > Components: binder > Versions: 3.2.0.cr1 > Reporter: Emmanuel Bernard > Priority: Trivial > Fix For: 3.2.0 > > > This does break backward compatibility -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 03:52:32
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-367?page=all ] Emmanuel Bernard resolved ANN-367: ---------------------------------- Resolution: Fixed > Upgrade to Lucene 2.0.0 (Sylvain Vieujot) > ----------------------------------------- > > Key: ANN-367 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-367 > Project: Hibernate Annotations > Type: New Feature > Components: lucene > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 03:44:31
|
Keywords first letter is not decapilalized
------------------------------------------
Key: ANN-368
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-368
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.cr1
Reporter: Emmanuel Bernard
Priority: Trivial
Fix For: 3.2.0
This does break backward compatibility
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-11 03:42:35
|
Upgrade to Lucene 2.0.0 (Sylvain Vieujot)
-----------------------------------------
Key: ANN-367
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-367
Project: Hibernate Annotations
Type: New Feature
Components: lucene
Reporter: Emmanuel Bernard
Assigned to: Emmanuel Bernard
Priority: Minor
Fix For: 3.2.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Patrick B. (JIRA) <no...@at...> - 2006-06-10 21:30:39
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615?page=comments#action_23310 ] Patrick Burleson commented on HHH-1615: --------------------------------------- Just ran into this this other day. Seems odd since this is in the examples in Chapter 11 of the reference guide. Does it only affect PosgreSQL? > GROUP BY entity does not work > ----------------------------- > > Key: HHH-1615 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615 > Project: Hibernate3 > Type: Bug > Components: query-hql > Versions: 3.1.3 > Environment: PostgreSQL 8.1.3, Hibernate 3.1.3 > Reporter: Xavier Bugaud > > > The query : "select cat, count(*) from Cat cat group by cat" does not work. > ERROR: column "xxxx" must appear in the GROUP BY clause or be used in an aggregate function > See : > - http://forum.hibernate.org/viewtopic.php?t=953716 > - http://jira.nhibernate.org/browse/NH-528 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Gavin K. (JIRA) <no...@at...> - 2006-06-10 20:22:31
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-197?page=comments#action_23309 ] Gavin King commented on EJB-197: -------------------------------- Yes that seems to be the case - except nothing I do is able to convince E-EJB3 to use JoinableCMTTransactionFactory. I think it is hardcoded in somewhere. > Bug in HEM synchronization registration in E-EJB3 > ------------------------------------------------- > > Key: EJB-197 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-197 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Reporter: Gavin King > Assignee: Emmanuel Bernard > > > Caused by: java.lang.RuntimeException: org.hibernate.TransactionException: Could not register synchronization > at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:274) > at org.jboss.ejb3.AbstractPool.remove(AbstractPool.java:171) > at org.jboss.ejb3.cache.NoPassivationCache.remove(NoPassivationCache.java:143) > at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:89) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:189) > at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:98) > at $Proxy65.ship(Unknown Source) > 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 com.sun.el.parser.AstValue.invoke(AstValue.java:151) > at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) > at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) > at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69) > ... 27 more > Caused by: org.hibernate.TransactionException: Could not register synchronization > at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159) > at org.hibernate.ejb.EntityManagerImpl.close(EntityManagerImpl.java:59) > at org.jboss.ejb3.stateful.StatefulBeanContext.closeExtendedPCs(StatefulBeanContext.java:285) > at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:269) > ... 48 more > Caused by: javax.transaction.RollbackException: Already marked for rollback, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1149964756546/52, BranchQual=null:1149964756546, localId=0:52] > at org.jboss.tm.TransactionImpl.checkStatus(TransactionImpl.java:2753) > at org.jboss.tm.TransactionImpl.registerSynchronization(TransactionImpl.java:1531) > at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:156) > ... 51 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-10 19:52:36
|
registering a transaction marked for Rollback is illegal
--------------------------------------------------------
Key: HHH-1828
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1828
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr2
Reporter: Emmanuel Bernard
Priority: Blocker
Fix For: 3.2.0
org.hibernate.TransactionException: Could not register synchronization
at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159)
at org.hibernate.ejb.EntityManagerImpl.close(EntityManagerImpl.java:59)
at org.jboss.ejb3.stateful.StatefulBeanContext.closeExtendedPCs(StatefulBeanContext.java:285)
at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:269)
... 48 more
Caused by: javax.transaction.RollbackException: Already marked for rollback, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1149964756546/52, BranchQual=null:1149964756546, localId=0:52]
at org.jboss.tm.TransactionImpl.checkStatus(TransactionImpl.java:2753)
at org.jboss.tm.TransactionImpl.registerSynchronization(TransactionImpl.java:1531)
at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:156)
True for CMT and JTA. JoinableCMTTransaction is safe.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-10 19:22:33
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-197?page=comments#action_23308 ] Emmanuel Bernard commented on EJB-197: -------------------------------------- I believe you do not use the JoinableCMTTransactionFactory. Did you override the hibernate transaction factory in your persistence.xml (or hibernate.properties) file? What does the init logs say about the transaction factory used? > Bug in HEM synchronization registration in E-EJB3 > ------------------------------------------------- > > Key: EJB-197 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-197 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Reporter: Gavin King > Assignee: Emmanuel Bernard > > > Caused by: java.lang.RuntimeException: org.hibernate.TransactionException: Could not register synchronization > at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:274) > at org.jboss.ejb3.AbstractPool.remove(AbstractPool.java:171) > at org.jboss.ejb3.cache.NoPassivationCache.remove(NoPassivationCache.java:143) > at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:89) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98) > at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:189) > at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:98) > at $Proxy65.ship(Unknown Source) > 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 com.sun.el.parser.AstValue.invoke(AstValue.java:151) > at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) > at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) > at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69) > ... 27 more > Caused by: org.hibernate.TransactionException: Could not register synchronization > at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159) > at org.hibernate.ejb.EntityManagerImpl.close(EntityManagerImpl.java:59) > at org.jboss.ejb3.stateful.StatefulBeanContext.closeExtendedPCs(StatefulBeanContext.java:285) > at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:269) > ... 48 more > Caused by: javax.transaction.RollbackException: Already marked for rollback, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1149964756546/52, BranchQual=null:1149964756546, localId=0:52] > at org.jboss.tm.TransactionImpl.checkStatus(TransactionImpl.java:2753) > at org.jboss.tm.TransactionImpl.registerSynchronization(TransactionImpl.java:1531) > at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:156) > ... 51 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Gavin K. (JIRA) <no...@at...> - 2006-06-10 18:51:33
|
Bug in HEM synchronization registration in E-EJB3
-------------------------------------------------
Key: EJB-197
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-197
Project: Hibernate Entity Manager
Type: Bug
Components: EntityManager
Reporter: Gavin King
Assigned to: Emmanuel Bernard
Caused by: java.lang.RuntimeException: org.hibernate.TransactionException: Could not register synchronization
at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:274)
at org.jboss.ejb3.AbstractPool.remove(AbstractPool.java:171)
at org.jboss.ejb3.cache.NoPassivationCache.remove(NoPassivationCache.java:143)
at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:89)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:189)
at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:98)
at $Proxy65.ship(Unknown Source)
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 com.sun.el.parser.AstValue.invoke(AstValue.java:151)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69)
... 27 more
Caused by: org.hibernate.TransactionException: Could not register synchronization
at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:159)
at org.hibernate.ejb.EntityManagerImpl.close(EntityManagerImpl.java:59)
at org.jboss.ejb3.stateful.StatefulBeanContext.closeExtendedPCs(StatefulBeanContext.java:285)
at org.jboss.ejb3.stateful.StatefulBeanContext.remove(StatefulBeanContext.java:269)
... 48 more
Caused by: javax.transaction.RollbackException: Already marked for rollback, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=null:1149964756546/52, BranchQual=null:1149964756546, localId=0:52]
at org.jboss.tm.TransactionImpl.checkStatus(TransactionImpl.java:2753)
at org.jboss.tm.TransactionImpl.registerSynchronization(TransactionImpl.java:1531)
at org.hibernate.transaction.CMTTransaction.registerSynchronization(CMTTransaction.java:156)
... 51 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Ingo J. (JIRA) <no...@at...> - 2006-06-10 18:47:33
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1751?pa= ge=3Dcomments#action_23306 ]=20 Ingo Jobling commented on HHH-1751: ----------------------------------- I am confirming this bug. Until this is fixed, I modified my HQL by removi= ng the fetch join on "one to many" collection (resulting in n+1 selects). This seems to be the same bug as HHH-1283 ScrollableResults JoinFetch don't= set child collection correctly=E3=80=80after the second parent object > Collection corruptly loaded when join fetching and scrolling (org.hiberna= te.impl.FetchingScrollableResultsImpl) > -------------------------------------------------------------------------= -------------------------------------- > > Key: HHH-1751 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-1751 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr2 > Reporter: Maarten Winkels > Attachments: Child.java, HQLScrollFetchTest.java, Parent.java, ParentChi= ld.hbm.xml, scroll-fetch-collection.patch > > > When scrolling a query that has a jon fetch on a collection (set), the co= llection is not loaded correctly. It appears that only the first item in th= e collection is correctly loaded. > Th attached tests show this behaviour, as well as a number of orderings i= n the query to show how the collection is corruptly loaded. --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Ingo J. (JIRA) <no...@at...> - 2006-06-10 18:47:32
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1283?pa= ge=3Dcomments#action_23307 ]=20 Ingo Jobling commented on HHH-1283: ----------------------------------- I am also confirming this bug. Until this is fixed, I modified my HQL by r= emoving the fetch join on "one to many" collection (resulting in n+1 select= s). This seems to be the same bug as HHH-1751 Collection corruptly loaded when = join fetching and scrolling (org.hibernate.impl.FetchingScrollableResultsIm= pl) > ScrollableResults JoinFetch don't set child collection correctly=E3=80=80= after the second parent object > -------------------------------------------------------------------------= ---------------------- > > Key: HHH-1283 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-1283 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Environment: Hibernate 3.1 > Oracle10gR2 > Oracle JDBC Driver 10.2.0.1.0 > Sun JDK 1.5.0_06 > Spring 1.2.6 > Reporter: Masahiro Hirashima > Attachments: ScrollableCollectionFetchingTest.java, ScrollableResults.zi= p > > > ScrollableResults JoinFetch set child collection correctly at first paren= t object. > but after the second parent object, It set only the first element of a c= hild collection. > I made the following tables. > CREATE TABLE owners ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > first_name VARCHAR(30), > last_name VARCHAR(30), > address VARCHAR(255), > city VARCHAR(80), > telephone VARCHAR(20), > version NUMBER(36, 0) DEFAULT 0 > ); > CREATE TABLE types ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > name VARCHAR(80), > version NUMBER(36, 0) DEFAULT 0 > ); > CREATE TABLE pets ( > id NUMBER(36, 0) NOT NULL PRIMARY KEY, > name VARCHAR(30), > birth_date DATE, > type_id NUMBER(36, 0), > owner_id NUMBER(36, 0), > version NUMBER(36, 0) DEFAULT 0 > ); > and inserted the following data. > INSERT INTO owners VALUES (1, 'Betty', 'Davis', '638 Cardinal Ave.= ', 'Sun Prairie', '6085551749', 0); > INSERT INTO owners VALUES (2, 'Eduardo', 'Rodriquez', '2693 Commerce St.= ', 'McFarland', '6085558763', 0); > INSERT INTO pets VALUES (1, 'Leo', '2000-09-07', 1, 1, 0); > INSERT INTO pets VALUES (2, 'Basil', '2002-08-06', 2, 1, 0); > INSERT INTO pets VALUES (3, 'Rosy', '2001-04-17', 3, 2, 0); > INSERT INTO pets VALUES (4, 'Jewel', '2000-03-07', 4, 2, 0); > INSERT INTO pets VALUES (5, 'Iggy', '2000-11-30', 5, 2, 0); > INSERT INTO types VALUES (1, 'cat', 0); > INSERT INTO types VALUES (2, 'dog', 0); > INSERT INTO types VALUES (3, 'lizard', 0); > INSERT INTO types VALUES (4, 'snake', 0); > INSERT INTO types VALUES (5, 'bird', 0); > and I execute following code. > String hqlJoinFetchTest =3D=20 > "from Owner owner " + > "left outer join fetch owner.pets as pets " + > "left outer join fetch pets.type " + > "order by owner.firstName, owner.lastName"; > Query query =3D session.createQuery(hqlJoinFetchTest); > ScrollableResults cursor =3D query.scroll(); > while ( cursor.next() ) { > Owner owner =3D (Owner)cursor.get(0); > System.out.println(owner); > } > result of this code is following. > petclinic.domain.Owner@15d616e[id=3D1,version=3D0,firstName=3DBetty,lastN= ame=3DDavis, > petclinic.domain.Pet@136d9d8[id=3D2,version=3D0,name=3DBasil,birthDate= =3D2002-08-06, > petclinic.domain.PetType@1be2893[id=3D2,version=3D0,name=3Ddog] > petclinic.domain.Pet@14a75bb[id=3D1,version=3D0,name=3DLeo,birthDate=3D= 2000-09-07, > petclinic.domain.PetType@17779e3[id=3D1,version=3D0,name=3Dcat] > petclinic.domain.Owner@e3570c[id=3D2,version=3D0,firstName=3DEduardo,last= Name=3DRodriquez > petclinic.domain.Pet@167e3a5[id=3D4,version=3D0,name=3DJewel,birthDate= =3D2000-03-07, > petclinic.domain.PetType@1926e90[id=3D4,version=3D0,name=3Dsnake] > First owner object set collection collectly. > but second owner object don't set second pet object(id=3D5) and third pet= object(id=3D6). --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Gavin K. (JIRA) <no...@at...> - 2006-06-10 17:17:33
|
JTATransactionFactory.isTransactionInProgress() hides NamingException
---------------------------------------------------------------------
Key: HHH-1827
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1827
Project: Hibernate3
Type: Bug
Components: core
Reporter: Gavin King
Assigned to: Steve Ebersole
This code:
try {
ut = ( UserTransaction ) context.lookup( utName );
}
catch ( NamingException e ) {
throw new TransactionException( "Unable to locate UserTransaction to check status" );
}
Should be:
try {
ut = ( UserTransaction ) context.lookup( utName );
}
catch ( NamingException e ) {
throw new TransactionException( "Unable to locate UserTransaction to check status" , e);
}
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-10 03:26:34
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1826?page=all ] Emmanuel Bernard resolved HHH-1826: ----------------------------------- Resolution: Fixed > Built-in type for char[] -> vARCHAR Byte[] and Character[] > ---------------------------------------------------------- > > Key: HHH-1826 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1826 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > > > For Byte[] and Character[], an exception if raised if one of those is 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-10 03:26:31
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1826?page=all ] Emmanuel Bernard updated HHH-1826: ---------------------------------- Summary: Built-in type for char[] -> VARCHAR Byte[] and Character[] (was: Built-in type for char[] -> vARCHAR Byte[] and Character[]) > Built-in type for char[] -> VARCHAR Byte[] and Character[] > ---------------------------------------------------------- > > Key: HHH-1826 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1826 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > > > For Byte[] and Character[], an exception if raised if one of those is 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-10 03:17:37
|
Built-in type for char[] -> vARCHAR Byte[] and Character[]
----------------------------------------------------------
Key: HHH-1826
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1826
Project: Hibernate3
Type: New Feature
Components: core
Reporter: Emmanuel Bernard
Assigned to: Emmanuel Bernard
Priority: Minor
Fix For: 3.2.0
For Byte[] and Character[], an exception if raised if one of those is 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Geoffrey De S. (JIRA) <no...@at...> - 2006-06-09 08:58:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-318?page=comments#action_23305 ] Geoffrey De Smet commented on ANN-318: -------------------------------------- To bad about Maven 2 (!= slow Maven 1), but understandable that's its definitly not a priority. The meta-data of the hibernate jars in the central repo is good, so there is no real need trying to convince you :) But if you're ever interested, read the freely downloadable m2 book - it contains a chapter on migration from ANT. Validator really deserves it own jar (maybe even it's own JSR?), as many application that don't use a database could benefit from it, (including my exceptionhandling example in spring-richclient). But since I want to propose changing one of the spring-richclient sample from JDBC to hibernate, we 'll have to deal with the javax.persistence jar not being in the central repo anyway. Ps: Keep up the good work, hibernate-annotations is wonderful, especially the @MappedSuperclass is a big improvement over classic hibernate. > consider making validator framework truely independant of hibernate core > ------------------------------------------------------------------------ > > Key: ANN-318 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-318 > Project: Hibernate Annotations > Type: Improvement > Components: validator > Versions: 3.1beta9 > Reporter: Andreas Schildbach > > > I'd like to use the validator framework, but without pulling hibernate in as a dependency. > Currently, if I try to instantiate a ClassValidator, a org.hibernate.MappingException cannot be found. > Consequently, the validator framework could also be independent of the rest of the annotations, and be distributed in its own jar. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Alexander Z. (JIRA) <no...@at...> - 2006-06-09 08:33:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409?pa= ge=3Dcomments#action_23304 ]=20 Alexander Zynevich commented on HHH-1409: ----------------------------------------- Just my 0.02=C2=A3: It would be good if this client side jar contained no only collection\excep= tion but also evrything required to "support" proxy on client side (i.e. se= rialization of proxy, ability to call getId() on proxy without opening sess= ion). I know about hibernate-client.jar @jBoss, but it is better to have it= in hibernate project. > Packaging of Hibernate binaries > ------------------------------- > > Key: HHH-1409 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-1409 > Project: Hibernate3 > Type: Improvement > Components: build > Reporter: Markus Jessenitschnig > Priority: Minor > > > We are using Hibernate in a typical client/server environment. Up to now = we need to have the hibernate.jar file on the classpath of both JVMs becaus= e on the client side, Hibernate Exception classes as well as Collection cla= sses needs to be found at runtime. Well, it would be possible to take care,= that all exceptions are converted into application exceptions (no hibernat= e exceptions set as cause) and all collections are copied into collections = of type java.util.Collection. Obviously this will remove the need of a hibe= rnate.jar file on the client side, but the advantages of e.g. persistent co= llections are lost.=20 > To keep the size of the client side distribution small, it would be nice = to have only classes on the client side classpath which are really needed (= I'm not sure if exception and collection classes are enough). For that reas= on I would suggest to split the hibernate3.jar of the distribution into two= parts. A hibernate-common.jar which contains classes needed on the client = and the server side of the application, and a hibernate-server.jar which on= ly contains classes needed on the server side of the application. > kind regards > Markus Jessenitschnig --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-06-09 07:11:34
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1825?pa= ge=3Dcomments#action_23303 ]=20 Max Rydahl Andersen commented on HHH-1825: ------------------------------------------ add a patch and it will be done faster > Improved mesage in Exception from Table.validateColumns > ------------------------------------------------------- > > Key: HHH-1825 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-1825 > Project: Hibernate3 > Type: Improvement > Components: metamodel > Versions: 3.1.2 > Reporter: Bj=C3=B8rn Bjerkeli > Priority: Minor > > > The method validateColumns in Table throws an exception when it encounter= s a missing column. Each time I encounter this problem, I have to start the= debugger and create a breakpoint to identify the which table that has the = missing column. > So instead of: > if ( columnInfo =3D=3D null ) { > =09=09=09=09throw new HibernateException( "Missing column: " + col.getNam= e() ); > } > Add proper context to the Exception: > if ( columnInfo =3D=3D null ) { > =09=09=09=09throw new HibernateException( "Table:"+this+has " missing col= umn: " + col.getName() ); > } > This will make it trivial to identify and correct the bogus mapping or sc= hema. --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: <no...@at...> - 2006-06-09 06:54:35
|
Improved mesage in Exception from Table.validateColumns
-------------------------------------------------------
Key: HHH-1825
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH=
-1825
Project: Hibernate3
Type: Improvement
Components: metamodel =20
Versions: 3.1.2 =20
Reporter: Bj=C3=B8rn Bjerkeli
Priority: Minor
The method validateColumns in Table throws an exception when it encounters =
a missing column. Each time I encounter this problem, I have to start the d=
ebugger and create a breakpoint to identify the which table that has the mi=
ssing column.
So instead of:
if ( columnInfo =3D=3D null ) {
=09=09=09=09throw new HibernateException( "Missing column: " + col.getName(=
) );
}
Add proper context to the Exception:
if ( columnInfo =3D=3D null ) {
=09=09=09=09throw new HibernateException( "Table:"+this+has " missing colum=
n: " + col.getName() );
}
This will make it trivial to identify and correct the bogus mapping or sche=
ma.
--=20
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=
.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
93 messages has been excluded from this view by a project administrator.
