I have discovered an optimized (very little code) solution to CRUD using S2. My next question has to do with CRUD across a 1:M domain model. I have the Preparable and ModelDriven technique working nicely with the id (PK) being set in the BaseAction class. What I would like to work through next is how to link a parent with children where the children make up an entirely new CRUD.
Ideas? -- Scott [EMAIL PROTECTED]
