Just to let you know the <dispatcher>FORWARD</dispatcher> was all I needed. I can't actually find any documentation on a <dispatcher>ERROR</dispatcher> mapping
On Wed, Jul 1, 2009 at 1:43 PM, Ben Gunter<[email protected]> wrote: > Do you have StripesFilter executing on error, something like this? > > <filter-mapping> > <filter-name>StripesFilter<filter-name> > <url-pattern>*.jsp</url-pattern> > <dispatcher>REQUEST</dispatcher> > <dispatcher>FORWARD</dispatcher> > <dispatcher>ERROR</dispatcher> > </filter-mapping> > > -Ben > > On Wed, Jul 1, 2009 at 7:09 AM, phil darley <[email protected]> > wrote: >> >> Hi Stripes folk, >> >> I'm getting a 500 internal server error (ironically) when attempting >> to customise my error pages - specifically the 404 page. >> >> My error pages use the default template layout-definition for my web >> app, if I request my 404 jsp directly it works fine but when the >> servlet container forwards a bad request (a request for a non-existant >> resource) to my 404 page a StripesJspException is thrown because the >> LayoutContext contains an empty Map of parameters for the layout >> componets. >> >> When does the Parameter Map get set on the LayoutContext? I can only >> assume it has something to do with the way the servlet container >> (weblogic 81) is forwarding on the request. >> >> Cheers, >> Phil > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Stripes-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/stripes-users > > ------------------------------------------------------------------------------ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
