Nicola,
In terms of the Mailet API and Avalon, there are multiple independent
issues. The most serious of which is that there seems to be little
willingness to implement IoC in the Mailet API. The preferred approach is
the pull model. I am proposing that we use JNDI resources as a general
solution to the problem of extending resources to matchers and mailets. The
basic idea is that you get resources by doing a lookup, which matches well
with the current plans for Avalon. The primary difference is the context
handling.
Your idea that James could detect and support additional lifecycle methods
is something that we can consider as needed. First, though, I'd like to
ensure that we have a really good Mailet Specification for portable Mailet
containers. Note that I said "specification", not API. JNDI isn't part of
the API, anymore than it is part of the Servlet API. But both the Mailet
and Servlet Specifications would talk about how to use JNDI resources in
those containers.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
