You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2017/05/04 22:07:04 UTC
[jira] [Commented] (AXIS2-4882) AxisBindingMessage effective policy
calculation adds policies in incorrect order
[ https://issues.apache.org/jira/browse/AXIS2-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997514#comment-15997514 ]
Andreas Veithen commented on AXIS2-4882:
----------------------------------------
This patch is missing a unit test.
> AxisBindingMessage effective policy calculation adds policies in incorrect order
> --------------------------------------------------------------------------------
>
> Key: AXIS2-4882
> URL: https://issues.apache.org/jira/browse/AXIS2-4882
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.6.0
> Reporter: Peter Mullins
> Attachments: AxisBindingMessage.patch
>
>
> In the calculateEffectivePolicy method in AxisBindingMessage, PolicyComponents are added in order from the most specific to the most general. This means that when they are combined by iterating over the list (e.g. for use by Rampart in RampartPolicyBuilder), service-wide policies will always override message-level ones. This order should be reversed, so that when the policies are processed in order, more specific policies will override more general ones.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org