yeah, Dave, will do.
-Original Message-
From: david.melia [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 10, 2008 3:59 AM
To: users@tomcat.apache.org
Subject: RE: JNDIRealm - how to display login exceptions/error msg
within form-error-page when using Form based authentication?
Hi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
david.melia wrote:
| Also, i have checked out the JNDIRealm source code and it only seems
to log
| any exception but not throw it back (seems to pass a null Principal
back to
| the calling code to signify you could not log on). If this is the
EMAIL PROTECTED]
> Sent: Wednesday, April 09, 2008 11:17 AM
> To: Tomcat Users List
> Subject: RE: JNDIRealm - how to display login exceptions/error msg
> within form-error-page when using Form based authentication?
>
>
>> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
>
ok, thanks.
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 11:47 AM
To: Tomcat Users List
Subject: RE: JNDIRealm - how to display login exceptions/error msg
within form-error-page when using Form based authentication?
> F
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDIRealm - how to display login
> exceptions/error msg within form-error-page when using Form
> based authentication?
>
> even for my antiquated version, Chuck? 4.1.36?
It's been in the servlet spec si
based authentication?
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDIRealm - how to display login
> exceptions/error msg within form-error-page when using Form
> based authentication?
>
> I believe you can only set one standard error page in the XML
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: JNDIRealm - how to display login
> exceptions/error msg within form-error-page when using Form
> based authentication?
>
> I believe you can only set one standard error page in the XML
> file, if I'm
I believe you can only set one standard error page in the XML file, if I'm not
mistaken, at least of the specific web app itself.
But one thing I did was flag for a specific exception to be caught, and if this
matched, ran an out.println series of statements to the browser indicating to
the use
