what you are describing are services and yes those shouldnt be hold on to in wicket components/models Image is just byte[] so that should be able to serialize
On Thu, Jul 24, 2008 at 10:57 AM, Fabrizio Giudici < [EMAIL PROTECTED]> wrote: > > On Jul 24, 2008, at 10:38 , Johan Compagner wrote: > > >> It is just simple if you want to play safe an nice be sure everything you >> put in the session is serializable >> > > It _isn't_ that simple. If you have to put an Image, or classes made by > third parties, or classes made by me for which ___I don't want___ that > Wicket duplicates an object because the related class has been designed to > guarantee a single instance for each object identity. I have to use > detachable wrappers, which is not the end of the world, but a great > annoyance and a source of code proliferation... > > > -- > 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 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
