Ales Justin wrote:
I doubt it.
EJBs are probably in your sub-deployment (x.ear/my-ejbs.jar), which belongs to root CL (as one of its roots).
So same rules should apply.
I see.
Does anyone have any ideas?
This happens with all EAR's... We can only deploy one EAR per JBoss 5.1.0.GA AS instance. Everytime two or more of them are deployed at the same time, this type of classloading issues with hibernate libs arise (all EARs have their own hibernate libs inside them, in ear/lib). Unfortunately, we need to update hibernate libs. Is there any other way to achieve the same goal?