Component-based Scalable Logical Architecture: Difference between revisions

Content deleted Content added
Line 35:
Allows objects to maintain collections of "broken rule" objects. Broken rules will exist for an object until it is in a valid state, meaning it is ready to be persisted to the database. ''BrokenRule'' objects are usually associated with validation logic such as ensuring that no alphabetic characters are entered into a phone number field. For example, if an ''Account'' object has a ''PhoneNumber'' property, and that property is assigned a phone number with alphabetic characters, the ''Account'' object's ''IsValid'' property will become false (making it impossible to save to the database) and then a new ''BrokenRule'' object will be created and assigned to the Account's ''Broken Rules'' collection. The rule will disappear when the invalid phone number is corrected making the Account object capable of saving itself to the database.
 
==[[''Extended features of CSLA.NET''''Italic]] text''==
===Simple UI creation===
Using [[Windows Forms]] or [[Web Forms]], data-bound controls like DataGrids and ListBoxes can be bound to business objects instead of more generalized database objects like [[ADO.NET]] DataSets and DataTables.