[
https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessio Soldano reopened CXF-5268:
----------------------------------
Estimated Complexity: Unknown (was: Novice)
I'm sorry Dan, but the commit at
https://fisheye6.atlassian.com/changelog/cxf?cs=1521906 is causing a regression
here when using a Dispatch instance created from an EPR and with addressing
enabled (payload mode).
When calling dispatch.invoke(Source) a source with different contents [1] is
returned depending on addressing being on or off, while the response message on
the wire is the same.
When calling dispatch.invoke(Object) (hence using JAXB) a jaxb exception [2] is
thrown during unmarshalling when addressing is enabled. Again, same response
messages on the wire with addressing on and off.
[1] looks like the tags of the response wrapper are stripped off
[2]
http://jbossws.jboss.org:8180/hudson/job/CXF-CORE-AS-8.0.0-SUN-JDK-6/246/testReport/org.jboss.test.ws.jaxws.jbws2937/JBWS2937TestCase/testCreateDispatchUsingEPRAndJAXBContext/
> 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
> Assignee: Daniel Kulp
> Labels: Dispatch, WS-Policy, patch
> Fix For: 3.0.0, 2.7.7
>
> 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
