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

Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/08/11 16:31:54 UTC

[jira] Closed: (GERONIMO-874) Deployer should not throw exceptions that cannot be deserialized

     [ http://issues.apache.org/jira/browse/GERONIMO-874?page=all ]
     
Aaron Mulder closed GERONIMO-874:
---------------------------------

    Resolution: Duplicate
     Assign To: Aaron Mulder

> Deployer should not throw exceptions that cannot be deserialized
> ----------------------------------------------------------------
>
>          Key: GERONIMO-874
>          URL: http://issues.apache.org/jira/browse/GERONIMO-874
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M4
>     Reporter: Jeremy Boynes
>     Assignee: Aaron Mulder

>
> When invoked remotely (e.g. over JMX) the deployer should not throw exceptions that cannot be deserialized, for example a DeploymentException with a nested Exception whose class is not available to the client. An example of this just reported on the user list occurs when a QueryException is raised by TranQL.
> One solution may be to log the exception on the server and just throw a DeploymentException with the message and no inner cause.

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