* Igor Vaynberg:
> this is not a requiremenet of wicket per se but that of the servlet
> containers. anything you keep in http session must be serializable. since
> wicket keeps most of its entities in session they must be serializable.
I understand this for a session because it can be made persistent
across restarts, but what about Application's metadata:
Application.setMetaData(MetaDataKey key, java.io.Serializable object)
Why do we need Serializable here?
BTW I use Application.setMetaData() to pass Spring beans to the
Page. Are MetaData suitable for that kind of purpose?
And about the Wicket-Spring extension, is there a documentation
available?
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
-------------------------------------------------------------------------
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
