Right, lets get this straight, there are mailets that break the API contract by going to James for access to the component manager. And we assume other people may have some too.
Therfore anything that breaks this will break existing code. However I have managed to re-write Mailet API and James and some of the mailets, to remove this "backdoor dependance" So the problem is now no longer James, but whatever external Mailets exist that do this thing too. We are about to go for a new release, for this to happen at a reasonable pace this release has to not break the existing mailet situation. During the next cycle we can address these issues, provide the richer contracts from the Mailet API, and remove access to Avalon via the James MailetContext. This may break existing mailets, but we will at least be able to warn people and provide alternative strategies for re-writing existing functionality. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
