I have encountered what is to me a serious usability issue with XWork. I am using it deployed in a .war in Jboss, where hot redeploy greatly reduces update times during the development process. To reduce the size of the created .war files, I store the xwork/webwork jars in the JBoss server lib configuration.
The problem I have encountered is that Xwork seems to store its configuration information from xwork.xml in as static attribute in a class. Thus, if this class is not redeployed, the configuration does not change.
The only way to get around this is to include the xwork jar, the webwork jar and the velocity jar in WEB-INF/lib for every .war I create. This boosts the size of each .war from a few kb to almost a Mb. It also seems rather wasteful, given that I try to componentize my webapp into several smaller .wars.
Have I got this right? If so, and there's no workaround, I may have to go back to Struts. Great framework otherwise.
Craig
PS The static attribute seems to be configurationInstance in ConfigurationManager.
------------------------------------------------------- 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
