I checked out the code to use to integrate xwork/webwork with spring. I was utilizing the interceptor classes posted to the JIRA.
But I ran into an issue. It's not entirely a critical one, but just thought perhaps people should know. The issue is that when you set the property to have webwork do xml reloading, it will reload all the external-ref resolver classes as well and instantiate new ones. How does this affect the spring integration or the spring resolver? Well, the application/servlet context set in the spring resolver is done in the context listener when the web-app is first initialized. Thus, when xwork reloads the xml config, the context listener is not notified to set the servlet context again for the spring resolver, resulting in a null application context inside the resolver and thus throwing an exception for the resolver. The workaround is obviously to just disable the xml reloading for xwork. However, I am wondering if there is a better way to set the servlet context for the spring resolver than to use a context listener? Maybe have the servlet context be retrieved through WebApplicationContext.getServletContext() in the spring resolver rather than go through the context listener? Or perhaps there's a better way. Thanks, Chris ------------------------------------------------------- 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
