[jboss-jira] [JBoss JIRA] Updated: (JBAS-2577) isolating Hibernate as an internal impl detail

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-2577?page=all ]

Dimitris Andreadis updated JBAS-2577:
-------------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was: JBossAS-5.0.0.Beta4)

Move to CR1.

> isolating Hibernate as an internal impl detail
> ----------------------------------------------
>
>                 Key: JBAS-2577
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2577
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Steve Ebersole
>         Assigned To: Steve Ebersole
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Currently Hibernate is used within JBossAS for EJB3 as well as the Hibernate-intg code, with plans/discussions to expand usage to JBoss Messaging and JBossMQ.  This represents Hibernate usage as an internal implementation detail
> Additionally, Hibernate is also used within JBossAS by user applications.  This represents Hibernate usage as a deployment detail.
> Currently, the two are not isolated from each other.  Thus, a user attempting to bundle Hibernate with their application is actually using the Hibernate bundled with EJB3 and/or the integration code.  This can cause problems when we have internal usage and external usage needing to rely on different releases of Hibernate.
> Need to devise a scheme to isolate the internal usages of Hibernate.  Two potential solutions:
> 1) source-level import and package renaming of Hibernate code (i.e. org.jboss.hibernate)
> 2) some form of classloader isolation

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