I should note that the aforementioned WSDL is produced by Microsoft WCF, which creates a modular WSDL. Has anyone had success in using JAX-WS binding files with those kinds of WSDLs?
--sg On Thu, Jul 8, 2010 at 1:41 PM, Scott Parkerson <[email protected]> wrote: > Greetings, all. > > I've been trying to use a JAX-WS bindings file to make my generated > objects serializable, as referenced here: > > http://markmail.org/message/aw52wgp6bdpwo5rx > > However, no matter what I do, I get this error when trying to run the > cxf-codegen-plugin in Maven: > > Could not find any node with the XPath expression: > //wsdl:definitions/wsdl:types/xs:schema > > It seems as if the cxf-codegen-plugin is only looking at the root > WSDL, not the included WSDL. The root WSDL looks like this: > > <wsdl:definitions name="FooService" > targetNamespace="http://example.com/FooSvc/";> > <wsdl:import namespace="http://tempuri.org/"; > location="https://somewhere.example.com/FooSvc/FooService.svc?wsdl=wsdl1"/> > <wsdl:types/> > <wsdl:service name="FooService"> > <wsdl:port name="BasicHttpBinding_IFooService" > binding="i0:BasicHttpBinding_IPharmacyService"> > <soap:address > location="https://somewhere.example.com/FooSvc/FooService.svc"/> > </wsdl:port> > </wsdl:service> > </wsdl:definitions> > > The root WSDL "imports" other WSDLs and XSDs, each with their own > targetNamespace. One of the imported XSDs should have the appropriate > XPath that I'm looking for, but wsdl2java complains that it doesn't. > > Has anyone else seen this problem? > > --sgp >
