It depends on your needs. The tapestry5-acegi or tapestry-spring-security (http://www.localhost.nu/java/tapestry-spring-security/index.html) are probably easier to drop in. The Spring-configured route might be better if your application includes other servlets or filters.
Either way you will be able to get access to things like the AuthenticationManager if you need to from your page classes. With an older T4 app, I used Spring / Hibernate / Acegi with Acegi configured via Spring. I also rolled a few components: Authorize and AclAuthorize. With the T5 apps I now do, I use a slightly modified tapestry5-acegi although I still use Spring for DAO's and some services. Parts of my old Authorize component are now included in the tapestry5-acegi IfRole component. Actually, I think tapestry5-acegi and its successor would benefit from being split in two: one piece for the annotations, components and supporting pieces that are specific to Tapestry, and the second piece to allow for a choice of configuration via Spring, or configuration via tapestry-ioc. Whichever way you choose, it's better than re-inventing the wheel and rolling your own security. Jonathan > -----Original Message----- > From: wesley [mailto:[EMAIL PROTECTED] > Sent: Friday, October 03, 2008 10:59 > To: users@tapestry.apache.org > Subject: spring T5 integration on acegi security considerations > > > hi all, > > i've been implementing a project by using T5 mostly as front end, spring > framework for back(eg Dao and db operations). after few search on it > regarding the acegi implementation, i'm a little bit confused as whether > or > not to implement this security framework on T5 or spring. any > recommendations or advise on this topic? should i just apply this security > layer on T5 alone? or Spring 2 for securing the backend or both?? > > please advise, thanks > > wesley > -- > View this message in context: http://n2.nabble.com/spring-T5-integration- > on-acegi-security-considerations-tp1142158p1142158.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
