On Friday 05 December 2003 17:53, Jason Carreira wrote:
Actually, there is a way to do that. With JBoss 3.2.x, if you package your war inside an .ear and place the following as jboss-app.xml in the ear META-INF directory, JBoss will use a separate classloader for the application (instead of the default flat classloader).
Thanks for all your help on this issue. I have filed a JIRA issue at http://jira.opensymphony.com/secure/ViewIssue.jspa?key=XW-139
I have done the following as a workaround for the meantime:
1) Added webwork.configuration.xml.reload=true to webwork.properties
2) Packaged my .war as a .ear with the jboss-app.xml specifying a unique classloader repository in JBoss.
This seems to work, but I need to perform further testing to be sure. I am, I admit, confused as to the reason of the reload property. Why would you not want to reload the configuration. Performance reasons?
Thanks again, Craig
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
