geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-513) jndi refs should result in dependencies, optionally
Date Mon, 29 Aug 2005 21:26:05 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-513?page=all ]

Aaron Mulder updated GERONIMO-513:
----------------------------------

    Fix Version: 1.0
    Description: 
After non-reference gbean dependencies (GERONIMO-512) are implemented, jndi refs should result
in creating these dependencies.  They need to be optional to take account of (at least) these
scenarios:

1. circular ejb references A uses B uses A.  
2. An ejb has 2 resource refs: if the first one isn't available, it tries the backup second
one.

So, the naming schema needs an optional <optional/> tag to prevent a ref from turning
into a dependency.

  was:
After non-reference gbean dependencies (GERONIMO-512) are implemented, jndi refs should result
in creating these dependencies.  They need to be optional to take account of (at least) these
scenarios:

1. circular ejb references A uses B uses A.  
2. An ejb has 2 resource refs: if the first one isn't available, it tries the backup second
one.

So, the naming schema needs an optional <optional/> tag to prevent a ref from turning
into a dependency.

    Environment: 

> jndi refs should result in dependencies, optionally
> ---------------------------------------------------
>
>          Key: GERONIMO-513
>          URL: http://issues.apache.org/jira/browse/GERONIMO-513
>      Project: Geronimo
>         Type: New Feature
>   Components: naming
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0

>
> After non-reference gbean dependencies (GERONIMO-512) are implemented, jndi refs should
result in creating these dependencies.  They need to be optional to take account of (at least)
these scenarios:
> 1. circular ejb references A uses B uses A.  
> 2. An ejb has 2 resource refs: if the first one isn't available, it tries the backup
second one.
> So, the naming schema needs an optional <optional/> tag to prevent a ref from turning
into a dependency.

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message