I already closed that as won't fix that is how serialization works.. A class that can be serialized that extends something cant be serialized then the super class is not suddenly serialized, thats not how it works For that class the default constructor is called which is responsible for its own class and if the default constructor doesnt do that then the serializable sub is responsible for that
johan On Wed, Apr 2, 2008 at 6:24 PM, Antoine Angenieux <[EMAIL PROTECTED]> wrote: > Okay guys, i finally figured it out, and i've setup a quickstart that i've > attached to the jira issue > http://issues.apache.org/jira/browse/WICKET-1474. > > I won't go into deeper explanations in this mail as i guess the jira is a > more suitable place ;) > > Cheers, > > Antoine. > > > Antoine Angenieux wrote: > > > Yep, i'll do that this WE, create a jira issue and attach a quickstart > > ;) > > > > James Carman wrote: > > > > > On Wed, Apr 2, 2008 at 8:52 AM, Antoine Angenieux > > > <[EMAIL PROTECTED]> wrote: > > > > > > > I've checked all the logs many times, and i just went through a few > > > > of them > > > > a few minutes ago... checking all errors logged, and no trace of > > > > serialization issues... > > > > > > > > > > > Can you put together a Quickstart which exhibits this behavior? > > > > > > > > > -- > Antoine Angénieux > Associé > > Clinigrid > 5, avenue Mozart > 75016 Paris, France > +336 60 21 09 18 > [EMAIL PROTECTED] > > >
