[Axis2] Why does org.apache.axis2.deployment.util.PhasesInfo have hard coded phase names?

[Bill Nagy <na...@watson.ibm.com>]

Is there a particular reason that
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.

-Bill
 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org