[jbossws-issues] [JBoss JIRA] Created: (JBWS-3149) Change CXF default MinimalAlternativeSelector to MaximalAlternative in sever side
Change CXF default MinimalAlternativeSelector to MaximalAlternative in sever side
----------------------------------------------------------------------------------
Key: JBWS-3149
URL: https://jira.jboss.org/browse/JBWS-3149
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-3.4.0.CR1
Reporter: Jim Ma
Assignee: Jim Ma
Fix For: jbossws-cxf-3.4.0
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira