Different SOAP 11/12 policy references WSDL interpretation by wsgen tool

[metro-3]

Hi everybody,
I am using NetBeans 6.7.1. I noticed that there are some important differences b/n WSDLs generated for both SOAP 11 and 12. I have one and the same source code but under different class names for both SOAP11 and SOAP12. These two WSs has identical wsit-***.xml files but with different names and binding names (i.e. corresponding to the java class names - e.g. MyWSSOAP11 and MyWSSOAP12). Here is the content of the wsit-***.xml for the SOAP 11 one:

<?xml version="1.0" encoding="UTF-8"?>
 <definitions
 xmlns="http://schemas.xmlsoap.org/wsdl/"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="EndorsingCert1EchoService" targetNamespace="http://service.jaxws.interoperability.integration.wsstack.softwareag.com/" xmlns:tns="http://service.jaxws.interoperability.integration.wsstack.softwareag.com/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsaws="http://www.w3.org/2005/08/addressing" xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy" xmlns:sc="http://schemas.sun.com/2006/03/wss/server" xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy"
 >
    <message name="echo7"/>
    <message name="echo7Response"/>
    <portType name="EndorsingCert1Echo">
        <operation name="echo7">
            <input message="tns:echo7"/>
            <output message="tns:echo7Response"/>
        </operation>
    </portType>
    <binding name="EndorsingCert1EchoPortBinding" type="tns:EndorsingCert1Echo">
        <wsp:PolicyReference URI="#EndorsingCert1EchoPortBindingPolicy"/>
        <operation name="echo7">
            <input>
                <wsp:PolicyReference URI="#EndorsingCert1EchoPortBinding_echo7_Input_Policy"/>
            </input>
            <output>
                <wsp:PolicyReference URI="#EndorsingCert1EchoPortBinding_echo7_Output_Policy"/>
            </output>
        </operation>
    </binding>
    <service name="EndorsingCert1EchoService">
        <port name="EndorsingCert1EchoPort" binding="tns:EndorsingCert1EchoPortBinding"/>
    </service>
    <wsp:Policy wsu:Id="EndorsingCert1EchoPortBindingPolicy">
        <wsp:ExactlyOne>
            <wsp:All>
                <wsaws:UsingAddressing xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/>
                <sp:SymmetricBinding>
                    <wsp:Policy>
                        <sp:ProtectionToken>
                            <wsp:Policy>
                                <sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
                                    <wsp:Policy>
                                        <sp:WssX509V3Token10/>
                                    </wsp:Policy>
                                </sp:X509Token>
                            </wsp:Policy>
                        </sp:ProtectionToken>
                        <sp:Layout>
                            <wsp:Policy>
                                <sp:Lax/>
                            </wsp:Policy>
                        </sp:Layout>
                        <sp:OnlySignEntireHeadersAndBody/>
                        <sp:AlgorithmSuite>
                            <wsp:Policy>
                                <sp:Basic128/>
                            </wsp:Policy>
                        </sp:AlgorithmSuite>
                    </wsp:Policy>
                </sp:SymmetricBinding>
                <sp:Wss11>
                    <wsp:Policy>
                        <sp:MustSupportRefKeyIdentifier/>
                        <sp:MustSupportRefIssuerSerial/>
                        <sp:MustSupportRefThumbprint/>
                        <sp:MustSupportRefEncryptedKey/>
                    </wsp:Policy>
                </sp:Wss11>
                <sp:EndorsingSupportingTokens>
                    <wsp:Policy>
                        <sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
                            <wsp:Policy>
                                <sp:WssX509V3Token10/>
                            </wsp:Policy>
                        </sp:X509Token>
                    </wsp:Policy>
                </sp:EndorsingSupportingTokens>
                <sc:KeyStore wspp:visibility="private" location="C:\Sun\AppServer\domains\domain1\config\keystore-interop-modified.jks" type="JKS" storepass="changeit" alias="xws-security-server"/>
                <sc:ValidatorConfiguration wspp:visibility="private" revocationEnabled="false"/>
            </wsp:All>
        </wsp:ExactlyOne>
    </wsp:Policy>
    <wsp:Policy wsu:Id="EndorsingCert1EchoPortBinding_echo7_Input_Policy">
        <wsp:ExactlyOne>
            <wsp:All>
                <sp:EncryptedParts>
                    <sp:Body/>
                </sp:EncryptedParts>
                <sp:SignedParts>
                    <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:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                    <sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                    <sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                </sp:SignedParts>
            </wsp:All>
        </wsp:ExactlyOne>
    </wsp:Policy>
    <wsp:Policy wsu:Id="EndorsingCert1EchoPortBinding_echo7_Output_Policy">
        <wsp:ExactlyOne>
            <wsp:All>
                <sp:EncryptedParts>
                    <sp:Body/>
                </sp:EncryptedParts>
                <sp:SignedParts>
                    <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:Header Name="AckRequested" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                    <sp:Header Name="SequenceAcknowledgement" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                    <sp:Header Name="Sequence" Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm"/>
                </sp:SignedParts>
            </wsp:All>
        </wsp:ExactlyOne>
    </wsp:Policy>
