What is doFilter doing in doFilter method in filters of java?

Question

I wanna know that in our dofilter method i made this call chain.doFilter. What is doFilter doing inside a doFilter?Is it not gonna get recursive call?

Answer 1

It is calling the doFilter method of the chain object, not itself, so no, it won't be recursive.

The name chain suggests that you have a sequence of filters, with each filter doing some processing and then passing on to the next in sequence, so each object has a chain member to point to the next filter in the sequence, which gets called after the filter has performed its own processing. The last in the sequence will then probably have null as the chain value, or it knows on its own that it is the last one in the sequence.

Answer 2

Internally it invokes doFilter of the next filter in the filter chain, and, when chain is over, it invokes the target servlet.

Answer 3

Servlet Filters are an implementation of the Chain of responsibility design pattern.

All fileters are chainged (in the order of their definition in web.xml). The chain.doFilter() is proceeding to the next element in the chain. The last element of the chain is the target resource/servlet.

Answer 4

By calling chain.doFilter you are handing the request/response to the next filter in your filter chain. If you do not call it then the next filter (probably defined in your web.xml) will not be executed.

If you just called doFilter, then yes you would have endless recursion and a stackoverflow. However, you are calling the doFilter method of the filterChain object, which instructs it to execute the next filter.

Answer 5

Not having any code that you are talking about, I can only assume that you something like:

class Filter implements FilterAPI {
  private FilterAPI chain;
  Filter(FilterAPI chain) { this.chain = chain; }
  @override void doFilter (Set setToFilter) {
    // do some filtering
    chain.doFilter(setToFilter);
  }
}

If that is the case, then you are not calling anything recursively, you are calling doFilter() on a different object. As mentioned on an another answer, this is the well known Chain of Responsibility design pattern.