Robin Helgelin wrote:
I’m thinking about it. The problem is that Acegi is a lot of small pieces which can be used for building required functionality and we need something more-or-less solid and configurable (module). One of the options is to provide several module configurations, one configuration for each case (CAS-based authentication, DAO-based authentication) and make the application to load the proper module configuration (do not specify it name in the Tapestry-Module-Classes manifest entry).The bad thing about tapestry-acegi is that it is not very flexible, though. Recently I was trying to apply tapestry-acegi for CAS authentication (http://www.ja-sig.org/products/cas/) and found that I had to rewrite almost every line of its module class, which unfortunately indicates that tapestry-acegi is not very reusable. On the other hand, tapestry-acegi does have an added value above the core Acegi (for example, worker that allows applying the @Secured to the methods/pages), so I can't just throw it away and write my own module file — that's not enough, I need these helper classes.You did a good job with the first code, so I'm happy to accept further changes to make it more flexible :)
-- WBR, Ivan S. Dubrov
signature.asc
Description: OpenPGP digital signature
