On 5/29/07, Jan Kriesten <[EMAIL PROTECTED]> wrote: > what i was thinking about was - instead of using acegi as a filter and use it > on > urls - integrate it in the wicket-app and act on top of the components. this > sounds like the wasp/swarm-concepts, only that acegi is the base. > > what i really dislike about acegi is the spring/xml-stuff. but that's another > story... ;-)
If you take the spring/xml and the URL based authorization out of Acegi, what is left? Not a stab at Acegi, just asking. Martijn -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
