that is something wrong in your code
Or maybe a bug in wicket somewhere but more people should see that then
Application object should never be serialized. At what point do you have to
serialize it?
I think you hold on to it somewhere in your code.
johan
On 12/7/06, ChuckDeal <[EMAIL PROTECTED]> wrote:
in 1.3, should Application implement Serializable?
I am in the process of switching to the 1.3-incubating-SNAPSHOT builds and
I
needed to implement Serializable on my APplication object. I checked the
Wiki (Migrating from 1.2 to 1.3) and this wasn't mentioned.
Is this required for 1.3 or have I got something wrong with my code?
Everything was peachy with the latest 1.2-SNAPSHOT.
Chuck
--
View this message in context:
http://www.nabble.com/Application-must-implement-Serializable--tf2771344.html#a7730054
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
[email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
