Validating Exactly One Composed Detail of a Given Type
By Steve Muench on Nov 04, 2009
I've added example# 153 that illustrates how to validate that there exists exactly one composed detail row of a given type, along with a number of other interesting smaller features like:
- Using a rowset aggregation function in groovy to conditionally assign the default value of the detail based on whether there already exists a row of "Primary" type or not.
- Using a custom framework extension class for ViewObjects that any view object can use to declaratively cause any new row to be added at the end of the default rowset
- Using a ClobDomain and custom EmailAddress domain and the genericConverter in JSF to allow successful data entry for these domain types.
- Initializing a bounded taskflow by declaratively invoking a custom application module method exposed on its client interface
- And more...