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 "James Grahn (Created) (JIRA)" <ji...@apache.org> on 2012/03/13 17:00:43 UTC
[jira] [Created] (AXIS2-5266) Axis2 phase ordering insufficiently
expressive
Axis2 phase ordering insufficiently expressive
----------------------------------------------
Key: AXIS2-5266
URL: https://issues.apache.org/jira/browse/AXIS2-5266
Project: Axis2
Issue Type: Bug
Affects Versions: 1.5.4
Reporter: James Grahn
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5266) Axis2 phase ordering insufficiently
expressive
Posted by "James Grahn (JIRA)" <ji...@apache.org>.
[ 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5266) Axis2 phase ordering insufficiently
expressive
Posted by "James Grahn (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Grahn updated AXIS2-5266:
-------------------------------
Component/s: kernel
Labels: handler module phase (was: handler module)
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org