Thanks Igor, I get the clear picture now, I'll make a workaround from your advice. I currently have problems with reference object that came from other libs that is not Serializable.
Best Regards, On Jan 23, 2008 2:01 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > anything that a page keeps reference to, directly or indirectly, needs > to be serializable. for objects that are not serializable you should > do what loadabledetachablemodel does: keep an object as a transient > variable and have a way to look it up if its null. ive built a lot of > stuff with wicket and this hasnt been a problem yet. sometimes i had > to wrap or subclass objects that came from other libs because the devs > didnt bother to make those objects serializable - not everyone thinks > about this stuff - but other then that nothing major. -- It's not going to be like this forever Blog: http://joshuajava.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
