Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-371

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-371
    Summary: Improved structure for xxx-refs in geronimo plans
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Apache Geronimo
 Components: 
             deployment
   Versions:
             1.0-M2

   Assignee: 
   Reporter: David Jencks

    Created: Mon, 11 Oct 2004 6:19 PM
    Updated: Mon, 11 Oct 2004 6:19 PM

Description:
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 are:
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)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to