[jira] Commented: (ODE-415) support ws-security for Process services

["Alexis Midon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670987#action_12670987 ] 

Alexis Midon commented on ODE-415:
----------------------------------

 Backward compatibility warning: axis2.xml does not use ODEAxisDispatcher anymore. This class has been deleted and replaced by 2 new dispatchers: ODEAxis*Service*Dispather and ODEAxis*Operation*Dispatcher. The uptodate axis2.xml is shipped with PXE but if you have a custom axis2.xml, you need to update your file as follows:

       <!--  <handler name="ODEAxisDispatcher" class="org.apache.ode.axis2.hooks.ODEAxisDispatcher"/>  -->
       <!-- ODEAxisDispatcher is now equivalent to ODEAxisServiceDispatcher + ODEAxisOperationDispatcher -->
      <handler name="ODEAxisServiceDispatcher"
                     class="org.apache.ode.axis2.hooks.ODEAxisServiceDispatcher"/>
      <handler name="ODEAxisOperationDispatcher"
                     class="org.apache.ode.axis2.hooks.ODEAxisOperationDispatcher"/>


The main reason for that is that the Security phase needs the service to be resolved, but we need the body to resolve the operation. So if the body is encrypted, we have a catch-22.

The solution is to plsit the dispatcher into 2 distinct dispatchers. One for the service, invoked *before* the Security phase ; one for the operation, invoked *after* the Secutiry phase.

> support ws-security for Process services
> ----------------------------------------
>
>                 Key: ODE-415
>                 URL: https://issues.apache.org/jira/browse/ODE-415
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.