Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 82703 invoked from network); 5 Dec 2004 07:56:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 5 Dec 2004 07:56:27 -0000 Received: (qmail 38645 invoked by uid 500); 5 Dec 2004 07:56:22 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 38612 invoked by uid 500); 5 Dec 2004 07:56:22 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 38590 invoked by uid 99); 5 Dec 2004 07:56:22 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from exchange.sun.com (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Sat, 04 Dec 2004 23:56:22 -0800 Received: (qmail 25832 invoked from network); 5 Dec 2004 07:56:20 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 5 Dec 2004 07:56:20 -0000 Message-ID: <1549635837.1102233380743.JavaMail.apache@nagoya> Date: Sat, 4 Dec 2004 23:56:20 -0800 (PST) From: "David Jencks (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-513) jndi refs should result in dependencies, optionally Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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 Assigned to: 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 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