Martin Chalupa <chalimartines <at> seznam.cz> writes:
> I don't have binding tag in wsdl and I don't connect to my methods. When I
> use SOAP 1.1 so everything is ok.
> I use netbeans and I generate client from wsdl.
> Can you help me? Where is problem?
Does anyone know solution to this problem?
I have similar kind of problem.
I am using Echo service Spring example (examples\spring) from xfire-1.2.4
release. If I add following lines to xfire-servlet.xml then XFire accepts SOAP
1.2 requests if I build request XML by hand. However XFire does not generate
binding or port elements to wsdl and thus clients depending on wsdl do not work.
<property name="createDefaultBindings" value="false" />
<property name="bindings">
<list>
<bean class="org.codehaus.xfire.spring.config.Soap12BindingBean">
<property name="transport"
value="http://www.w3.org/2003/05/soap/bindings/HTTP/"; />
<property name="allowUndefinedEndpoints" value="true" />
</bean>
</list>
</property>
If I replace Soap12BindingBean above with following Soap11BindingBean
<bean class="org.codehaus.xfire.spring.config.Soap11BindingBean">
<property name="transport"
value="http://schemas.xmlsoap.org/soap/http"; />
<property name="allowUndefinedEndpoints" value="true" />
</bean>
then XFire generates binding element to wsdl.
So the following elements appear in wsdl if I explicitly define SOAP 1.1 over
HTTP binding but corresponding elements are missing if I define SOAP 1.2 over
HTTP binding.
<wsdl:binding name="EchoHttpBinding" type="tns:EchoPortType">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="echo">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="echoRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="echoResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
and
<wsdl:port name="EchoHttpPort" binding="tns:EchoHttpBinding">
<wsdlsoap:address
location="http://localhost:9080/XFireSpringExampleWeb/EchoService"/>
</wsdl:port>
So did I do something wrong or did I miss something that should have been done
to get EchoService using SOAP 1.2 instead of SOAP 1.1 or is this a bug in XFire?
I quickly tried to search related bugs from XFire Jira but could not find any.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
