I'm having trouble understanding the 4.x editable child list.
The Using CSLA 4.x objects ebook lumps together Editable Root and Child lists (in the title of the section on page 58) but in that section goes on to completely ignore editable child lists and provides no further info about the practical matter of coding them, instead it discusses in fairly good detail how to code an editable root collection that is directly persisted.
I'll appreciate that later when I get to my editable root collections but for now I'm in limbo.
I have a number of editable Root objects that contain a collection of child objects that I need to port over from csla 1.x and so far I'm stumped as to best practices for this.
Are there any examples of how to do this?
The Using CSLA 4: Data Access ebook has a section in Chapter 5 titled "Editable Object Graph Persistence". This is a walkthrough of a parent-childlist-child-grandchildlist-grandchild object graph.
That provides pretty detailed coverage of the editable child list stereotype.
Outside of persistence, there's no difference between a root or child editable list, and so the Using CSLA 4: Creating Business Objects ebook doesn't spend much time trying to differentiate. I left that to the Data Access ebook, where the differences are very real.
Ok, thanks, I'll look at that again. I guess I'm too literal, I think to myself there are these stereotypes and I look for a section on them and then expect an example of how to use each one.
Cheers and thanks again.
I tried to cover each stereotype.
But there's literally no difference between an editable root list and an editable child list outside the persistence code. I must confess that I thought about copy-pasting some of the content, but that really seemed inappropriate somehow :)
Copyright (c) Marimer LLC