You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Alessio Soldano (JIRA)" <ji...@apache.org> on 2010/10/06 14:32:31 UTC
[jira] Created: (CXF-3044) Issue with optional policy alternatives
and default policy selector
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
Reporter: Alessio Soldano
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.
[jira] Resolved: (CXF-3044) Issue with optional policy alternatives
and default policy selector
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jimma resolved CXF-3044.
------------------------
Resolution: Later
Setting this to later resolution. And discuss this issue again to see if there is need to implement another dynamic alternative selector to enable wsa related interceptors depends on the inbound message.
> 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.
[jira] Commented: (CXF-3044) Issue with optional policy
alternatives and default policy selector
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921980#action_12921980 ]
jimma commented on CXF-3044:
----------------------------
Setting the MaximalAlternativeSelctor in the sever side can fix this issue. This enables the PolicyIntercetorProverder to add the wsa related interceptors to encode and populate the wsa headers.
> 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.
[jira] Assigned: (CXF-3044) Issue with optional policy alternatives
and default policy selector
Posted by "jimma (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CXF-3044) Issue with optional policy alternatives
and default policy selector
Posted by "Alessio Soldano (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated CXF-3044:
---------------------------------
Component/s: WS-* Components
> 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
>
> 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.