[ http://issues.apache.org/jira/browse/AXIS2-1238?page=all ]
Bill Nagy closed AXIS2-1238.
----------------------------
Resolution: Invalid
This was addressed (at least partially -- there are still hardcoded names, but
less of them) between the time that I brought it up and when I opened the JIRA.
> org.apache.axis2.deployment.util.PhasesInfo has hard coded phase names which
> prevent the phase ordering in axis2.xml from functioning properly
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1238
> URL: http://issues.apache.org/jira/browse/AXIS2-1238
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Reporter: Bill Nagy
> Assigned To: Bill Nagy
> Priority: Critical
>
> org.apache.axis2.deployment.util.PhasesInfo has hard coded phase names (well,
> the constant equivalent of them anyways.) This makes it impossible to add
> new phases in certain cases and have the ordering during execution reflect
> what appeared in the axis2.xml file. (e.g. the change that Ruchith just made
> to add a security phase to the outflow won't work correctly, as the PhaseInfo
> class will return the Security phase as an operation-level phase and not a
> global phase, thus screwing up the execution order in AxisEngine.send(...).)
> Simply adding a new hard coded constant switch (as seems to have been done in
> the past) is not a good solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
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]
