Did you check XFireSpringServlet ? On 5/23/07, Matthew Young <[EMAIL PROTECTED]> wrote:
just getting started with XFire... have a webapp that currently through DWR loads my spring configuration via ClassPathXmlApplicationContext which means I only have to add the directory to all Spring XML files to the application classpath. would like to do the same with a webapp (deployed under the same ear) for xfire. yet when running xfire via the Spring DispatcherServlet the main Spring configuration XML file is loaded (ie. through the contextConfigLocation context) plus (as seen in the log4j logs) all child (imported) Spring XML files (service defs, hibernate, etc) but context initialization fails. likely the classloader in the applicationContext is replaced with the Servlets (rather than using the application classpath path - looks that way in the HttpServletBean code). thinking the best resolution (since i want to keep accessing Spring via the application wide classpath) is to extend the XFireServlet and force usage of ClassPathXmlApplicationContext. wondering if somebody else has gone down this road and run into other problems? / matthew -- View this message in context: http://www.nabble.com/Either-extend-XFireServlet-or-misunderstanding-Spring-WebApp-tf3804356.html#a10764931 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
