Any objections against adding two new methods in the Rhino Security
AuthorisationRepository: RenameUsersGroup and RenameEntitiesGroup
Reason: a consumer of Rhino.Security could already change the name of the
UsersGroup and the EntitiesGroup by directly accessing the Repository<T> of
them but when doing that the business rules are of course not checked, and
you don't get a decent exception when you do something wrong such as giving
two groups the same name.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to