the models have to be serializable, not the model objects they point to. for example if you are accessing a hibernate entity then the model that accesses it has to be serializable, not the entity itself. this is why we have LoadableDetachableModels.
-igor On Fri, Nov 12, 2010 at 8:18 AM, Brown, Berlin [GCG-PFS] <[email protected]> wrote: > I haven't entirely researched this. But I know wicket recommends > declaring your model objects as serializable so that if the page > serializes than so do the objects. > > With this approach, I tend to define all or most of my beans and service > objects as serializable. Do you have to define an object serializable > if it is accessed from Wicket (say on an event method)? > > Also, aren't there issues with declaring objects as serializable? Is it > insecure to put data in a serializable object? Where by the security > mechanisms for that object can be bypassed? > > For example. > > Some Panel.java: > > final Serializable x = new Serializable() {} > > final Component z = new Link() { > onClick { > x??? <--- does X have to be serializable in this case? > } > } > > Berlin Brown (POL) > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
