[EMAIL PROTECTED] wrote:
FYI, The serialization problem should be fixed in the Derby 10.1 release which should be out in the next few days hopefully.
Derby exceptions are just an example. I'd like to know who should take care of the issue, the container or a bean provider? Also, I'm wondering whether or not SQLExceptions are of any value at a client side? I would rather suggest using real application exceptions (created by the bean provider) which would only carry information that a given operation could not be executed properly.
What about the property - openejb.includeStackTrace or openejb.sendStackTrace - to not send a stack trace, but only a toString() representation of it. It may be of help in some situations where a bean is not properly developed wrt exception handling. I think people would like a property that would turn them off.
John
Jacek
