Hi, I'm new on the list, sorry if my question has already been asked. I didn't find the right answer on google.
Is it possible tu use wicket without Page serialization ? If no, why ? Technically, is it possible to imagine a SimpleHttpSessionPageStore that don't serialize objects and keep them as they are in session, like it's done in others frameworks ? I know, the main reason is to save Session memory by writing pages versions on disk... ok. But... I'm working on an app that consist of few pages, not versioned (no need of the back button support), because I need to keep page state through navigation, I keep pages references created, avoiding creation of a new page instance when back on a visited page.. I don't need to write anything on disk, the session space is enough. This way, i wanted to share a data object instance between pages (as class member), for modification. But due to the Page Serialization the object identity is broken. My unique data object instance turn into several instances (As much as pages that references it i guess ...) I know that I can get arround this by putting directly my object in session.. But, my question is, why to force serialization when we don't need it ? Regards, Yves-Marie PS : sorry for my english. Thanks!
