geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-513) jndi refs should result in dependencies, optionally
Date Sun, 05 Dec 2004 08:29:21 GMT
     [ ]
David Jencks commented on GERONIMO-513:

I don't understand how your proposal would work.  I can understand that you could have "needs
to be started" and "needs to exist" dependencies, but I don't quite understand a "doesn't
have to exist, but must be started if it exists".  Wouldn't this result in random start order
and stopping the bean with the dependency between the time the needed bean was created and
when it was started?

Another way to look at this is that there really isn't any way to determine if a gbean is
"available" without starting every configuration and looking.

I recommend we keep it simple and just have one kind of these dependencies, "needs to be started"

> jndi refs should result in dependencies, optionally
> ---------------------------------------------------
>          Key: GERONIMO-513
>          URL:
>      Project: Apache Geronimo
>         Type: New Feature
>   Components: naming
>     Versions: 1.0-M3
>     Reporter: David Jencks
>     Assignee: David Jencks

> 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:
If you want more information on JIRA, or have a bug to report see:

View raw message