[ https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Pangburn updated CXF-5268: -------------------------------- Attachment: DispatchImpl.java.patch This patch goes on the 2.7.6 release version of DispatchImpl.java. The full path is apache-cxf-2.7.6-src/rt/frontend/jaxws/src/main/java/org/apache/cxf/DispatchImpl.java > Automatic WS-Policy computation should be possible on Dispatch clients > without setting operation manually > --------------------------------------------------------------------------------------------------------- > > Key: CXF-5268 > URL: https://issues.apache.org/jira/browse/CXF-5268 > Project: CXF > Issue Type: Bug > Components: WS-* Components > Affects Versions: 2.7.6 > Environment: Linux > Reporter: Jesse Pangburn > Labels: Dispatch, WS-Policy, patch > Attachments: DispatchImpl.java.patch > > > If a WSDL contains a WS-Policy with separate policies on the Operation > message elements, CXF should compute the correct policy for Dispatch clients > by looking at the message content. It already does this to determine the > operation so it can compute the correct WS-Addressing values, if the Dispatch > developer does the following: > {code} > disp.getRequestContext().put("find.dispatch.operation", Boolean.TRUE); > {code} > So we're already doing that work. It's a one line fix to update the > operation at that time, so that the WS-Policy computation engine can read the > correct operation and use that to get the right set of policies from the WSDL > to mix together. I will supply that patch :-) after submitting this issue > for it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira