[jboss-jira] [JBoss JIRA] Commented: (JBAS-5133) Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)

[Steve Ebersole (JIRA)]

    [ 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