[JBoss JIRA] Created: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
12:07 a.m.
Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
---------------------------------------------------------------
Key: EJBTHREE-799
URL: http://jira.jboss.com/jira/browse/EJBTHREE-799
Project: EJB 3.0
Issue Type: Sub-task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: EJB 3.0 RC10 - FD
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
[ http://jira.jboss.com/jira/browse/EJBTHREE-799?page=all ]
Brian Stansberry updated EJBTHREE-799:
--------------------------------------
Original Estimate: 2 weeks
Remaining Estimate: 2 weeks
Estimating two weeks of effort on this, which largely involves getting the fix into
hibernate along with whatever other related JBC/Hibernate work comes out of
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernateAlignment. The actual work in
EJB3 itself is a couple of hours.
Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
---------------------------------------------------------------
Key: EJBTHREE-799
URL: http://jira.jboss.com/jira/browse/EJBTHREE-799
Project: EJB 3.0
Issue Type: Sub-task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: EJB 3.0 RC10 - FD
Original Estimate: 2 weeks
Remaining Estimate: 2 weeks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:11 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
[ http://jira.jboss.com/jira/browse/EJBTHREE-799?page=all ]
Brian Stansberry updated EJBTHREE-799:
--------------------------------------
Fix Version/s: EJB 3.0 RC11 - FD
(was: EJB 3.0 RC10 - FD)
Deferring to RC11 as haven't had chance to work with Hibernate team on this.
Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
---------------------------------------------------------------
Key: EJBTHREE-799
URL: http://jira.jboss.com/jira/browse/EJBTHREE-799
Project: EJB 3.0
Issue Type: Sub-task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: EJB 3.0 RC11 - FD
Original Estimate: 2 weeks
Remaining Estimate: 2 weeks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:45 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
[ http://jira.jboss.com/jira/browse/EJBTHREE-799?page=all ]
Carlo de Wolf updated EJBTHREE-799:
-----------------------------------
Fix Version/s: HEAD
(was: AS 5.0.0.Beta3)
Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
---------------------------------------------------------------
Key: EJBTHREE-799
URL: http://jira.jboss.com/jira/browse/EJBTHREE-799
Project: EJB 3.0
Issue Type: Sub-task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: HEAD
Original Estimate: 2 weeks
Remaining Estimate: 2 weeks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 p.m.
New subject: [JBoss JIRA] Closed: (EJBTHREE-799) Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
[ http://jira.jboss.com/jira/browse/EJBTHREE-799?page=all ]
Brian Stansberry closed EJBTHREE-799.
-------------------------------------
Fix Version/s: (was: HEAD)
Resolution: Out of Date
Doesn't really apply any more; the Hibernate 3.3 entity caching impl will completely
replace this code.
Remove EJBTHREE-798 workaround once issue is fixed in Hibernate
---------------------------------------------------------------
Key: EJBTHREE-799
URL: http://jira.jboss.com/jira/browse/EJBTHREE-799
Project: EJB 3.0
Issue Type: Sub-task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Original Estimate: 2 weeks
Remaining Estimate: 2 weeks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6091
days inactive
6631
days old
4 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Brian Stansberry (JIRA) -
Carlo de Wolf (JIRA)