Using custom resources, Using external jndi repositories and resources, Table 6–1 – Sun Microsystems GLASSFISH ENTERPRISE 820433510 User Manual
Page 79: Jndi lookups and their associated references

TABLE 6–1
JNDI Lookups and Their Associated References
JNDI Lookup Name
Associated Reference
java:comp/env
Application environment entries
java:comp/env/jdbc
JDBC DataSource resource manager connection factories
java:comp/env/ejb
EJB References
java:comp/UserTransaction
UserTransaction references
java:comp/env/mail
JavaMail Session Connection Factories
java:comp/env/url
URL Connection Factories
java:comp/env/jms
JMS Connection Factories and Destinations
java:comp/ORB
ORB instance shared across application components
Using Custom Resources
A custom resource accesses a local JNDI repository and an external resource accesses an
external JNDI repository. Both types of resources need user-specified factory class elements,
JNDI name attributes, etc. In this section, we will discuss how to configure JNDI connection
factory resources, for J2EE resources, and how to access these resources.
Within the Enterprise Server, you can create, delete, and list resources, as well as
list-jndi-entities
.
Using External JNDI Repositories and Resources
Often applications running on the Enterprise Server require access to resources stored in an
external JNDI repository. For example, generic Java objects could be stored in an LDAP server
as per the Java schema. External JNDI resource elements let users configure such external
resource repositories. The external JNDI factory must implement
javax.naming.spi.InitialContextFactory
interface.
An example of the use of an external JNDI resource is: