On Fri, 25 Jul 2003, Bailey, Shane C. wrote:
> Date: Fri, 25 Jul 2003 14:18:54 -0400 > From: "Bailey, Shane C." <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: 'Struts Users Mailing List' <[EMAIL PROTECTED]> > Subject: RE: How does Tiles effect filters and URL mapping? > > > Thanks for your help Craig. I am close to solving my problem but after > trying to use a simple example (a "regular" action, then mapping.findForward > to a tile with no redirect attribute specified so I assume redirect is false > by default) to test my filter / request and a strange thing is happening... > > Even with the simple action test I either Struts or JRun4 is acting in an > unexpected way. In my Action the value for request.getClass().getName() is > "org.securityfilter.filter.SecurityRequestWrapper" and in the JSP (tile) > page that is forwarded with the RequestDispatcher.forward the value of <%= > request.getClass().getName() %> is "jrun.servlet.ForwardRequest". > > I am guessing it is a JRun4 specific reason (and not Struts) why the same > request object isn't available in the JSP as is in the prior Action. Your > thoughts? > In order to implement the semantics of RequestDispatcher, it is generally required to wrap the original request object. But that should make no difference to your application, because the same attributes, parameters, and request property values are still visible through the wrapper. Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
