Hi Damitha:
Because I think currently the phases in Axis2 is not a totally ordered
set like integers you took for your example. ie. There could be two
phases which have no binary relationship(using before, after) with each
other. But at the same time as Glen mentioned, if he want to make the
phases in axis2 a total order then it is redundant in saying
<phase name="MyNewPhase" before="phase2,phase3" flow="in,out"/>
because MyNewPhase, phase2 and phase3 should relate to each other in a
total ordering.
The only relationship (without more information) that phase2 and phase3
have here is that they must both be after MyNewPhase.
But I don't think the phases need a total ordering because we should
always be able to define a phase which have no before, after relation
ship with some other phases. That means it don't care about when it's
handers are executed in the phase order in relation to certain phases.
If you give the following constraints (all of them are "before"s but
they could just as well be reversed as "after"s)...
A before B
1 before B
B before C
B before 2
You should end up with a list in the order [A 1] B [C 2]. The order of
A and 1 doesn't matter as long as they are both before B, ditto with C
and 2 as long as they are both after B.
A before B
A before 1
B before C
B before 2
1 before 2
This could give you A 1 B C 2, A B C 1 2, A B 1 2 C, etc.
In other words, partial ordering between sets of elements connected by
constraints - (A B C) (A 1 2) (B 2) - MUST be respected, and any total
order which does so is fine.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
