I've been doing some refactoring with my ApplicationResources.properties and
every once in a while I get a page that shows a JspException when I've
mistyped a property name or whatever. Is there anyway of catching the
JspException at this compilcation point and displaying a different message
(or none at all)?

Theoretically, this should never happen once we deploy, but if someone mucks
with an image path or something is missing, I'd rather the client deal with
a missing image rather than see the JspException trace.

Thanks.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to