Naming (JNDI)

Page edited by Runhua Chi


Changes (2)

{excerpt:hidden=true}This page describes how the Geronimo server puts the names of JCA objects and EJBs in the JNDI namespace so that clients may access them. {excerpt}
This page describes how the Geronimo server puts the names of your Java EE Connector Architecture (JCA) objects, for example datasource and Java Messaging Service (JMS) resource groups, and Enterprise Java Beans (EJBs) in the JNDI namespace so that clients may access them. Geronimo supports all the following JNDI naming schemes:

|| Categories || naming schemes ||
| Java EE 6 naming context | java:comp/ \\
java:modle/ \\
java:app/ \\
java:global/ |
| OSGi naming context | osgi:services/ \\
osgi:servicelist/ |
| Aries naming context | aries:services/ |
| Geronimo global naming context | jca:/

{children}

Full Content

This page describes how the Geronimo server puts the names of your Java EE Connector Architecture (JCA) objects, for example datasource and Java Messaging Service (JMS) resource groups, and Enterprise Java Beans (EJBs) in the JNDI namespace so that clients may access them. Geronimo supports all the following JNDI naming schemes:

Categories naming schemes
Java EE 6 naming context java:comp/
java:modle/
java:app/
java:global/
OSGi naming context osgi:services/
osgi:servicelist/
Aries naming context aries:services/
Geronimo global naming context jca:/
  • Client JNDI Names
  • Datasource, ConnectionFactory, MDB and JPA Naming
  • EJB naming
  • Global JNDI
  • JNDI environment references
Change Notification Preferences
View Online | View Changes | Add Comment