The main LDM shouldn't get you serialization errors, because you're not serializing the "entity" (just the key perhaps and a proxied reference to your dao/repository).
On Fri, Sep 26, 2008 at 12:11 PM, Neil McT <[EMAIL PROTECTED]> wrote: > > Yeah, I originally had that - a LDM as the main model and the ListView model > based on that. I've also tried a couple of variations of this but I still > get the Serialization errors. I think maybe I'm not following you exactly. > > As far as I can see the ListView needs a collection as a model (the > collection of Contacts) and, no matter how I configure this model, it will > still point to non-serializable objects (either the 'owner' property of the > AbstractPersistentCollection or perhaps the Contacts themselves). So does > the collection itself need to be Loadable / Detachable? > > Thanks. > > > > > jwcarman wrote: >> >> I usually use a LDM for the main object (which has the collection >> property) and have the model for the collection based upon that >> (perhaps a PropertyModel?). >> >> > > -- > View this message in context: > http://www.nabble.com/Loadable-detachable-collections--tp19685949p19691650.html > Sent from the Wicket - User mailing list archive at Nabble.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]
