what is the lifecycle of this data? when do you no longer need to store it?
if this is runtime data you can create a runtime store for it, even a simple map can do. this map can live in servlet context, spring context, as a field of your wicket application, etc. the user pages can then retrieve this data without actually having to have a hard reference to it. the only trick is knowing when to remove this data from memory. -igor On Sat, Oct 10, 2009 at 8:39 AM, Ceki Gulcu <[email protected]> wrote: > > > Igor Vaynberg wrote: >> >> On Fri, Oct 9, 2009 at 1:41 PM, Ceki Gulcu <[email protected]> wrote: >>> >>> Anyway, my application handles a complex tree-like structure, with >>> almost all of the contents non-serializable and outside my control. I >>> don't think I can use a Loadable Detachable Model, because loading the >>> tree may take several minutes. >> >> you would use an LDM per node - the LDM should load the object >> represented by that node only, not the entire tree. >> >> does that make sense? > > LDM makes sense if you can detach data and then re-attach at a later > time. In my case, I can't re-attach data without potentially paying a > very severe penalty. (There is no datasource which can be queried for > my data, as my data is runtime data. I'd need to re-run tests to > re-acquire, which is pretty much nonsensical.) > >> -igor > > -- > Ceki Gülcü > Logback: The reliable, generic, fast and flexible logging framework for > Java. > http://logback.qos.ch > > --------------------------------------------------------------------- > 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]
