Hi, I don't think so. cxf.xml and cxf-servlet.xml are working for the difference level configuration. You can add the some bus level configuration in cxf.xml, and add your application level configuration in cxf-servlet.xml, such as <jaxws:endpoint> ...
If you put the <jaxws:endpoint> in the cxf.xml , you need to make sure you import the below resource for setting a right bus. <import resource="classpath:META-INF/cxf/cxf.xml"/> <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/> <import resource="classpath:META-INF/cxf/cxf-servlet.xml"/> Or you can't get the endpoint published with servlet transport. If you don't specify the cxf.xml in you class path, CXFServlet will help you to set up the bus, and you do not need to import any upper resources in your cxf-servlet.xml. BTW, If you are the SUN's Metro user, you can just use a XSLT to turn the SUN's endpoints.xml into cxf-servlet.xml. Willem. -----Original Message----- From: James Mao [mailto:[EMAIL PROTECTED] Sent: Thu 11/15/2007 14:56 To: [email protected] Subject: Re: Difference between cxf.xml and cxf-servlet.xml? Glen, I would say +1 to reduce the number of configuration files, James > Hello, > > I'm getting confused over the server-side configuration files for CXF. > When deploying a web service in a WAR file, what is the difference > between the cxf.xml config file and the cxf-servlet.xml config file? I > know the former needs to be on the classpath, and the latter is kept > directly under the WEB-INF folder--but what is the difference in those > two files' contents or purpose? > > Or, is there really no cxf.xml for the service, that cxf.xml is only to > be packaged with the client? I.e., can everything that is specified in > the cxf.xml actually be specifiable in the cxf-servlet instead, > eliminating the need for both files? > > Thanks, > Glen > > >
