[
https://issues.apache.org/jira/browse/ODE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749758#comment-13749758
]
Hudson commented on ODE-509:
----------------------------
SUCCESS: Integrated in ODE-1.x #395 (See
[https://builds.apache.org/job/ODE-1.x/395/])
backporting ODE-509 in order to fix a security policy regression introduced by
the upgrade to Axis 1.5.2. (vanto: rev ae56a9d08d29b0d20dfc8f49af085bf653c2027a)
* axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisServiceDispatcher.java
* axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisOperationDispatcher.java
> Encrypted body with Axis2 1.4 or higher
> ---------------------------------------
>
> Key: ODE-509
> URL: https://issues.apache.org/jira/browse/ODE-509
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 2.0
>
>
> If you're using Axis2 1.4 or higher, you cannot encrypt message bodies due to
> a regresstion in Axis2.
> Actually the Security phase fails to decrypt the body (see AXIS2-4233 for
> details) because the targeted operation is not resolved yet. But meanwhile
> the operation name is resolved base on the name of the first element in the
> body. catch-22.
> As of 02/5/2009, only ODE trunk is affectred by this issue. ODE 1.X uses
> Axis2 1.3.
> No known workaround for this issue.
--
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
