cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Trevor Paterson <trevor.pater...@roslin.ed.ac.uk>
Subject portnumbers in target namespaces
Date Wed, 25 Mar 2009 13:13:45 GMT

I am having problems generating client code from a WSDL, which I suspect may
be because the WSDL imports a schema which has a targetNamespace which
includes a port number.

the WSDL types:

<types>
  <xsd:schema>
    <xsd:import namespace="http://www.biomart.org:80/MartServiceSoap"
                        ="martxsd" />
  </xsd:schema>
</types>

the schema declaration:

<xs:schema
xmlns:tns="http://www.biomart.org:80/MartServiceSoap"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sawsdl="http://www.w3.org/ns/sawsdl"
targetNamespace="http://www.biomart.org:80/MartServiceSoap" version="1.0">

wsdl2java by default generates client code in the package
org.biomart._80.martservicesoap

a SOAP request generated from client code generated using wsdl2java:

   <soap:Body>
      <ns1:getRegistry xmlns:ns1="http://martservicesoap._80.biomart.org" />
   </soap:Body>

Am I naïve in thinking that xmlns:ns1 should =
"http://www.biomart.org:80/MartServiceSoap" in order to  match the schema
namespace for the service?

Is the namespace in the SOAP request made on the fly from the package name
of the code? and therefore is the “:80” insurmountable?

Is there a way to set the namespaces generated?

thanks
Trevor Paterson, Roslin Institute 
-- 
View this message in context: http://www.nabble.com/portnumbers-in-target-namespaces-tp22701556p22701556.html
Sent from the cxf-user mailing list archive at Nabble.com.


Mime
View raw message