Noel J. Bergman wrote:
This is direction my thinking has been going, too. However, there seems to be a number of ways to achieve the per-mailet context thing.You have lost me - can you expand on something for me?The container can establish both the implementation and population of the
Context myContext = new InitialContext();
How does a container control what is in the instance myContext?
initial context. To do this per component is a bit more of an issue.
One solution involves playing with
NamingManager.setInitialContextFactoryBuilder().
You can also play aroundThe direction that I have taken this proposal is not intended to implement IOC, either. One aspect of it realises one benefit of IOC - IMHO the important one.
with classloaders. If this were really of interest, we can snarf code from
Tomcat, which supports per-webapp contexts, as I understand it.
However, my proposal wasn't an attempt to implement IoC.
Servlets don't seeAs far as I am aware, servlets have nothing to do with JNDI. Is this a recent addition to the servlet spec? (I have not written a servlet in about a year, but I wrote a fair few prior to that.)
separate contexts, and that is the model closest to the Mailet API.
ADK
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
