Hi Amila!
Amila Suriarachchi wrote:
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).
Right.
So lets say we have a phase rule like this,
<phase name="Decrypt" after="WrongPhaseName">
<handler name="DecryptionHandler" class="..."/>
</phase>
if the WrongPhaseName phase does not exists why shouldn't it throw an
exception?
Later some one may or may not deploy a phase as given. we can not sure.
Exactly - the trick is we should *remember* the constraint that
"Decrypt" must come after "WrongPhaseName". I think this deployment
should work fine, with no Exception. If no one ever deploys
WrongPhaseName, no problem. But if someone DOES deploy it, we notice
the open constraint, and we need to make sure WrongPhaseName gets
inserted before "Decrypt" - otherwise at that time there IS an Exception
(if another constraint would have forced WrongPhaseName to be after
Decrypt).
We want to allow people to express constraints on things that may or may
not be deployed yet, because that enables constellations of related
Modules to be developed without requiring that they all be deployed at once.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
