> I have *just now* commited a revised James.java which
> provides an attribute "confDir" this attribute is a
> string path to ~james/appas/james/conf to allow you
> to pick up config files from there.
If you would't mind, would you please apply the fix (from the other thread),
if you get to it before I do tomorrow?
> It should work, because it is exactly the same as the
> method used to get a path for the mailet/matcher
> classloaders, which do work.
Same thing. We need to avoid BlockContext.
> > Did we come to a conclusion on how to handle DB connections in Mailets?
> I suspect we may end up with "hasDBProvider()" and "getDBProvider()" so
> that DB provision is optional but allowed for containers.
Serge indicates that he wants to expose JNDI in the Mailet API to gain
access to resources. If you want to respond to that, please change the
subject. :-)
I'm not at all in favor of the particular direction being taken for this
bounce handler, but I still have more reading to do. It seems to me that it
is attempting to build a pipeline within in a mailet, rather than take
advantage of matchers, mailets and the processor pipeline. My current
belief, which still begs more reading, is that there will be good code, but
that the code related to his complex configuration is going to be wasted.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
