-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bill,
Bill Barker wrote: > Suggestions on how to improve the Authenticators that ship with TC are > always welcome on [EMAIL PROTECTED] But help on > rolling-your-own-Authenticator > will likely get you pointed back to this list :). The original question was something like "why does the code for the authenticator check for a principal twice?", which seems like a valid question. Apparently, AuthenticatorBase checks for a Principal and, finding none, calls the subclass's method. The subclass's method again checks for a Principal. I see that as good protection against unexpected changes from the superclass (i.e. in case it /does not/ check for a Principal), but the OP wants to know why. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHTum+9CaO5/Lv0PARAsOzAJ9F+/NhayvX12hqfqBwYwURpDxeRACguG3z dZYpY4onr+pW7NBtxMfZa78= =OLLx -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
