Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification.
The following page has been changed by NiallPemberton: http://wiki.apache.org/struts/StrutsCatalogLazyList ------------------------------------------------------------------------------ === Still not very satisified === I'm still not happy with the solutions provided (including my own). Many of the above solutions assume you know how deep your items are nested, or that you create nested objects up front that can handle the lazy situation. Where I'm not happy is where you can get back a nested structure of unknown depth. I have a case now where the generated content that can be editable is a questionnaire and each question can end up having sub-questions. Other than using Session scope I'm not sure of the best approach to use. I'm messing around with LazyDynaMaps to see if that might work. Not the ideal solution since I'd prefer to use straight value objects from the midtier, but I'll compromise if need be. + ''[http://www.niallp.pwp.blueyonder.co.uk/lazydynabean.html NestedLazyBean] does n level indexed properties. For straight forward object graphs (e.g. {{{person.address.line1}}}) where you want an "address" !DynaBean automatically created when {{{person.get("address").set("line1", ...)}}} is called then its slightly more problematic, since how do you know when it hits {{{get("address")}}} that it should be a !DynaBean property rather than some other regular kind? Using !BeanUtils's '''Map''' notation (i.e. using {{{person[address][line1]}}}) works from a !LazyDynaMap PoV, but you will need the [http://commons.apache.org/downloads/download_beanutils.cgi BeanUtils 1.8.0-BETA], since nested maps were not supported until that version.'' +
