geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gianny DAMOUR (JIRA)" <>
Subject [jira] Closed: (GERONIMO-581) Deployer unaware of org.tranql.ql.QueryException
Date Sat, 12 Mar 2005 07:02:52 GMT
     [ ]
Gianny DAMOUR closed GERONIMO-581:

     Resolution: Fixed
    Fix Version: 1.0-M4

TranQL error messages are extracted and used to build a DeploymentException which is then

For instance, this is what is currently displayed on the deployer side when a TranQL exception
is raised:

Caused by: org.apache.geronimo.common.DeploymentException: A stack-trace has bee
n provided on the server-side.
        EJB [Entity logical name=[BasicCmpBean]; physical name=[BasicCmpBean]]
        Finder [Finder method=[findByLastName]; EJB-QL=[
                SELECT OBJECT(a) FROM BasicCmpean AS a WHERE a.lastName = ?1
        Parser, lexer or Tree-walker exception
        No entity having the physical name BasicCmpean

> Deployer unaware of org.tranql.ql.QueryException
> ------------------------------------------------
>          Key: GERONIMO-581
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: deployment, OpenEJB
>     Versions: 1.0-M3
>     Reporter: Aaron Mulder
>     Assignee: Gianny DAMOUR
>      Fix For: 1.0-M4

> 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:
If you want more information on JIRA, or have a bug to report see:

View raw message