[
https://issues.apache.org/jira/browse/AXIS2-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446441#comment-13446441
]
James Grahn commented on AXIS2-5266:
------------------------------------
This issue seems to be dependent upon #AXIS2-5267. Without a guarantee that
the ordering will be enforced, there's little point in making the means of
specifying the order more expressive.
> Axis2 phase ordering insufficiently expressive
> ----------------------------------------------
>
> Key: AXIS2-5266
> URL: https://issues.apache.org/jira/browse/AXIS2-5266
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5.4
> Reporter: James Grahn
> Labels: handler, module, phase
>
> The order element specified when inserting a handler only allows for at most
> one "before" and one "after" handler. I currently have a case wherein two
> handlers ought to be run before a third, and this proves problematic for the
> system as implemented.
> If my system relies on both A and B coming before C and D, there is no direct
> way to state this dependency. While an order might be imposed, an
> artificial order containing false dependencies is less than ideal and
> requires more configuration than direct specification.
> This change could be accomplished in a backwards compatible manner by
> allowing the existing "order" element to have children, which identify
> additional "before" and "after" rules.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
