Hi,
Chapter 4 "Business Rules" of the E-book on CSLA 4: Creating Business Objects describes (p.83):
"You should use business rules to alter property values in your objects based on any sort of rule, algorithmic process, or calculation. Business rules can do something as simple as upper-casing a string value, or as complex as performing a tax, price, or discount calculation."
For read-only objects only authorization rules are called, but wouldn't it be perfectly valid to apply business rules (not validation rules!) on read-only objects as well, especially when it comes to presentation of data?
The example describes that it could be as simple as uppercasing a string. So as this is presentation only, why not support this in a read-only situation? This would allow changing the presentation without thinking about the data.
Wouldn't it make sense to separate business rules and validation rules?
Any thoughts?
Cheers,
Peter