You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "jimma (JIRA)" <ji...@apache.org> on 2010/10/12 13:24:33 UTC
[jira] Assigned: (CXF-3044) Issue with optional policy alternatives
and default policy selector
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jimma reassigned CXF-3044:
--------------------------
Assignee: jimma
> Issue with optional policy alternatives and default policy selector
> -------------------------------------------------------------------
>
> Key: CXF-3044
> URL: https://issues.apache.org/jira/browse/CXF-3044
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Reporter: Alessio Soldano
> Assignee: jimma
>
> When deploying an endpoint whose wsdl contract includes a policy with just an optional alternative for enabling ws-addressing, it seems the default policy selector that's used on server side is not turning on ws-addressing when getting a message that actually uses ws-addressing.
> The wsdl is like has a policy attached to the binding as follows:
> <portType name="Echo">
> <operation name="echo" parameterOrder="string1 testName">
> <input message="tns:EchoInput" wsam:Action="EchoInputAction" />
> <output message="tns:EchoOutput" wsam:Action="EchoOutputAction" />
> </operation>
> </portType>
> <binding name="EchoBinding" type="tns:Echo">
> <wsp:Policy>
> <wsam:Addressing wsp:Optional="true">
> <wsp:Policy/>
> </wsam:Addressing>
> </wsp:Policy>
> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc" />
> <operation name="echo">
> <soap:operation soapAction="" />
> <input>
> <soap:body use="literal" namespace="http://Echo.org" />
> </input>
> <output>
> <soap:body use="literal" namespace="http://Echo.org" />
> </output>
> </operation>
> </binding>
> <service name="EchoService">
> <port name="EchoPort" binding="tns:EchoBinding">
> <soap:address location="http://foo:9999/bar"/>
> </port>
> </service>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.