[JSecurity-Developer] Re: HasPermission default target and actions

[jhaile (s. by Nabble.com) <li...@na...>]

Hmmm - but #2 is what I do everywhere.  If the Permission class assumes that a name/target will always be specified, why not just leave the default target as "*"?  We could make actions optional though if we want to allow a 1-arg constructor.

Alternatively we could drop the use of the Permission JDK class entirely and create a JSecurity permission class.  I wonder what issues that would cause in the adoption of JSecurity.  On the one hand, I think users wouldn't care.  On the other hand, it might make it easier to migrate from an existing JAAS implementation.
--
Sent from the Developer forum at Nabble.com:
http://www.nabble.com/HasPermission-default-target-and-actions-t826978c13668.html#a2150592