[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: hasClassInitializer and exception
From: |
Mark Wielaard |
Subject: |
RE: hasClassInitializer and exception |
Date: |
Fri, 22 Jul 2005 12:10:01 +0200 |
Hi,
On Fri, 2005-07-22 at 08:28 +0200, Jeroen Frijters wrote:
> > The question is whether or not we are throwing the right exception at
> > the right place. I haven't looked closely at the code yet
> >
> > Can someone come up with a nice (or probably contrived) testcase for
> > this?
>
> See attached. Sun throws a NoClassDefFoundError on serialization and the
> expected exception (i.e. either the Error or
> ExceptionInInitializerError) on deserialization. Both exceptions are
> throws from ObjectStreamClass.getSerialVersionUID().
Thanks. I turned this into some mauve tests. See
gnu/testlet/java/io/Serializable/BreakMe. It seems we already have the
correct behavior since all these tests PASS. Or I implemented the tests
wrong of course. Please check.
Cheers,
Mark
signature.asc
Description: This is a digitally signed message part