Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <21821866.1146516706659.JavaMail.jira@brutus>
Date: Mon, 1 May 2006 20:51:46 +0000 (GMT+00:00)
From: "Aaron Mulder (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-1960) Bad GBean reference isn't caught
 during deployment
In-Reply-To: <16638294.1146516586350.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-1960?page=all ]

Aaron Mulder updated GERONIMO-1960:
-----------------------------------

    Attachment: filestore.jar
                geronimo-service.xml

> Bad GBean reference isn't caught during deployment
> --------------------------------------------------
>
>          Key: GERONIMO-1960
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1960
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment, kernel
>     Versions: 1.1
>     Reporter: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1
>  Attachments: filestore.jar, geronimo-service.xml
>
> If you deploy the attached JAR and plan, it is distributed successfully but fails during startup when the GBean in the plan can't find ServerInfo.  This is not correct behavior -- we should fail during distribute if there are bad GBean references.

-- 
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