I just attached a new patch to the same issue in JIRA.
The advantage of this patch is that, if we get an
InvocationTargetException when unmarshalling an object, the causal
exception (thrown by the constructor of the class being instantiated) is
kept in the stack trace instead of being lost. This makes debugging much
easier.
There are probably other places where a similar change should be made;
my patch just solves what I came upon when debugging our application.
Note that this makes Castor depend on Java 1.4 (although this has been
announced previously for other changes anyway).
Benoit
Werner Guttmann wrote:
Yes, very much indeed .. ;-). Either re-open 824 and attach a new patch,
or create a new issue. Whatever your preference is ....
Werner
Benoit Maisonny wrote:
Hi,
Back a long time ago, I submitted a patch to support causal exception in
a SAXException in Unmarshaller:
http://jira.codehaus.org/browse/CASTOR-824
Now that Castor depends on Java 1.4, there's no reason not to loose
causal exceptions anymore.
Would you be intersted in a new patch?
Cheers,
Benoit
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
--
Benoit Maisonny [EMAIL PROTECTED]
Director & Consultant http://synclude.com
Synclude
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
