You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Shantanu Sen <ss...@pacbell.net> on 2007/06/28 08:23:50 UTC

Axis2-1.2 - missing WS-Addressing headers on the client call

I have deployed a service which requires WS-Addressing - here is a parrt of the WSDL

---
 <wsdl:binding name="AddressBookServiceSOAP11Binding" type="axis2:AddressBookServicePortType">
        
    <wsaw:UsingAddressing wsdl:required="true" />
        <wsdl:operation name="addEntry">
            <soap:operation soapAction="urn:addEntry" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
        </wsdl:operation>
        <wsdl:operation name="findEntry">
            <soap:operation soapAction="urn:findEntry" style="document"/>
            <wsdl:input>
                <soap:body use="literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="AddressBookService">
        <wsdl:port name="AddressBookServiceSOAP11port_http" binding="axis2:AddressBookServiceSOAP11Binding">
            http://localhost:8080/axis2/services/AddressBookService"/>
            <wsa:EndpointReference>
                    <wsa:Address>RouterService</wsa:Address>
                    <wsa:ReferenceParameters>
                        <test>hello</test>                     
                    </wsa:ReferenceParameters>
            <wsa:Metadata>
               <wsaw:ServiceName>ServiceXXX</wsaw:ServiceName>
            </wsa:Metadata>
                </wsa:EndpointReference>
        </wsdl:port>
    </wsdl:service>
--
When I generate a stub with this wsdl, I do not see any of the wsa:EndpointReference that I specify in the wsdl. I thought that the stub  should contain this and generate the content in the ws-addressing headers. Instead I only get the following headers in the outgoing call:

---
 <soapenv:Header>
        http://localhost:8070/axis2/services/AddressBookService
        <wsa:MessageID>urn:uuid:E21E2EE85BA5DDC1121183011196876</wsa:MessageID>
        <wsa:Action>urn:addEntry</wsa:Action>
    </soapenv:Header>
---

Is'nt it mandatory to include the wsa:Metadata and wsaReferenceParameters etc from the wsdl in outgoing call from the client? 

Is this a bug, or am I interpreting this incorrectly?

Thanks,
Shantanu Sen


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: Axis2-1.2 - missing WS-Addressing headers on the client call

Posted by Brian De Pradine <PR...@uk.ibm.com>.
Hello Shantanu,

Please raise a JIRA for this issue. Thanks.

[1] http://issues.apache.org/jira/browse/AXIS2

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal 246319

If you can't find the time to do it right the first time, where will you 
find the time to do it again?


Shantanu Sen <ss...@pacbell.net> wrote on 28/06/2007 07:23:50:

> I have deployed a service which requires WS-Addressing - here is a 
> parrt of the WSDL
> 
> ---
>  <wsdl:binding name="AddressBookServiceSOAP11Binding" type="axis2:
> AddressBookServicePortType">
> 
>     <wsaw:UsingAddressing wsdl:required="true" />
>         <wsdl:operation name="addEntry">
>             <soap:operation soapAction="urn:addEntry" style="document"/>
>             <wsdl:input>
>                 <soap:body use="literal"/>
>             </wsdl:input>
>         </wsdl:operation>
>         <wsdl:operation name="findEntry">
>             <soap:operation soapAction="urn:findEntry" 
style="document"/>
>             <wsdl:input>
>                 <soap:body use="literal"/>
>             </wsdl:input>
>             <wsdl:output>
>                 <soap:body use="literal"/>
>             </wsdl:output>
>         </wsdl:operation>
>     </wsdl:binding>
>     <wsdl:service name="AddressBookService">
>         <wsdl:port name="AddressBookServiceSOAP11port_http" 
> binding="axis2:AddressBookServiceSOAP11Binding">
>             http://localhost:8080/axis2/services/AddressBookService"/>
>             <wsa:EndpointReference>
>                     <wsa:Address>RouterService</wsa:Address>
>                     <wsa:ReferenceParameters>
>                         <test>hello</test> 
>                     </wsa:ReferenceParameters>
>             <wsa:Metadata>
>                <wsaw:ServiceName>ServiceXXX</wsaw:ServiceName>
>             </wsa:Metadata>
>                 </wsa:EndpointReference>
>         </wsdl:port>
>     </wsdl:service>
> --
> When I generate a stub with this wsdl, I do not see any of the wsa:
> EndpointReference that I specify in the wsdl. I thought that the 
> stub  should contain this and generate the content in the ws-
> addressing headers. Instead I only get the following headers in the 
> outgoing call:
> 
> ---
>  <soapenv:Header>
>         http://localhost:8070/axis2/services/AddressBookService
>         <wsa:MessageID>urn:uuid:
> E21E2EE85BA5DDC1121183011196876</wsa:MessageID>
>         <wsa:Action>urn:addEntry</wsa:Action>
>     </soapenv:Header>
> ---
> 
> Is'nt it mandatory to include the wsa:Metadata and 
> wsaReferenceParameters etc from the wsdl in outgoing call from the 
client? 
> 
> Is this a bug, or am I interpreting this incorrectly?
> 
> Thanks,
> Shantanu Sen
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
> 






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU