We are doing both. We have a customer wsdl that we want to create a client for AND mock up an implementation of the service provider.
I believe I am seeing the cxf.xml not found error in regard to the client generation AND I do have the cxf.xml file where you recommend it to be for SOAP clients. But we are creating both a client as a jar and service provider as a war from the same parent pom. Another developer started this project and chose the module organization we have in place. It may be that we need to change our strategy to have a separate customization for the client and server. The provider is supposed to be accessed via https so we have some http conduit items our cxf.xml to cover this. Your URL reference will be valuable I am sure in trying to resolve our issue. This gives me something further to go on. Jim Glen Mazza-2 wrote: > > I'm not clear if you're creating a SOAP client or web service provider. > Generally speaking, use cxf.xml only for SOAP clients; for web service > providers, unless you're doing some big-time CXF surgery, > cxf-servlet.xml or anythingelse.xml as shown in Steps #7 and #8 here is > preferable: http://www.jroller.com/gmazza/date/20080417#WFstep7 > > At any rate, for providers, the config file needs to be in the WEB-INF > folder, as shown above in step #8. For SOAP clients using Maven, the > cxf.xml should be in src/main/resources[1]. The cxf.xml (along with > everything else in resources) will then get copied to the classpath > during mvn install. > > HTH, > Glen > > [1] > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > > > 2008-06-06 jsolderitsch wrote: >> Still looking for help on this. >> > ... >> >> jsolderitsch wrote: >> > >> > I see the following in my maven console when running a build that uses >> > cxf: >> > >> > Jun 4, 2008 4:41:52 PM >> > org.springframework.context.support.AbstractApplicationContext >> > prepareRefresh >> > INFO: Refreshing >> [EMAIL PROTECTED]: >> > display name [EMAIL PROTECTED]; >> > startup date [Wed Jun 04 16:41:52 EDT 2008]; root of context hierarchy >> > Jun 4, 2008 4:41:52 PM org.apache.cxf.bus.spring.BusApplicationContext >> > getConfigResources >> > INFO: No cxf.xml configuration file detected, relying on defaults. > > ... > >> > Jim >> > >> > > > -- View this message in context: http://www.nabble.com/cxf.xml-file-not-being-picked-up-during-maven2-processing-tp17674372p17710699.html Sent from the cxf-user mailing list archive at Nabble.com.
