geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2615) Not enough info when a gbean ref can't be verified during deployment
Date Sat, 02 Dec 2006 00:59:21 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2615?page=all ]

David Jencks closed GERONIMO-2615.
----------------------------------

    Resolution: Fixed

Fixed in rev 481466 (trunk) by appending the message from the GBeanNotFoundException.

A more sophisticated mechanism might be to add more fields and info to the GBeanNotFoundException
and generate the message from that info.

Not applied to 1.2.

> Not enough info when a gbean ref can't be verified during deployment
> --------------------------------------------------------------------
>
>                 Key: GERONIMO-2615
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2615
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0, 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 2.0
>
>
> The GBeanNotFoundExceptions from Configuration.findGBean methods include info on what
went wrong (none or more than one) but the DeploymentContext.verify method doensn't report
this.  I've wasted several hours looking for the missing gbean until I realized that there
were too many.  The verify method should tell you what the problem is.

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

        

Mime
View raw message