jaybytez wrote: > > 1) The wsdl_first example contains a cxf-servlet.xml and > server-applicationContext.xml, while the cxf-jaxws-javafirst archetype > creates a project with a beans.xml and web.xml file. Is it an either or > approach? If you pair a Spring applicationContext.xml with a > cxf-servlet.xml, then do you not need a web.xml? I read the following: > http://cxf.apache.org/docs/configuration.html >
If you're hosting on a standalone servlet container, you'll need a WAR and a web.xml. (90% truthful statement, truthful enough.) The cxf-servlet.xml file is a Spring configuration context file, you should be able to add whatever CXF and non-CXF beans you want to it. I think there is a way in the web.xml file to give it a different name, but it's been a long time since I last did that. You can have multiple Spring context files by modifying the web.xml: http://www.jroller.com/gmazza/entry/refactoring_the_spring_mvc_web My WSDL-first tutorial: http://www.jroller.com/gmazza/entry/web_service_tutorial jaybytez wrote: > > 2) If I have multiple wars (cxf services) running on my App Server, do I > need to change any of the configuration files in the individual wars to > handle this? > I don't think so. I'm assuming you'll be placing the CXF JARs in the WEB-INF/lib of each and every WAR. YMMV otherwise. Of course, the endpoint URLs and servlet paths in the web.xml files must not conflict with each other. HTH, Glen -- View this message in context: http://cxf.547215.n5.nabble.com/Newbie-Question-web-xml-or-cxf-servlet-xml-and-multiple-wars-tp1070451p1144331.html Sent from the cxf-user mailing list archive at Nabble.com.
