Phil Kulak wrote:
I've had bad experiences with Acegi. The complexity it adds to a
project is rediculous and it's difficult (if not impossible) to use a
class heirarchy for your users domain instead of the classic "roles"
model. Essentially, it forces the relational model into your
application which I don't care for at all. Just my 2 cents.
I didn't look very carefull into it, it just looked like a nice
collection of tools from the outside.
I once thought of an ACL system that uses heirachial roles for their
principals, i.e. the user is the lowest leaf, tied together with in
different "groups". Looking from the acegi default SQL schema it looks
quite ineffective and cumbersome to me ...
Can you give me some example what you mean to handle it without a
relational model ?
regards,
Michael
--
Michael Glauche, Dipl. Inform. Connection GmbH
[EMAIL PROTECTED] http://www.connection-net.de/
pgp key: http://www.connection-net.de/~mglauche/mglauche.asc
Reclaim Your Inbox!
http://www.mozilla.org/products/thunderbird/
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
