1 Reply Latest reply on Feb 11, 2008 8:09 AM by asoldano

wsconsume and soap 1.2 warning

gllambi Feb 6, 2008 11:50 AM

We are making some interoperability test between WCF and JBoss WS-Security and founded some problems while using the wsconsume tool.

The wsdl generate with WCF is this one:

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions name="EchoService"
 targetNamespace="http://tempuri.org/"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 xmlns:tns="http://tempuri.org/"
 xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
 xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
 xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"
 xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
 xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
 xmlns:wsa10="http://www.w3.org/2005/08/addressing"
 xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">
 <wsp:Policy wsu:Id="WSSEndpoint_policy">
 <wsp:ExactlyOne>
 <wsp:All>
 <sp:SymmetricBinding
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <wsp:Policy>
 <sp:ProtectionToken>
 <wsp:Policy>
 <sp:X509Token
 sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
 <wsp:Policy>
 <sp:RequireDerivedKeys />
 <sp:RequireThumbprintReference />
 <sp:WssX509V3Token10 />
 </wsp:Policy>
 </sp:X509Token>
 </wsp:Policy>
 </sp:ProtectionToken>
 <sp:AlgorithmSuite>
 <wsp:Policy>
 <sp:Basic256 />
 </wsp:Policy>
 </sp:AlgorithmSuite>
 <sp:Layout>
 <wsp:Policy>
 <sp:Strict />
 </wsp:Policy>
 </sp:Layout>
 <sp:IncludeTimestamp />
 <sp:EncryptSignature />
 <sp:OnlySignEntireHeadersAndBody />
 </wsp:Policy>
 </sp:SymmetricBinding>
 <sp:SignedSupportingTokens
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <wsp:Policy>
 <sp:UsernameToken
 sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
 <wsp:Policy>
 <sp:WssUsernameToken10 />
 </wsp:Policy>
 </sp:UsernameToken>
 </wsp:Policy>
 </sp:SignedSupportingTokens>
 <sp:Wss11
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <wsp:Policy>
 <sp:MustSupportRefKeyIdentifier />
 <sp:MustSupportRefIssuerSerial />
 <sp:MustSupportRefThumbprint />
 <sp:MustSupportRefEncryptedKey />
 </wsp:Policy>
 </sp:Wss11>
 <sp:Trust10
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <wsp:Policy>
 <sp:MustSupportIssuedTokens />
 <sp:RequireClientEntropy />
 <sp:RequireServerEntropy />
 </wsp:Policy>
 </sp:Trust10>
 <wsaw:UsingAddressing />
 </wsp:All>
 </wsp:ExactlyOne>
 </wsp:Policy>
 <wsp:Policy wsu:Id="WSSEndpoint_echoService_Input_policy">
 <wsp:ExactlyOne>
 <wsp:All>
 <sp:SignedParts
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <sp:Body />
 <sp:Header Name="To"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="From"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="FaultTo"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="ReplyTo"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="MessageID"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="RelatesTo"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="Action"
 Namespace="http://www.w3.org/2005/08/addressing" />
 </sp:SignedParts>
 <sp:EncryptedParts
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <sp:Body />
 </sp:EncryptedParts>
 </wsp:All>
 </wsp:ExactlyOne>
 </wsp:Policy>
 <wsp:Policy wsu:Id="WSSEndpoint_echoService_output_policy">
 <wsp:ExactlyOne>
 <wsp:All>
 <sp:SignedParts
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <sp:Body />
 <sp:Header Name="To"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="From"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="FaultTo"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="ReplyTo"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="MessageID"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="RelatesTo"
 Namespace="http://www.w3.org/2005/08/addressing" />
 <sp:Header Name="Action"
 Namespace="http://www.w3.org/2005/08/addressing" />
 </sp:SignedParts>
 <sp:EncryptedParts
 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
 <sp:Body />
 </sp:EncryptedParts>
 </wsp:All>
 </wsp:ExactlyOne>
 </wsp:Policy>
 <wsdl:types>
 <xsd:schema targetNamespace="http://tempuri.org/Imports">
 <xsd:import
 schemaLocation="http://192.168.32.18:8002/EchoService?xsd=xsd0"
 namespace="http://tempuri.org/" />
 <xsd:import
 schemaLocation="http://192.168.32.18:8002/EchoService?xsd=xsd1"
 namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="IEchoService_echoService_InputMessage">
 <wsdl:part name="parameters" element="tns:echoService" />
 </wsdl:message>
 <wsdl:message name="IEchoService_echoService_OutputMessage">
 <wsdl:part name="parameters" element="tns:echoServiceResponse" />
 </wsdl:message>
 <wsdl:portType name="IEchoService">
 <wsdl:operation name="echoService">
 <wsdl:input
 wsaw:Action="http://tempuri.org/IEchoService/echoService"
 message="tns:IEchoService_echoService_InputMessage" />
 <wsdl:output
 wsaw:Action="http://tempuri.org/IEchoService/echoServiceResponse"
 message="tns:IEchoService_echoService_OutputMessage" />
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="WSSEndpoint" type="tns:IEchoService">
 <wsp:PolicyReference URI="#WSSEndpoint_policy" />
 <soap12:binding
 transport="http://schemas.xmlsoap.org/soap/http" />
 <wsdl:operation name="echoService">
 <soap12:operation
 soapAction="http://tempuri.org/IEchoService/echoService"
 style="document" />
 <wsdl:input>
 <wsp:PolicyReference
 URI="#WSSEndpoint_echoService_Input_policy" />
 <soap12:body use="literal" />
 </wsdl:input>
 <wsdl:output>
 <wsp:PolicyReference
 URI="#WSSEndpoint_echoService_output_policy" />
 <soap12:body use="literal" />
 </wsdl:output>
 </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="EchoService">
 <wsdl:port name="WSSEndpoint" binding="tns:WSSEndpoint">
 <soap12:address
 location="http://192.168.32.18:8002/EchoService" />
 <wsa10:EndpointReference>
 <wsa10:Address>
 http://192.168.32.18:8002/EchoService
 </wsa10:Address>
 <Identity
 xmlns="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity">
 <KeyInfo
 xmlns="http://www.w3.org/2000/09/xmldsig#">
 <X509Data>
 <X509Certificate>
 MIIBujCCAWigAwIBAgIQwTce2y7515tNUR4Nwq1jozAJBgUrDgMCHQUAMBYxFDASBgNVBAMTC1Jvb3QgQWdlbmN5MB4XDTA4MDEzMDExMTQzMloXDTM5MTIzMTIzNTk1OVowHTEbMBkGA1UEAxMSc2VjdXJlZC1XQ0ZTZXJ2aWNlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJrkiHSOxmR2B5wt20yEO3CCqEgllT030C3THnbF7KLODf4Df0ht+ZDaif126BRMbVF+BZtnuhbPm1pzj8TUGv0HkfqWKnippLkbc/DDa7JbbOvbMRWFsQx2AiNP+3uQRrUcraCacWiolIU9kyLpBMCG0rgK16k0nFWM4QrnPspQIDAQABo0swSTBHBgNVHQEEQDA+gBAS5AktBh0dTwCNYSHcFmRjoRgwFjEUMBIGA1UEAxMLUm9vdCBBZ2VuY3mCEAY3bACqAGSKEc+41KpcNfQwCQYFKw4DAh0FAANBAAH0JbfnjGaP83CuSRn2TbV4KJ16kTEU4VXUXmrWN/kEz4YGv99xHbiWjK6GSoVMlplevkXh9caXY+r5PJbHnU0=
 </X509Certificate>
 </X509Data>
 </KeyInfo>
 </Identity>
 </wsa10:EndpointReference>
 </wsdl:port>
 </wsdl:service>
</wsdl:definitions>

When I run the wsconsume the following message appears and it doesn't generate any stubs:


[WARNING] Ignoring SOAP port "WSSEndpoint": it uses non-standard SOAP 1.2 binding.
You must specify the "-extension" option to use this binding.
 line 1 of http://192.168.32.18:8002/EchoService?wsdl

[WARNING] Service "EchoService" does not contain any usable ports. try running wsimport with -extension switch.
 line 1 of http://192.168.32.18:8002/EchoService?wsdl

wsconsume can't generate soap 1.2 client stubs?

Thanks!

Guzman

1. Re: wsconsume and soap 1.2 warning

asoldano Feb 11, 2008 8:09 AM (in response to gllambi)

I've just create a jira feature request for this: http://jira.jboss.org/jira/browse/JBWS-1990
In the mean time, valid workarounds are using the Sun's wsimport with the -extension option or manually commenting the soap 1.2 stuff from a local wsdl copy, running wsconsume and eventually restoring the original wsdl.
Actions