</definitions>


When generate the corresponding WSs and invoking the WSDLs I can see one important difference. In the SOAP11 one I have:

<binding name="EndorsingCert1EchoPortBinding" type="tns:EndorsingCert1Echo">
    <ns16:PolicyReference xmlns:ns16="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#EndorsingCert1EchoPortBindingPolicy"/>
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="echo7">
        <soap:operation soapAction=""/>
        <input>
            <ns17:PolicyReference xmlns:ns17="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#EndorsingCert1EchoPortBinding_echo7_Input_Policy"/>
            <soap:body use="literal"/>
        </input>
        <output>
            <ns18:PolicyReference xmlns:ns18="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#EndorsingCert1EchoPortBinding_echo7_Output_Policy"/>
            <soap:body use="literal"/>
        </output>
    </operation>
</binding>

We have PolicyReference for input/output. But when requesting the SOAP12 we have:

<binding name="EndorsingCert1EchoSOAP12PortBinding" type="tns:EndorsingCert1EchoSOAP12">
    <ns17:PolicyReference xmlns:ns17="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#EndorsingCert1EchoSOAP12PortBindingPolicy"/>
    <soap12:binding transport="http://www.w3.org/2003/05/soap/bindings/HTTP/" style="document"/>
    <operation name="echo7">
        <soap12:operation soapAction=""/>
        <input>
            <soap12:body use="literal"/>
        </input>
        <output>
            <soap12:body use="literal"/>
        </output>
    </operation>
</binding>

There are NO PolicyReference-s for the input/output subjects?

1) Why there is difference b/n the WSDLs generated for SOAP11 and SOAP12?

2) Why SOAP12 has no PolicyReference-s attached for the input/output subjects?

Thank you in advance,
Dobri
[Message sent by forum member 'kdobrik' (kdobrik@...)]

http://forums.java.net/jive/thread.jspa?messageID=370476

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[metro-3]

>
> 2) Why SOAP12 has no PolicyReference-s attached for
> the input/output subjects?

Sounds like a bug. Could you file an issue here for this:

http://www.netbeans.org/community/issues.html
[Message sent by forum member 'jdg6688' (jiandong.guo@...)]

http://forums.java.net/jive/thread.jspa?messageID=370543

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[metro-3]

Hi,
thank you for the fast answer. I am going to open an issue on November 09, Mon.. The reason about this is that currently the system is not working. when I tried to create new issue I saw:

"Note that netbeans.org website is undergoing infrastructure update at this moment and services like Issuezilla and mailing lists are not working. Also project websites except www and platform are not accessible.

All services should be available again on November 09, Mon."

Regards,
Dobri
[Message sent by forum member 'kdobrik' (kdobrik@...)]

http://forums.java.net/jive/thread.jspa?messageID=370627

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[metro-3]

Hello Dobri,

Have you filed an issue for this?

Thanks!

Jiandong
[Message sent by forum member 'jdg6688' ]

http://forums.java.net/jive/thread.jspa?messageID=371615

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...