Hi Shailesh, Answers inline:
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Shailesh Mangal Sent: Thursday, July 03, 2008 9:15 AM To: [email protected] Subject: [flexcoders] LCDS Performance (hibernate cascade) We are using LCDS 2.5.1 and have a bit of a strange need. Here is a simplistic Object model. Object A ------- Object B Collection [One-TO-Many] Object B collection can be really huge and the relation between A and B is not need on the client but is needed on server so that we can take advantage of hibernate cascade for bulk operations. Here are my queries: 1. Is there any way that I can ask LCDS to ignore Object B collection completely e.g. some configuration in meta of data-management-config.xml In LC DS 2.6, you can either set load-on-demand="true" or page-size on the association tags (one-to-many in this case). With either of these attributes set, DMS will not touch that collection when the parent object is returned. The client gets back an empty collection which is fetched on-demand. With page-size set, only the requested page is fetched. On the server side, if you set paged-collection="true" on the association tag, a new assembler method called getPagedCollectionProperty is called to fetch the collection one page at a time so this approach supports very large association properties. 2. We are thinking of writing a AOP interceptor where we will manually nullify Object B collection whenever assembler get involked. While this option doesnt sound very clean, is it even feasible? It will surely add more complexity in code. If your client never needs the collection, this would be possible. If it does need the collection you'd have to define two destinations one with and one without. 3. Should this be a Managed relation or Hierarchical in data-management-config.xml? Managed associations will be required to use the LC DS 2.6 paging features. BTW, a stable LC DS 2.6 release candidate is available now from the prelease site (which requires you to be on the beta list)... the official release is coming "real soon now". Contact me off list if you need early access to that release. Jeff
<<inline: ~WRD000.jpg>>
<<inline: image001.jpg>>
<<inline: image002.jpg>>
