|Home > Documentation > Creating deployment plans > Creating deployment plans for applications > Naming (JNDI) > Global JNDI|
In Geronimo 2.2 most accessible Java EE objects are bound in global JNDI automatically. Generally the names they are bound under can be adjusted if necessary by means of templates.
All J2CA objects are now bound automatically into a global jndi context. Note that these objects can only be accessed in the geronimo vm. The default locations are under jca: and use a formatting pattern of
where groupId and artifactId are from the module the J2CA object is deployed in, and the j2eeType and name are from the AbstractName or ObjectName identifying the object. The j2eeType is normally JCAManagedConnectionFactory or JCAAdminObject. Note that although this format appears to specify a gbean such as a ManagedConnectionFactoryWrapper gbean what is actually obtained from JNDI is what you get by calling the $getResource() method on this gbean, in this case a connection factory such as a DataSource. Similarly for a JCAAdminObject you are likely to get a Topic or Queue if you are working with a JMS adapter such as that for ActiveMQ.
You can customize which objects are bound and where they end up with these properties from var/config/config-substitutions.properties:
Specify a format string. "variables" are enclosed in curly brackets
and text outside these brackets is copied literally. You can use any component of the module artifact (groupId, artifactId, version, type) and any name-value pair in the object name as a variable.
will only bind DataSources and ConnectionFactories and not AdminObjects.
All session and (ejb 2.1) entity beans are bound into global jndi automatically. Session beans and entity beans will be bound automatically into a global JNDI context. An EJB's JNDI name is in the following format:
Remote interfaces can be accessed from other vms. This is documented extensively at http://cwiki.apache.org/GMOxDEV/client-jndi-names.html