geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-581) Deployer unaware of org.tranql.ql.QueryException
Date Sun, 13 Feb 2005 16:23:14 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-581?page=history ]

Aaron Mulder updated GERONIMO-581:
----------------------------------

    Description: 
When an EJB deployment throws a TranQL QueryException, the deployer just gets a big stack
trace for a ClassNotFoundException, concealing the actual exception.  We usually put exceptions
of this nature in Geronimo/Common.  It looks like in this case we wrap the TranQL exception
in a Geronimo DeploymentException before throwing it, but the Geronimo exception uses the
TranQL exception as a chained exception (enough to cause the CNFE) and does not itself contain
the error message.  So the DeploymentException should have no chained exception, and should
itself contain the error message.


  was:
When an EJB deployment throws a TranQL QueryException, the deployer just gets a big stack
trace for a ClassNotFoundException, concealing the actual exception.  We usually put exceptions
of this nature in Geronimo/Common.  We probably need to convert the TranQL exception to a
Geronimo exception (e.g. DeploymentException) before throwing it, since we can't put the TranQL
exception in Geronimo/Common.



> Deployer unaware of org.tranql.ql.QueryException
> ------------------------------------------------
>
>          Key: GERONIMO-581
>          URL: http://issues.apache.org/jira/browse/GERONIMO-581
>      Project: Apache Geronimo
>         Type: Bug
>   Components: deployment, OpenEJB
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder

>
> When an EJB deployment throws a TranQL QueryException, the deployer just gets a big stack
trace for a ClassNotFoundException, concealing the actual exception.  We usually put exceptions
of this nature in Geronimo/Common.  It looks like in this case we wrap the TranQL exception
in a Geronimo DeploymentException before throwing it, but the Geronimo exception uses the
TranQL exception as a chained exception (enough to cause the CNFE) and does not itself contain
the error message.  So the DeploymentException should have no chained exception, and should
itself contain the error message.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message