[ https://issues.apache.org/jira/browse/AXIS2-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Daniels resolved AXIS2-2703. --------------------------------- Resolution: Won't Fix This actually does work - I hadn't understood that there is a separate copy of the operation-specific phases (after Dispatch) for each operation, and those copies are pre-filled from the global deployment. Therefore the later handler in the example WILL get called. No work needed. > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]