I have now manually hacked the generated client (SIFoRPortClient.java)
to add a new SOAP 1.2 Binding, a new Endpoint, and a utility method to
expose the corresponding port - this now works.
But this means that the default client generated by WsGen is not
complete, and I have to now maintain it by hand. Hmmmm.
Cornel Masson wrote:
Hi
I am evaluating XFire vs JAX-WS (RI) as the client for an existing
gSOAP service. This service exposes two ports: one for SOAP 1.1 and
one for SOAP 1.2.
I have used XFire WsGen to generate a client. Problem is, I see no way
of addressing the TWO ports of the service - the generated client
seems to work only with the SOAP 1.1 port. How do I address the 1.2
port? And will the generated client actually work with 1.2?
Below is a summary of the WSDL that the gSOAP service defines...
<definitions name="SIFoR"...
<types>...
<message...
<message...
...
<portType name="SIFoRInterface">...
<operation...
<operation...
...
</portType>
<binding name="SIFoR" type="tns:SIFoRInterface">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<operation...
<operation...
...
</binding>
<binding name="SIFoRSoap12" type="tns:SIFoRInterface">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<operation...
<operation...
...
</binding>
<service name="SIFoRPort">
<port name="SIFoRPort" binding="tns:SIFoR">
<soap:address location="http://xxxxxxxx"/>
</port>
<port name="SIFoRSOAP12Port" binding="tns:SIFoRSoap12">
<soap12:address location="http://xxxxxxxx"/>
</port>
</service>
</definitions>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
