Hi Kristofer,
As a stand-alone API, JNDI certainly provides the capability to define a naming service that
supports binding. However, in Java EE, there is no requirement that such a global naming
service be available. Most Java EE implementations do in fact have an underlying global
naming service but that's an implementation detail. There is nothing in Java EE that says an
application should assume it can bind an object to a global naming service provided by the
container. That's why it's not part of the Java EE programming model and not portable.
--ken
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=224024