One solution would be to package all the shared classes in a .jar, and use e.g.
the PrefixDeploymentSorter in the DeploymentScanner to deploy this .jar before
the .sar ejbs
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923698#3923698
Reply to the post :
Scott,
Thanks for the quick reply, but I'm not quite sure I understand your
answer. Perhaps this isn't the proper board for this question, because this is
really a classloading question; I just happened to run into the problem when
deploying an MBean.
My goal is to have only one copy of
Dependency is not down to the level of class loading. If you read the service
mbean behavior in chapter 2 of the server guide it will be clear that the
service lifecycle notion applies well have the service is created in the jvm.
The jboss5 microcontainer will support class loader level
