river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Dolan" <christopher.do...@avid.com>
Subject RE: Tricky question - UnmarshalException Serialized Form.
Date Fri, 30 Apr 2010 13:56:12 GMT
I'm intrigued and confused.  Throwable is Serializable so how is it
possible to make a subclass not serializable?

-----Original Message-----
From: Peter Firmstone [mailto:jini@zeus.net.au] 
Sent: Friday, April 30, 2010 2:22 AM
To: river-dev@incubator.apache.org
Subject: Re: Tricky question - UnmarshalException Serialized Form.

Thanks Gregg,

I'm thinking about making all the new Exception classes non serializable

to eliminate any codebase downloads for older jini version clients, 
thanks for the soln.

That way only RemoteExceptions need be Serialized.



Gregg Wonderly wrote:
> Peter Firmstone wrote:
>> No mate, that sounds cool, it would be nice to send stack traces 
>> remotely with nested exceptions too if possible anyone got any 
>> experiences or suggestions?
> ex.printStackTrace( new PrintWriter( new StringWriter() ) );
> This works for me where I have does this to make sure that I don't 
> have to worry about SQLExceptions and the like not being serializable.
> Gregg Wonderly

View raw message