The class scoping is according to the spec - as far as I know there is no way
around it (though the scoping does appear to be broken in 5.0 beta4, but I
would not rely on that - it should be fixed by GA).
In general the scoping is such that all classes in server/xxx/lib and
server/xxx/deploy
Class defined in war files are in a different scope from classes defined
elsewhere. Thus any attempt to instantiate class in a war from anywhere other
than inside the war will fail.
P.S. Use the code tags when posting XML content - select the content and click
the Code button.
View the
Hi Peter,
thanks for your help.
If I move the class package.Foo to foo.par entity module, the common.jar under
server/default/lib can instantiate the class.
But the package.Foo class needs to access classes defined in the web module,
and throws
java.lang.NoClassDefFoundError.
Is there a way
Another question:
how to package a lib jar into enitty par module and session ejb3 module?
Thanks
Dave
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4132028#4132028
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4132028
