Peter,
We are stuck with a bad situation with respect to Mailets. The somewhat
anemic Mailet API doesn't provide enough functionality to write a range of
mailets, so mailets pierce the veil into the underlying platform (James and
Avalon).
In my opinion, for this release we have to maintain compatibility with the
current set of interfaces, one way or another. For the NEXT release after,
looks like we have to bite the bullet and thrash out the Mailet v2 API so
that we know how services will be exposed.
What this means for Phoenix and Cornerstone, I can't say as I haven't spent
enough time looking them over. Perhaps we need to take a copy of the
released Phoenix and add wrappers to fix what they broke by improperly
following the deprecation pattern (by definition, deprecation does NOT break
existing code).
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
