Peter,
We'll note your desire to no longer refer to JAMES as if it were *our* project. We had been careful to indicate 'contentious' or 'perfect world' (our point of view), but clearly that is not enough. It is going to confuse casual readers of this list, thus we'll not refer to MailetContext again.Now, on to the MailetContext. This has zero, zip, nada to do with the Avalon Context, Paul's desires notwithstanding. In fact, some discussions of the proper behavior of the Avalon Context (as a read-only repository of container-provided data) clearly don't seem to support the idea of implementing the MailetContext as an extension of Context.
Do *us* a favour though dude....
Once.... please differentiate between 'Avalon' (a project which is a collection of tools), 'Avalon-Framework' (a set of very reusable component interfaces), and Avalon-Framework recognising containers (such as Phoenix).
again, it is critical that a developer writing a component or set of
components that use Avalon be able to
Cheers!
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
