I've had the pleasure of developing against both plugins. JSecurity
has a nicer model, more granular control of permissions and from what
I understand, it has a somewhat unique ability to integrate
crossplatform applications with a single signon. Its very cliche for
me to say this, but the JSecurity plugin is a "Mac" and acegi seems to
be the PC in this case.
On Fri, May 16, 2008 at 9:35 AM, Jon.S <
bulkmailme@...> wrote:
>
> Hi there,
>
> I just notice your taglib test(AuthorizeTagLibTest) in plugin folder, I
> might play with it some more. Somehow I miss that from your docs...
>
> The only thing remains is to create some manager program where I can specify
> each role permision for each domain fields.
>
> For example:
>
> class DomainFoo{
> String blah;
> }
>
> then you have another domain to store your role
>
> class DomainRolePermission{
> String domainName;
> Role theRole;
> short permisionLevel;
> }
>
> Then I need to write a taglib something similar like this...
> <g:fieldVisibility value="${permisionLevel}"> ...
>
> the permisionLevel could be: read, write, hidden
>
> Then it will render text box if writeable, or hidden input, etc....
>
> I am actually planning to write this because its pretty simple
> actually(maybe). But if you want to include that, it will be superb -- I'll
> owe you a beer for that :)
>
>
> Best Regards,
>
> J
>
> --
> View this message in context:
http://www.nabble.com/jsecurity-VS-acegi-tp17272804p17274871.html> Sent from the grails - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email