Just out of curiosity, I was wondering if anyone could let me know the reason why there is no formal CSLA way to enforce authorization rules when adding, replacing or removing items from a collection.
I really wish the CSLA had a built in way (well know way) to be able to enforce such actions. Note that I am not just taking about simple "is in role" authorization rules but more sophisticated rules that includes authorization based on a value on a parent object for example or some other criteria.
In essence, I wish we could attach a rule to an add, replace, remove collection action (just like we do for properties) and have the CSLA take it from there. As of now, I only know of workarounds that requires us to manually enforce such rules on our business objects.
This is a good idea. I will add it to the wish list.
Copyright (c) Marimer LLC