Remy Maucherat wrote: >> And internals and 'priviledged' application will get access to the >> root of this tree, and look up anything configurable or runtime >> using the 'normal' API - with no tricks with classloader/thread binding. > > That's different from the ENC, since here, you can give the component a > reference to the right context.
That's something I don't understand. Each app is supposed to get it's own DirContext, using the same name. And that's done by binding it per thread or class loader. However this DirContext may also be binded in the 'big tree' - and internal code could access all those 'enc' contexts. >> I am thinking to propose use of commons-discovery and a >> META-INF/mbeans.xml in modeler - so a jar containing tomcat modules will >> include it's onw description, and an easy mechanism to find it. > > Ok, since you have ideas, feel free to experiment ;-) Sure. Just trying to get feedback and maybe get other people interested. So far only 2 people seem interested in 'common-discovery'. I want to use it for an antlib 'experiment', but it would also help for tomcat. Something like ant's ProjectHelper hook to plug in different jndi config drivers ? Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
