You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org> on 2006/09/06 20:15:29 UTC

[jira] Updated: (GERONIMO-1960) Reject invalid GBean references at deployment time

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

Dain Sundstrom updated GERONIMO-1960:
-------------------------------------

        Summary: Reject invalid GBean references at deployment time  (was: Bad GBean reference isn't caught during deployment)
    Description: 
Invalid GBean references are not identified until the component attempts to start which is very inconvenient for users. 

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.

  was: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.

       Priority: Major  (was: Blocker)

> Reject invalid GBean references at deployment time
> --------------------------------------------------
>
>                 Key: GERONIMO-1960
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-1960
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, kernel
>    Affects Versions: 1.1
>            Reporter: Aaron Mulder
>         Assigned To: Dain Sundstrom
>             Fix For: 1.2, 1.1.1
>
>         Attachments: 1960.patch, filestore.jar, geronimo-service.xml, geronimo-service.xml, openejb-1960.patch
>
>
> Invalid GBean references are not identified until the component attempts to start which is very inconvenient for users. 
> 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