Thanks very much!! This blog posting opened my eyes to the mistakes we were making in our attempt to generate client and service from the same WSDL.
I have things mostly working now -- the big breakthrough came when I fully annotated our server Impl file so that the @WebService declaration included all of: targetNamespace, portName, serviceName, and endpointInterface. My beans.xml file also needed a reference to the customer wsdl -- it didn't have one at first. Part of the problem was the developer who originally wrote this code was basing some assumptions on his xfire experiences in the past. In the end, the message about no cxf.xml file being found did not seem to matter -- it's still there. Really appreciate the help. Glen Mazza-2 wrote: > > Resending, forgot to include a link... > > 2008-06-07 Glen Mazza wrote: >> 2008-06-07 jsolderitsch wrote: >> > 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. >> > >> >> The tutorial link I gave you below uses Maven's assembly plugin, so you >> can take the JAX-WS artifacts generated by the service and reuse them >> for the client. >> >> Alternatively, you can break out the JAX-WS artifacts into a separate >> module, as here: >> >> > > http://www.jroller.com/gmazza/date/20071019 > > ... (much quoting deleted) > > -- View this message in context: http://www.nabble.com/cxf.xml-file-not-being-picked-up-during-maven2-processing-tp17674372p17740292.html Sent from the cxf-user mailing list archive at Nabble.com.
