You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/10/28 09:02:27 UTC
[jira] Commented: (GERONIMO-513) jndi refs should result in dependencies, optionally
[ http://issues.apache.org/jira/browse/GERONIMO-513?page=comments#action_12356179 ]
David Jencks commented on GERONIMO-513:
---------------------------------------
Missed this file in initial commit:
Sending modules/web-builder/project.xml
Transmitting file data .
Committed revision 329132.
> 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
> Attachments: jndi-dependencies.diff, jndi-dependencies.diff
>
> 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