I have a service (using JSR181) whose interface uses classes from 2 additional packages. When XFire generates the WSDL, is appears to put one of the namespace prefix definitions in the wsdl:definitions element, and one in the wsdl:types element, as follows:
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:ns2="http://model.tax.services.redhat.com"; xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"; xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding"; xmlns:tns="http://tax.services.redhat.com"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; targetNamespace="http://tax.services.redhat.com";> <wsdl:types xmlns:ns1="http://model.common.redhat.com";> I suspect this is technically valid, although strangely inconsistent (both ns1 and ns2 are only referenced within the wsdl:types element), and unfortunately is causing our BPEL process manager to go haywire. Any ideas? Thanks again! Chris -- View this message in context: http://www.nabble.com/Inconsistent-WSDL-namespace-generation-t1285885.html#a3419729 Sent from the XFire - User forum at Nabble.com.
