dkulp wrote: > > The GOOD news is we have a: > META-INF/cxf/cxf-all.xml > that automatically grabs all of the above. Thus, you COULD do: > > <context-param> > <param-name>contextConfigLocation</param-name> > <param-value> > classpath:META-INF/cxf/cxf-all.xml > classpath:META-INF/cxf/cxf-servlet.xml > WEB-INF/ws-beans.xml > </param-value> > </context-param> > > and pretty much get the entire thing setup just like if you did a pure > cxf-servlet.xml approach. That said, cxf-all does bring in a lot of > stuff > you may not need (just like cxf-servlet approach) so startup is slower, > memory footprint is higher, etc.... > > Dan >
Thanks Dan, two more questions if you know: 1.) Do you know why the META-INF/cxf/cxf-servlet.xml that you have listed in the context-param above is not included in cxf-all.xml? Class conflicts? also 2.) As you and Ian have said, using the configuration file WEB-INF/cxf-servlet.xml brings in all of the components of CXF, i.e., is equivalent to exporting META-INF/cxf/cxf-all.xml. What makes that automatically happen, where the components of the cxf-servlet.xml approach will equal the components in cxf-all.xml--does the cxf-servlet.xml approach import cxf-all.xml behind-the-scenes, or you manually need to add the components to the cxf-servlet.xml approach to keep the two approaches in sync? Thanks, Glen -- View this message in context: http://www.nabble.com/Need-clarification-on-cxf-servlet.xml-config-file.-tp19598828p19635558.html Sent from the cxf-user mailing list archive at Nabble.com.
