According to one glassfish guy, this rule can be problematic in an OSGi env. It
seems you could have hibernate in both the lib and the app class loader and you
could end up with CCE because the same classes could be loaded by two
classloaders and conflict
Some background
http://opensource.atla
On Thu, 2010-09-16 at 07:52 -0500, Steve Ebersole wrote:
> On Thu, 2010-09-16 at 10:19 +0200, Emmanuel Bernard wrote:
> > I have a spot spot for (1). If I load an Hib class library, I use
> > hibernate-cl, if I load an app class, I use application-cl etc.
By the way I am not sure it is as simple
On Thu, 2010-09-16 at 10:19 +0200, Emmanuel Bernard wrote:
> I have a spot spot for (1). If I load an Hib class library, I use
> hibernate-cl, if I load an app class, I use application-cl etc.
> BTW what would be environment-cl?
The ClassLoader we'd use for JDBC classes. Thats the only use case
I have a spot spot for (1). If I load an Hib class library, I use hibernate-cl,
if I load an app class, I use application-cl etc.
BTW what would be environment-cl?
On 15 sept. 2010, at 15:47, Steve Ebersole wrote:
>
> We will need access to multiple ClassLoader references though to always
> be
We will need access to multiple ClassLoader references though to always
be able to DoTheRightThing. Just not sure the right "view" here. Do
we:
1) categorize these based on the role of the ClassLoader
(application-cl, hibernate-cl, environment-cl, etc)
2) categorize them based on our specific ne
