Thanks Jan,
> If you think about it, this makes sense: While error pages
> declared via <error-page> receive the request via
> RequestDispatcher.forward() (meaning any error-related
> request attributes added to the request prior to the dispatch
> will be visible to them), the same does not necessarily hold
> true for error pages declared via <form-error-page>, which
> should receive the request via an HTTP redirect, meaning any
> error attributes stored on the request prior to the redirect
> will be lost.
This makes sense.
> for why a <form-login-page> resource (and also
> <form-error-page>, since the same resource may be used for
> both purposes) should receive the request via an HTTP
> redirect as opposed to a
> RequestDispatcher.forward() operation. We fixed the above
> issue only very recently in GlassFish v2 (as of build 57).
(Although here I'm not so sure why using HTTP redirect instead of
dispatcher.forward(...) fixes the problem, I would've thought the
opposite way around, but no matter).
> I know this is subtle, but I hope it still makes sense to you.
>
> Let me know if you have any questions.
>
>
> Jan
Thanks again, I'll checkout one of the latest builds,
Cheers
Joe
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.