On Jul 24, 2008, at 22:32 , Jeremy Thomerson wrote:
There are other, just as simple options. A couple of examples below.
Really, you're not being "forced" to do this by Wicket. If you want
to hold
*anything*, in *any* framework, in the HTTP session, it should be
...
I'm only disagreeing on the part about it being Wicket forcing you
to do it.
Guys, but I'm ___not___ talking of the session :-) I'm not putting
those things in the session. The problem is with __pages__ that get
serialized, I think because they get into the session for the
versioning. So it's Wicket doing that, right?
--
Fabrizio Giudici, Ph.D. - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog
[EMAIL PROTECTED] - mobile: +39 348.150.6941
