No reason in particular other than to minimize the number of public extension points. The more of them there are, the more maintenance is required for the dev team for backwards compatibility.
If you feel this should be enabled, please feel free to open a Jira issue. Cheers, Les On Mon, Feb 27, 2012 at 9:26 PM, ted <[email protected]> wrote: > Hey guys, > > What was the motivation behind the decision of making the following method > private? > AuthorizingRealm, line 465: > private boolean isPermitted(Permission permission, AuthorizationInfo info) > > As for me, it's a pretty convenient extension point, since all the other > isPermitted* and isPermittedAll* methods are using this method, so maybe it > would be better to make it protected instead of private? > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/private-boolean-isPermitted-Permission-permission-AuthorizationInfo-info-as-public-tp7324533p7324533.html > Sent from the Shiro User mailing list archive at Nabble.com.
