The purpose of the LoadableDetachableModel is to not hold the data itself between requests, just a 'handle' that loads it from 'somewhere' on demand.
If in the constructor of the page you just pull the data and pass it to components, they will hold the reference to it, and everything will be serialized with the page. On Fri, Dec 3, 2010 at 7:51 PM, Don <[email protected]> wrote: > Does it matter as long as I use it only in the c-tor(s)? I could have > something like this: > > Document doc = model.getObject(); > add(new Label("doc_name", doc.getName())); > add(new Label("doc_size", doc.getSize())); > > But I could have also something else, with dropdowns etc. > > --- On Fri, 12/3/10, James Carman <[email protected]> wrote: > >> From: James Carman <[email protected]> >> Subject: Re: Question on LoadableDetachableModel >> To: [email protected] >> Date: Friday, December 3, 2010, 11:43 PM >> What do you do with "docModel" in >> that constructor? >> >> On Fri, Dec 3, 2010 at 4:15 PM, Don <[email protected]> >> wrote: >> > Hi, >> > >> > I would suspect that having a class like below I >> wouldnt really need to use a LoadableDetachableModel model >> because I dont store it in some field of the class (or any >> of the components used by it) so if the page gets stored >> into session, that wouldnt bloat the session. >> > >> > Am I right in my thinking here, please? >> > >> > public class ResultPage extends WebPage { >> > // note no model stored as private fields of >> some type >> > // DocumentModel model; >> > >> > public ResultPage(DocumentModel docModel) { >> > // ... >> > } >> > } >> > >> > Tks >> > >> > >> > >> > >> > > > >
