Le dimanche 2007 décembre 30, Peter Ledbrook a écrit :
> To all JSecurity plugin users,
>
> I have made an intermediate release of the plugin available that uses
> a filter rather than an abstract base controller. In other words, your
> controllers will no longer have to extend JsecAuthBase. To install it,
> simply run this command:
>
> grails install-plugin jsecurity 0.2-SNAPSHOT
>
> I have only briefly tested it with Grails HEAD, so I don't know how it
> behaves with the release candidates. This is definitely "use at your
> own risk" :) However, you should be start using it with a minimum of
> fuss: once installed, you only have to recreate the DB realm (if
> you're using it).
It's nice to see the new JSecurity library is now included in your plugin.
I upgraded to the 0.2-SNAPSHOT release and it works perfectly on my RC3 app.
And now the charsetName bug (Jira GRAILSPLUGINS-171) seems to be solved
forevermore!
Big up to Peter and Lez!
> Please try it out and raise any issues in the plugin JIRA:
>
>
http://jira.codehaus.org/browse/GRAILSPLUGINSNot really an issue but I think a redirect to the root url should be still
present at the end of the signOut method of AuthController (avoiding the user
to create his own signOut view).
And it's really cool to use filter instead of the "old" JsecAuthBase
controller.
But have someone a tip for using the flash object from a filter (which seems
to available for controllers and taglib only)?
Thanks, Vincent.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
