Date: 2004-10-27T23:45:01
   Editor: DavidJencks <[EMAIL PROTECTED]>
   Wiki: Apache Geronimo Wiki
   Page: Naming
   URL: http://wiki.apache.org/geronimo/Naming

   no comment

New Page:

The java:comp/env naming environment of a j2ee component in geronimo is set up 
by referencing the gbeans representing the desired components through their 
jsr-77 object names, which are also the components gbean names.  The naming 
system attempts to let you specify the minimum possible about the desired 
target, while still letting you specify the entire name conveniently should you 
need to.

== ejb [local] refs. ==

 * If no ejb-link in the spec descriptor is present, and you specify nothing in 
the geronimo plan, geronimo will look in the current application for an ejb 
with the specified home and remote/localhome and local interfaces.  If there is 
exactly one choice, it will link to that.
 * If an ejb-link is present in the spec descriptor or the geronimo plan, 
geronimo split the link: <optional-path>#<name>.  If there is only one ejb with 
the given name and correct interfaces, it will be used.  Otherwise the path 
will be followed to the specified ejb module and a restricted search done there.
 * geronimo locator and target-name are supported

== resource refs ==

 * If nothing is specifed in the geronimo plan, geronimo will look in the 
current application for a connection factory of the same name as the resource 
ref name.  If not found, geronimo will look for a connection factory of the 
same name deployed in a non-application module.  Geronimo will not look in 
other applications.
 * If a resource-link is specified in the geronimo plan, it will be treated as 
a path and name: the name will be used in the same way as the 
resource-ref-name, with the optional assistance of the path in finding the 
correct module.
 * geronimo locator and target-name are supported.
 * url resource refs must be specified using the <url> element.

== resource-env-refs ==

 * If nothing is specified in the geronimo plan, geronimo will look in the 
current application for an admin object of the same name as the 
resource-env-ref-name.  If not found, geronimo will look for an admin object of 
the same name deployed in a non-application module.  Geronimo will not look in 
other applications.
 * If a message-destination-link is specified in the geronimo plan it will be 
treated as a path and name: the name will be used in the same way as the 
resource-env-ref-name with the optional assistance of the path in finding the 
correct module.
 * geronimo locator and target-name are supported.

== geronimo locators ==
A geronimo locator is a group of elements specifying the components of a jsr-77 
object name.  When interpreting a locator, any ommitted components are set to 
match the current context.
The elements are:
 * domain  ''the J2EEDomain''
 * server ''the J2EEServer''
 * application ''the J2EEApplication name or "null" if deployed as a 
non-application module.''
 * module ''the module name: the key of this property varies depending on the 
component type.''
 * type ''the j2eeType of the component''    
 * name ''the name of the component (required).''

== target-name ==
target-name can be used to explicitly specify an entire object name.

------------------------------------------------------------------------------

This is based on GERONIMO-371

Reply via email to