wsdl from server contains "new" service and binding element

[wolle <wo...@gmail.com>]

Hi,
I made the above observation when trying to populate field soapaction which
in my case was empty.
When I then tried to insert soapAction explicitly via
headers.put("SOAPAction", Arrays.asList("http://mysoapaction"));
I got an error from server "the given soapaction does not match an
operation".

I then noticed that the wsdl from server contains a second service element
with respect to the original wsdl. This one refers binding
tns:PortTypeSoapBinding which is not contained in original wsdl, either.

<service name="Service">
<port binding="tns:Binding" name="Port">
<wsdlsoap:address location="http://bla"/>
</port>
<wsp:UsagePolicy wsdl:Required="true"/>
</service>
<service name="PortTypeService">
<port binding="tns:PortTypeSoapBinding" name="PortTypePort">
<wsdlsoap:address location="http://bla"/>
</port>
</service>

The difference to original wsdl's binding tns:Binding is that in 
tns:PortTypeSoapBinding the soapActions are all empty.

<wsdlsoap:operation soapAction="" style="document"/>

soapActions in tns:Binding are populated, also action attribute of
@WebMethod annotations in generated sources.

Can anyone please explain?
Why is there a second service element referring a new binding with empty
soapactions?
I would like to work with the binding containing the proper soapActions. How
is that possible?

Regards,
Wolfgang





--
View this message in context: http://cxf.547215.n5.nabble.com/wsdl-from-server-contains-new-service-and-binding-element-tp5735029.html
Sent from the cxf-user mailing list archive at Nabble.com.