Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Although Exceptions (or any Throwables actually) can be serialized acceptably, they can not yet be deserialized (immediate problem is with "cause" propery, there is "getCause" but no "setCause"; that's "initCause").
Hmmh. Ok, so I got "initCause" added as a setter. But now the problem is "message" – there is no "setMessage" (exceptions are no beans all right). So I will need to find a constructor... tricky.
There is another Jira entry for adding ability to auto-detect constructors, but that wouldn't help here since it'll need annotation support.
But for now a simple heuristic just might work: most exception classes do have single-string-arg constructor for passing in message. So let's assume that for now...