Network Deployment (Distributed operating systems), v8.0 > Reference > Developer best practices
JNDI support in WAS
The product includes a name server to provide shared access to Java components, and an implementation of the javax.naming JNDI package which supports user access to the name server through the JNDI naming interface.
The product does not provide implementations for:
- javax.naming.directory or
- javax.naming.ldap packages
Also, the product does not support interfaces defined in the javax.naming.event package.
However, to provide access to LDAP servers, the development kit shipped with the product supports the Sun Microsystems implementation of:
- javax.naming.ldap and
- com.sun.jndi.ldap.LdapCtxFactory
The WAS JNDI implementation is based on the JNDI interface, and was tested with the Sun Microsystems JNDI Service Provider Interface (SPI).
The default behavior of this JNDI implementation is adequate for most users. However, users with specific requirements can control certain aspects of JNDI behavior.
Naming
Use naming
Default messaging provider queue connection factory [Settings]