ahh I guess that is a proxy class that by itself is not serializeable but we
need to handle those i guess specially .
will check it out
johan
On 2/15/07, ChuckDeal <[EMAIL PROTECTED]> wrote:
I suppose it is worth noting that upon Eelco's suggestion, I now have the
following lines in my Application.init()
//Objects.setObjectStreamFactory(new WicketObjectStreamFactory()); //
custom
serialization
Objects.setObjectStreamFactory(null); // jdk
serialization
When I got the exception, I was using the custom serialization, when I
swtiched to JDK serialization, I did not get the exception. I suppose you
might have expected that (?), but I'm just confirming it.
BTW, wicket serialization is still the default (Eelco had thought that JDK
was the default as of revision 507700)
Chuck
--
View this message in context:
http://www.nabble.com/custom-serialization-problem-tf3229766.html#a8985626
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
