From: "David Johnson" <[EMAIL PROTECTED]> > I <<really>> want to use a tiles def here somehow or my > **only** page that is all hardcoded will be error.jsp. > thoughts?
What is the root cause of the error 500? Take the <error-page> out and look at the stack trace. Ignoring any ServletExceptions, what's the _real_ problem here? Configure THAT exception in struts-config.xml with an <exception> tag, and you will be able to use a tiles definition. Then create a simple html or jsp page that fits with your site design, put a generic error message on it, and use that for the location of your error code 500 in web.xml. IMO, you should never get as far as an error code 500 during normal operations. You know what kind of exceptions your code can throw, deal with those in struts-config.xml. It's the unchecked exceptions that are going to make it all the way out to the container, and the web.xml config is a last ditch effort to make sure the user does not see a stack trace. -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
