Robin Helgelin wrote:
On 8/18/07, Mark Helmstetter <[EMAIL PROTECTED]> wrote:
Do you have any examples of how to implement the login form/page? I'd
certainly much prefer to implement this as a Tapestry page rather than
other approaches that use JSP. How will login errors be reported on the
login page?
There is a small example application available here:
http://www.localhost.nu/svn/public/tapestry5-acegi-example/
Currently I'm using the acegi.failure.url application option to give
information that the login didn't work out. If you have other idea,
just shoot them over here :)
Thanks Robin, I just found the example app, and I've got it working
now. I think that is really all that is needed for the login failure case.
There's still a lot that's going on here that I don't quite understand,
but most of that is due to my lack of understanding of how all of the T5
IoC magic works. I'd really prefer to have a bit more control over how
the Acegi classes are configured, and to do so using a more
"traditional" Spring-based approach. I managed to do this for the
injection of the UserDetailsService by omitting the binder.bind() call
in the AppModule. I was unable to do this with the
daoAuthenticationProvider, resulting in the error "Service id
'daoAuthenticationProvider' has already been defined.". It looks like
I'd need to modify the SecurityModule to do this.
Overall though, I'm really happy with it, and thanks to you and Ivan for
your contribution.
Mark
