Filter being called for Struts' forwarded JSP

Feb 18, 2009 00:48:34

I have a Struts action class like this:

A filter like this:

My struts-config.xml:

My filter declaration in web.xml:

My test.jsp JSP is like this:

When I called the action, I got the following result:

requestUri: /TestAction.do
In TestAction
requestUri: /test.jsp
In test.jsp
After
After

My question is: why is the filter called for the JSP? I thought only request that is coming in directly from the client browser will activate the filter, which in this case should be for /TestAction.do only.

By the way, I am using BEA WebLogic 8.1 to test this.

Feb 18, 2009 01:48:30

The Java Servlet specification version 2.3 introduces a new component type, called a filter. A filter dynamically intercepts requests and responses to transform or use the information contained in the requests or responses. Filters typically do not themselves create responses, but instead provide universal functions that can be "attached" to any type of servlet or JSP page.

From Essential of Filters
Filter is used for intercepting both request and response.

try using /*.do for mapping

Feb 18, 2009 03:22:52

Vivek Kr Singh wrote:try using /*.do for mapping

hi Vivek , what is the difference between /*.do and *.do ?

Feb 18, 2009 03:31:41

Sorry thats a mistake it should be *.do.

/*.do will be an invalid pattern

Feb 18, 2009 20:21:12

Hi guys, I think you are missing the point. I want my filter to be activated for ALL requests coming from the client browser, not just .do only.

My point is, why is the filter activated for a forward? The JSP request does not come directly from the dlient; it is a forwarded request. From what I read from the specification, by default the filter should only be activated for requests coming directly from the client. I have explicitly stated this with <dispatcher>REQUEST</dispatcher> too. But it seems to have no effect.

Feb 18, 2009 20:41:39

Edmund Said:
From what I read from the specification, by default the filter should only be activated for requests coming directly from the client. I have explicitly stated this with <dispatcher>REQUEST</dispatcher> too.

I had a look at the Dispatcher element schema, here is what it mentions

The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE and ERROR. A value of FORWARD means the Filter will be applied under RequestDispatcher.forward() calls. A value of REQUEST means the Filter will be applied under ordinary client calls to the path or servlet. A value of INCLUDE means the Filter will be applied under RequestDispatcher.include() calls. A value of ERROR means the Filter will be applied under the error page mechanism. The absence of any dispatcher elements in a filter-mapping indicates a default of applying filters only under ordinary client calls to the path or servlet.

By default filter will be applied to the path or servlet. Path like "/*" means filter will be applied to everything after the context.
Maybe some one else can explain why REQUEST in Dispatcher does not prevent filter from being applied on actionMapping.findForward("test");
What are ordinary Client calls apart from client browser?

Feb 18, 2009 23:41:48

I think the <dispatcher> tag is applicable from servlet 2.4 onwards. On WebLogic 8.1, I believe that it is implementing servlet 2.3, which does not have this <dispatcher> tag. And therefore, the filter will be applied to everything. Can anyone confirm this?

A wop bop a lu bob a womp bam boom. Tutti frutti ad:

a bit of art, as a gift, the permaculture playing cards

https://gardener-gift.com