geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Closed: (GERONIMO-371) Improved structure for xxx-refs in geronimo plans
Date Thu, 28 Oct 2004 02:06:32 GMT
     [ ]
David Jencks closed GERONIMO-371:

     Resolution: Fixed
    Fix Version: 1.0-M3

Implemented.  This involves extensive changes in how to use resource and other refs.  I'll
try to get some docs on the wiki.

> Improved structure for xxx-refs in geronimo plans
> -------------------------------------------------
>          Key: GERONIMO-371
>          URL:
>      Project: Apache Geronimo
>         Type: Improvement
>   Components: deployment
>     Versions: 1.0-M2
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0-M3

> In geronimo, jndi component environment references are resolved by turning some information
supplied in an ejb-link or geronimo plan element into a complete object name.  Resolving the
reference usually  consists of calling some method on the named gbean.
> Currently the "easy ways" are ejb-link in the spec dds or target-name for a resource-ref
to a connection factory.  non-link ejb-refs require you to supply the complete object name,
which is difficult and error prone.
> All the target object names are jsr77 compliant names.  
> This proposal is to have tags in the geronimo plan ref element for each component of
the jsr77 name.  Any that are not supplied can be filled in from the context.  The elements
> domain
> server
> application
> module
> type
> name
> I'm not entirely clear on whether the server attribute will allow you to specify a server
in a different vm.  If not something along these lines will be needed as well.
> I'm proposing to keep the current target-name element in case you want to specify the
entire name yourself.
> Among other things this should provide geronimo plan "ejb-link" like functionality and
simplify access to javamail and other non-connectionfactory resources (if any)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message