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 "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/06/08 16:16:27 UTC
[jira] Updated: (AXIS2-2703) Global phases after Dispatch are
ignored
[ https://issues.apache.org/jira/browse/AXIS2-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2703:
------------------------------------
Priority: Blocker (was: Major)
> Global phases after Dispatch are ignored
> ----------------------------------------
>
> Key: AXIS2-2703
> URL: https://issues.apache.org/jira/browse/AXIS2-2703
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Glen Daniels
> Assignee: Glen Daniels
> Priority: Blocker
> Fix For: 1.3
>
>
> As noted by Afkham in http://www.wso2.org/jira/browse/WSAS-244, we aren't currently respecting any phases deployed in axis2.xml after Dispatch. This is because in the last line of DispatchPhase.checkPostConditions(), we *overwrite* the ExecutionChain in the MessageContext with the one we get from the operation. We should be *merging* the operation specific stuff with the original version. In other words, if we had the following EC:
> Phase1[ h1, h2 ], Dispatch[h3], Phase2[], Phase3[h4]
> ...and an operation which put handler "h5" into Phase2, we should end up with:
> Phase1[ h1, h2 ], Dispatch[h3], Phase2[h5], Phase3[h4]
> after dispatching, with the execution point at Phase2. In particular h4 should still be invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org