This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
When I called the action, I got the following result:
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.
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.
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.
Vivek Kr Singh
Joined: Oct 12, 2007
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?
Joined: Nov 16, 2003
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?