Hi Joachim,
I would prefer to use standard java 5 annotations for the declarative part.
If a container (James Server) wants to support declaring dependencies
using an XML descriptor this should be implementation specific.
Either way, even if this is implementation specific, I think it is
useful to even talk about possible implementations of the api we are
discussing, otherwise we risk to be too much abstract.
Stefano
Joachim Draeger wrote:
Hi!
Although I'm referring to James server I think it is the right list.
James server is somehow our reference costumer. :-)
The details of an implementation should of course be discussed on
server-dev.
I just noticed that we already have designated factories for Mailets and
Matchers!
JamesMatcherLoader and JamesMatcherLoader
I guess it is not too difficult to lookup a xml document for each Mailet
and inject dependencies via setters.
Maybe we could even use a framework which could introduce even more
flexibility.
This way we wouldn't have to declare the deps redundant in config.xml
when a Mailet is used more than once. (config.xml is also big enough :-)
Default dependencies from xml document could be overridden by directives
in config.xml to have full control.
Joachim
