The first thing I'd do is turn up logging to 11 on s2, xwork, tiles, and ognl.
Not sure why the exception page would be hit w/ *no* exception but I could imagine that there could be an exception after the page/response has been written to... Is the 'right' page rendered *completely*? Dave stanlick wrote: > When I dig deeper into this, I see the problem is with a oops.jsp I have > configured in my struts.xml as > <global-results> > <result name="exceptionLogger" > type="dispatcher">/oops.jsp</result> > </global-results> > Now here is the strange part -- my request for homePage.action is working > fine and there are no errors! I can remove all references to this oop.jsp > yet the following messages continues to dump to stdout. > "The Struts dispatcher cannot be found. This is usually caused by using > Struts tags without the associated filter..." > If I remove the HTML inside oops.jsp everything works fine! What is > interacting with oops.jsp even when there are no exceptions? > -- > View this message in context: > http://www.nabble.com/The-Struts-dispatcher-cannot-be-found-tp20118536p20138049.html > Sent from the Struts - User mailing list archive at Nabble.com. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
