Again, you are the man.
Thanks for the quick responses, Jake | Loading all the roles into GenericPrincipal is just the way that the | existing Realm implementations do it. Nothing stops you from using a | Principal implementation that doesn't contain the roles, and make your | Realm.hasRole() implementation do database lookups for the particular role | in question. Note that your Realm implementation acts as a Factory for | the Principal -- you can override RealmBase.authenticate() to return | whatever kind of Principal you want, as long as you override hasRole() | also. For example, it would be straightforward to create a Realm | implementation that implemented every call to hasRole() as a database | lookup -- although this will be slower than the current approach, it won't | have the memory overhead of storing all the roles (or the computational | overhead of looking all of them up). | | | > Much Appreciated, | > Jake Hookom | > | | Craig | | | -- | To unsubscribe, e-mail: <mailto:tomcat-user- | [EMAIL PROTECTED]> | For additional commands, e-mail: <mailto:tomcat-user- | [EMAIL PROTECTED]> | | --- | Incoming mail is certified Virus Free. | Checked by AVG anti-virus system (http://www.grisoft.com). | Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 | --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.381 / Virus Database: 214 - Release Date: 8/2/2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
