axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Illsley (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2873) WS-Addressing EndpointReference elements not getting added in the outgoing soap message
Date Wed, 09 Jan 2008 09:28:35 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Illsley resolved AXIS2-2873.
----------------------------------

       Resolution: Fixed
    Fix Version/s: nightly

This should be fixed in the latest nightly.

Fixed in r610024 and r610207

> WS-Addressing EndpointReference elements not getting added in the outgoing soap message
> ---------------------------------------------------------------------------------------
>
>                 Key: AXIS2-2873
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2873
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing
>    Affects Versions: 1.2
>         Environment: Axis2 - 1.2 on windows xp
>            Reporter: Shantanu Sen
>            Assignee: David Illsley
>             Fix For: nightly
>
>
> 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>
> ---
> It should be  mandatory to include the wsa:Metadata and wsaReferenceParameters etc from
the wsdl in outgoing call from the client. The user should not have to do this manually -
the generated stub should include these just as it includes the wsa:Action now.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message