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.
-igor On Jan 22, 2008 10:56 PM, Joshua Jackson <[EMAIL PROTECTED]> wrote: > Looks like that this problem is viral. How do I work with objects that > is not Serializable while on the other hand wicket want it to be > Serializable? > > On Jan 23, 2008 11:31 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > see SpringWebApplcation, it has methods to create same proxies @SpringBean > > does. > > > > -igor > > > > > -- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
