|
| Using External JNDI Repositories and Resources | |
|
| ||
| TABLE | ||
|
|
|
|
| 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
Within the Enterprise Server, you can create, delete, and list resources, as well as
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:
<resources>
--stored in an external JNDI repository. The following example
--illustrates how to access a java object stored in LDAP.
--
--needs to be used to access the resource factory. property element
--corresponds to the environment applicable to the external JNDI context
Chapter 6 • JNDI Resources | 79 |