Hey I have now put the updated JNP (JNDI provider) in CVS. The most significant change is that the java: implementation is now not component local. Instead, java: can be used by all components in the server to do VM-local bindings (i.e. things that should not be seen by remote clients, such as TransactionManager, JDBC pools, etc.). I expect all of the components affected to update their use of JNDI shortly. I have also added support for component local "java:comp" namespace. Yes, "java:comp" is component local, and not only "java:comp/env", as defined in Da Specs(tm). This change is transparent to app developers, but source readers may note that this affected the setup of the "java:comp/env" namespace in Container.java. It is now much simpler :-) One interesting thing about the new java:comp namespace is that it is pretty automatic. What it does is to simply provide a namespace for each ContextClassLoader that it sees. This means that it should be trivial to use this for Tomcat as well, since all that has to be done in Tomcat is bind into the "java:comp" namespace: it does not have to know anything about the underlying implementation! See Container.java for example on how to use the "java:comp" namespace. If there are any questions on this let me know. Oh, and one more thing. The "java:comp" namespace is implemented as a federated namespace, as defined in the JNDI specs. I had to update JNP to support federated naming. This also means that you can pretty easily bind in your own custom namespaces in JNP now. See JNDI SPI spec for detail: http://java.sun.com/j2se/1.3/docs/guide/jndi/spec/spi/jndispi.fm.html#1003676 and specifically: http://java.sun.com/j2se/1.3/docs/guide/jndi/spec/spi/jndispi.fm.html#1003761 regards, Rickard -- Rickard �berg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
