Amila Suriarachchi wrote:
>
>
> On 6/2/07, *Glen Daniels* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     Hi Amila!
>
>     Amila Suriarachchi wrote:
>     >     <module name="Security">
>     >        <InFlow>
>     >          <!-- Add Decrypt phase if not already present.  If it's
>     there -->
>     >          <!-- already, just confirm that it matches these rules
>     ( i.e.  -->
>     >          <!-- after
>     Transport)                                         -->
>     >          <phase name="Decrypt" after="Transport">
>     >            <handler name="DecryptionHandler" class="..."/>
>     >          </phase>
>     >          <handler name="OtherHandler" class="...">
>     >            <order phase="Dispatch"/>
>     >          </handler>
>     >        </InFlow>
>     >        ...
>     >     </module>
>     >
>     >
>     > I am not sure the practical limitations of doing this but,
>     > +1 for adding Phases in InFlow and OutFlow and placing them
>     using the
>     > phase order rules like
>     > in handlers. I belive this would allow us to develop modules as real
>     > pluggable components.
>
>     This is relatively easy to do (I've already written the code
>     once), and
>     I agree 100% this is what is needed to make Modules sufficiently...
>     well, modular. :)  This was absolutely the design center that I had in
>     mind even from the outset of the Axis2 discussions.
>
>     Essentially you have a list of Constraints - a Constraint is like "A
>     must come before B" or "A must be in Phase Q".  Whenever you deploy a
>     thing (Handler or Phase) with Constraints, you check its Constraints
>     against the current state of the ExecutionChain.  If everything is
>     either satisfied or "open" (we'll come back to this in a sec) then
>     that
>     deployment was successful.  "Open" means that one of the referents of
>     the Constraint didn't exist at the time - so for instance if we're
>     deploying "A" and it says "A before B" but there's no "B" yet, we can
>     put A in and it works.  
>
>
> As I understood We have set of phases order of which determines by the
> phase rules (eg. before, after)  and within a phase we have set of
> handlers . Agian order of the handlers within the phase is determined
> by the handler rules. (eg. before, after).
Amila , I am sorry I could not able to find the mail archives , but I
100% sure we discussed all those when we were finalizing  phase and
phase rules.

Thanks
Deepal


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to