axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Commented: (AXIS2-2703) Global phases after Dispatch are ignored
Date Fri, 08 Jun 2007 14:16:28 GMT


Davanum Srinivas commented on AXIS2-2703:

Either we fix this for 1.3 or we mark this as won't fix. please decide.

> Global phases after Dispatch are ignored
> ----------------------------------------
>                 Key: AXIS2-2703
>                 URL:
>             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, 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:
For additional commands, e-mail:

View raw message