[ http://nagoya.apache.org/jira/browse/GERONIMO-513?page=comments#action_56203 ] Aaron Mulder commented on GERONIMO-513: ---------------------------------------
In the case of optional references, I would prefer to turn this into an "optional dependency" instead of not creating a dependency at all. In effect, I would like it to be the case that if the dependent resource is available, it will be started first, but if it is not available, no error will result. I'm afraid that if we generate no dependency, there's no way to achieve the "start first if present" behavior, and the optional resource may start after the application that uses it, even when both are on the list to be started. > jndi refs should result in dependencies, optionally > --------------------------------------------------- > > Key: GERONIMO-513 > URL: http://nagoya.apache.org/jira/browse/GERONIMO-513 > 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: http://nagoya.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
