[
https://issues.apache.org/jira/browse/OPENEJB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau resolved OPENEJB-334.
----------------------------------------
Resolution: Fixed
Fix Version/s: 3.0
no more relevant
> Server side exception classes are exposed to EJB clients
> --------------------------------------------------------
>
> Key: OPENEJB-334
> URL: https://issues.apache.org/jira/browse/OPENEJB-334
> Project: OpenEJB
> Issue Type: Improvement
> Affects Versions: 1.1, 2.0, 2.2
> Reporter: Dain Sundstrom
> Fix For: 3.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
