Venkata Krishnan wrote:
Hi,
I've tried another way out of this and it works... here is a jist of what
I've done...
- During the composite loading phase itself aggregate the policies into the
child elements. This makes the component free to take over the
implementation policies since it has already given away the policies that
the child element should inherit.
- Just before an Implementation is resolved, validate the policies that have
been specified on the implementation. Upto the resolution point every
component has its own implementation model instance. Its only after
resolution that they might end up sharing an existing instance. So at this
point the validity of policies specified on the implementation is checked
and then copied over to the component.
Can you point me to the class/method where you're doing that? Thanks.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]