You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Matt Hogstrom (JIRA)" <ji...@apache.org> on 2006/11/17 06:41:37 UTC
[jira] Moved: (OPENEJB-334) Server side exception classes are
exposed to EJB clients
[ http://issues.apache.org/jira/browse/OPENEJB-334?page=all ]
Matt Hogstrom moved GERONIMO-1302 to OPENEJB-334:
-------------------------------------------------
Project: OpenEJB (was: Geronimo)
Key: OPENEJB-334 (was: GERONIMO-1302)
Issue Type: Improvement (was: Bug)
Component/s: (was: OpenEJB)
Fix Version/s: (was: 1.2)
Affects Version/s: 1.1
2.0
2.2
(was: 1.0)
> Server side exception classes are exposed to EJB clients
> --------------------------------------------------------
>
> Key: OPENEJB-334
> URL: http://issues.apache.org/jira/browse/OPENEJB-334
> Project: OpenEJB
> Issue Type: Improvement
> Affects Versions: 1.1, 2.0, 2.2
> Reporter: Dain Sundstrom
>
> Currently we are passing all exceptions from the server directly to clients. We should have a strategy encapsulate "system exceptions" so the client does not require server exception classes on the client.
> I propose we serialize the full exception class, the exception message, and the exception stack trace separately. This will double the size of the exception on the wire, but will allow us to attempt to deserialize the exception and if that fails, create a new replacement exception using the message and stack trace.
--
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