Thanks for the reply, Hong.
I don't see anything about class-path in the ee6 tutorial, so I'm not sure
where to look for documentation on this...
So the class-path entry has to exist in the manifest for the library jar that
does the "forName"? So would this mean I have to do some jar-hacking while
packaging the ear to modify the loading jar to refer to the location of the
loaded class? What should the class-path entry look like?
I'm inferring the packaged structure should include something like this:
* App
* War
* WEB-INF
* classes (which includes class to be loaded using "forName" in the
loading.jar below)
* ...
* lib
* loading.jar (with manifest modified with class-path:
War/WEB-INF/classes)
* ...
Is there a NetBeans project setting to simplify this?
Thanks again!
-Chris
PS: This (or something very similar) seems to be discussed
here:
http://hanscappelle.blogspot.com/2010/07/ear-deployment-on-glassfish-3-vs.html
--
[Message sent by forum member 'christopherrued']
View Post: http://forums.java.net/node/809783