From: lhazlewood (s. by Nabble.com) <li...@na...> - 2005-12-31 03:40:25
|
I think the Permission class is too widespread and ingrained in the Java security mindset to abandon it. Aside from minor inconveniences, it seems to work well enough. The name itself is very intuitive to new users (i.e. everyone is pretty comfortable with the terms 'user' 'role' and 'permission'), so this is a good thing. I'm good with leaving the name/target attribute as '*'. This to me is certainly better than what we have now, which always forces a two 2-arg-constructor to be used. If the developer doesn't like it, they can manually override the target to be whatever they want. At least this gives them flexibility over how the permission is constructed, unlike the current code. So, I'll go ahead and make the change of the default actions string from "*" to "" and update the permission instantiation logic accordingly. This is good, I've now achieved the warm-n-fuzzy feeling I was looking for ;) -- Sent from the Developer forum at Nabble.com: http://www.nabble.com/HasPermission-default-target-and-actions-t826978c13668.html#a2150970 |