ianroberts wrote: > > As I understand it, the two choices when using CXF are (a) use the > Spring ContextLoaderListener to set up the application context or (b) > don't use the CLL, and instead let the CXF servlet load its own context > including beans defined in cxf-servlet.xml. In case (a) Spring needs to > be told where to find the bean definitions that make up the CXF > infrastructure (the bus, etc.), but in case (b) the context created by > the CXF servlet has these definitions imported automatically. > > The important thing is that the CXF infrastructure bean definitions have > to get into the context somehow - in case (a) this is typically done > using <import> but alternatively you could remove the imports from your > ws-beans.xml and add the corresponding resource URLs to the > contextConfigLocation parameter in web.xml, the results should be > identical. > > <context-param> > <param-name>contextConfigLocation</param-name> > <param-value> > classpath:META-INF/cxf/cxf.xml > classpath:META-INF/cxf/cxf-extension-soap.xml > classpath:META-INF/cxf/cxf-servlet.xml > WEB-INF/ws-beans.xml > </param-value> > </context-param> > > Ian >
Thanks Ian--that clarifies a lot. I'll be updating that section soon. Glen -- View this message in context: http://www.nabble.com/Need-clarification-on-cxf-servlet.xml-config-file.-tp19598828p19602024.html Sent from the cxf-user mailing list archive at Nabble.com.
