1:37 p.m.
Upgrade Hibernate to 3.3.0.GA (from 3.2.4.SP1_CP01)
---------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
1:02 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=all ]
Dimitris Andreadis updated JBAS-5133:
-------------------------------------
Summary: Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01) (was: Upgrade
Hibernate to 3.3.0.GA (from 3.2.4.SP1_CP01))
Steve says we can only have a Hibernate CR for AS5 CR1.
Note that the Hibernate is dependent on a JBoss Cache 2.1.0.GA release (JBAS-5148).
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
12:24 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12403189 ]
Dimitris Andreadis commented on JBAS-5133:
------------------------------------------
I will try Hibernate 3.2.6.GA.
Any updates on 3.3.0.CR1 ?
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
12:41 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12403195 ]
Steve Ebersole commented on JBAS-5133:
--------------------------------------
I am working on the release right now
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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:08 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12403429 ]
Steve Ebersole commented on JBAS-5133:
--------------------------------------
I am running into issues with the maven release plugin.
I'd like to get you jars from a reproducible build. When is the drop dead date for me
to get you this release? Otherwise, I'll just manually build you the jars.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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:47 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12403438 ]
Dimitris Andreadis commented on JBAS-5133:
------------------------------------------
Better do it right. We have other ongoing refactorings so we have time.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
noon
New subject: [JBoss JIRA] Updated: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=all ]
Dimitris Andreadis updated JBAS-5133:
-------------------------------------
Priority: Critical (was: Major)
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
1:33 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12409647 ]
Steve Ebersole commented on JBAS-5133:
--------------------------------------
two questions dimitris:
1) are y'all using maven now for building? I am trying to figure out where to put
these jars for you. Is just in the maven repo good enough?
2) I am past the issues with the release plugin per se. I am still having issues with
generating an assembly which is what is used to create a dist bundle for upload to
sourceforge. so basically there means that currently there is a 100% chance this CR will
not simply clock over to be GA. Is that kosher for you for the time being?
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
2:46 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12409700 ]
Dimitris Andreadis commented on JBAS-5133:
------------------------------------------
AS uses our maven repository to download thirdparty dependencies, but it still uses ant
for the actual build. So the jars just need to be in the maven repo, we don't care
much how each project is built.
I see we have 2 locations for hibernate:
1) https://svn.jboss.org/repos/repository.jboss.org/maven2//org/hibernate/hi...
2) https://svn.jboss.org/repos/repository.jboss.org/maven2//hibernate/hibern...
I'm not sure which is better. AS currently uses (2) but (1) seems more correct.
For all maven build issues better ask Paul Geir on the JBoss Build forum.
CR is fine for now.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
noon
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12410967 ]
Steve Ebersole commented on JBAS-5133:
--------------------------------------
I have finally been able to do a release, and have gotten the 3.3.0.CR1 bits into the
maven repo (I use the org.hibernate groupId, no clue where the other stuff comes from).
However, the other aspect to this jira issue is to actually update the AS build to use
these new bits. No clue how to accomplish that part. I have asked Paul for some
guidance.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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:48 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=all ]
Steve Ebersole reassigned JBAS-5133:
------------------------------------
Assignee: Paul Gier (was: Steve Ebersole)
Assigning to Paul to make the necessary changes to pull that new release into AS.
Couple of points:
1) Due to splitting Hibernate out into modules, we will need to account for Hibernate
features actually utilized within the AS. AFAIK, we should only need the following 2
artifacts:
a) org.hibernate:hibernate-core
b) org.hibernate:hibernate-jbosscache2
2) a dependency on the hibernate-core artifact is going to transitively pull in a dep on
cglib/asm. should those be excluded?
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Paul Gier
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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:39 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12411391 ]
Paul Gier commented on JBAS-5133:
---------------------------------
I updated the hibernate dependency. The hibernate3 jar seems to have been replaced by
hibernate-core and hibernate-jmx. With those two jars, the build seems to run ok. I
didn't try a full testsuite, but it seems to compile and start ok.
Should any of the other core hibernate components (cache, connection, etc) be included in
the build?
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Paul Gier
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
6:13 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12411522 ]
Rajesh Rajasekaran commented on JBAS-5133:
------------------------------------------
TCK complains about a missing org/slf4j/LoggerFactory class which is a dependency on
hibernate-jbosscache. Should this also be installed?
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Paul Gier
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
9:05 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=all ]
Dimitris Andreadis reassigned JBAS-5133:
----------------------------------------
Assignee: Dimitris Andreadis (was: Paul Gier)
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
9:09 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=all ]
Dimitris Andreadis updated JBAS-5133:
-------------------------------------
Summary: Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA) (was: Upgrade Hibernate to
3.3.0.CRx (from 3.2.4.SP1_CP01))
Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA)
-----------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
9:09 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12412609 ]
Dimitris Andreadis commented on JBAS-5133:
------------------------------------------
I've included slf4j-api + slf4j-jboss-logging bridge in AS5, so that shouldn't
pose a problem anymore. (JBAS-5519)
I've also moved the build from hibernate 3.2.4.SP1 to 3.2.6.GA
We can move to hibernate 3.3.0.CR1, as soon as Emmanuel delivers the rest of the hibernate
components (HAN/HEM/HV/HSearch) that work with the lastest hibernate.
After that, we will move to hibernate-core / hibernate-jmx.
I'm not sure what other pieces we'll need, maybe hibernate-jbosscache2.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
9:15 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12412612 ]
Brian Stansberry commented on JBAS-5133:
----------------------------------------
For sure hibernate-jbosscache2 is needed. :-)
Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA)
-----------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
6:48 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA)
[ http://jira.jboss.com/jira/browse/JBAS-5133?page=all ]
Dimitris Andreadis resolved JBAS-5133.
--------------------------------------
Resolution: Done
So i've made the following upgrades:
hibernate to 3.3.0.CR1
hibernate-commons-annotations to 3.1.0.CR1
hibernate-annotations to 3.4.0.CR1
hibernate-entity-manager to 3.4.0.CR1
hibernate-validator to 3.1.0.CR1
hibernate-core and hibernate-jmx are now included with the server libs.
(note old jar hibernate.jar, new jar hibernate-core.jar)
If additional modules are needed, they would need to be added.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.6.GA)
-----------------------------------------------
Key: JBAS-5133
URL: http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
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
6550
days inactive
6686
days old
17 comments
5 participants
participants (5)
-
Brian Stansberry (JIRA) -
Dimitris Andreadis (JIRA)
-
Paul Gier (JIRA)
-
Rajesh Rajasekaran (JIRA)
-
Steve Ebersole (JIRA)