[ 
https://issues.apache.org/jira/browse/CXF-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764476#comment-13764476
 ] 

Jesse Pangburn commented on CXF-5268:
-------------------------------------

Awesome!  From the first time I looked at this code for WS-Addressing use, I 
wondered about this whole dispatchToOperation thing.  Why not just set the 
operation itself?  I assumed there was a complicated reason and left it alone.  
Great to see you felt like it could just be ripped out altogether!  Good 
riddance hacks.
                
> 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: 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

Reply via email to