ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <>
Subject RE: Serializable Location?
Date Mon, 15 Jul 2002 16:43:25 GMT
FYI, JDK 1.4 made Throwable serializable, and added exception nesting (see
'cause'), so distributed exception passing is *so much more convenient* with
1.4. Traditionally, before that, people wrote their own base exception that
serialized the stack straces as a string, thus one had to trap normal
exception so they could be nested in that serializable user-defined
exception (we did here before 1.4. Now we use 1.4 ;-). --DD

-----Original Message-----
From: Stephane Bailliez [] 
Sent: Monday, July 15, 2002 7:52 AM
To: Ant Developers List
Subject: RE: Serializable Location?

> -----Original Message-----
> From: Jonas Göransson []

> In my case it's only the convenience to be able to pass the 
> BuildExceptions through to the client without having to
> convert it into some serializable format. But the BuildException 
> serialization will fail if the Throwable which might have
> caused the exception isn't serializable so I would still have 
> to perform a check in order to be safe.

Yes and most of the time you will miss the important information (ie the
nested exception if any and the stacktrace of the buildexception).

FYI I just committed Location that implements Serializable (cvs head)

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message