Hi,
>Unfortunately, the <exception-type> does not catch return code. I I didn't say it does ;) I was just offering an alternative, and it looks like you'd already taken advantage of it, so that's a good thing. >web applications. I really don't look forward to managing a long list >of <error-page> for each error code in 40+ web.xml files. Higher maintenance is always nearly a cost associated with higher modularity. One might also have N build files, N war files, etc for N modules. >I wonder if I can use a filter to catch the setting of a status code > >200 and does a page forward there .... You could, and then you can use whatever rules (regex, etc.) to decide on the error page. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
