Perhaps the community can answer that question for you. I use the error-page 500 as a catch all for undefined / unexpected errors. I'm sure there's a way to do it, I just haven't done it before and can't tell you off the top of my head. You can probably point the Error at an action which can point to a tiles definition. I'm just getting started with tiles, so I'm not sure... let me know how it turns out.
My first test would be something like the following: Point the Error to an action which pulls all the parameters out of the request object and see what's there. If nothing is there, you may want to modify your code to catch all exceptions and put the stack trace in the session scope as a bean and pass it that way, parse it in the action your Error 500 page points to. But whether that works or if there is a better was is speculation. Hope this helped, Andrew T On 5/26/05, David Johnson <[EMAIL PROTECTED]> wrote: > Can I point it at a tiles-definition? I have one called "page.error" > > Also, how to I display the details of the error in my error page? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
