DelegatingFilterProxy分析

前言

最近在分析源码时发现了一个配置如下：

#web.xml文件中
<filter>
    <filter-name>cacheSessionFilter</filter-name>
    <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
    <init-param>
        <param-name>targetFilterLifecycle</param-name>
        <param-vale>true</param-value>
    </init-param>
</filter>
<filter-mapping>
    <filter-name></filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

#applicationContext.xml文件
<bean name="cacheSessionFilter"  class="xxxx.xxx.xxFilter"/>

那么这个DelegatingFilterProxy到底是干嘛用的那？？？网上查了很多，最终总结为一句话即：DelegateFilterProxy实现了服务器容器（tomcate was等）中的filter调用spring容器中类的功能，那这是如何实现的那？

DelegatingFilterProxy和spring容器如何关联的？

观察web.xml文件，spring的初始化一般都是在非常靠前的，也就是说在使用delegatingfilterproxy之前，spring容器已经初始化完成了，然后观察delegatingfilterproxy的源码会发现有这么一段

protected void initFilterBean() throws ServletException {
        synchronized (this.delegateMonitor) {
            if (this.delegate == null) {
                // If no target bean name specified, use filter name.
                if (this.targetBeanName == null) {
                    this.targetBeanName = getFilterName();
                }
                // Fetch Spring root application context and initialize the delegate early,
                // if possible. If the root application context will be started after this
                // filter proxy, we'll have to resort to lazy initialization.
                WebApplicationContext wac = findWebApplicationContext();
                if (wac != null) {
                    this.delegate = initDelegate(wac);
                }
            }
        }
    }

没错WebApplicationContext其实就是spring容器，也就是说DelegatingFilterProxy中保存有spring的容器，而在WebApplicationContext中有一个和DelegatingFilerProxy同名的类（这个类就是我们自己的类），DelegatingFilterProxy会从WebApplicationContext中寻找那个和其同名的类，然后将所有的动作赋予给它。

public void doFilter(ServletRequest request, ServletResponse response, FilterChain filterChain)
            throws ServletException, IOException {

        // Lazily initialize the delegate if necessary.
        Filter delegateToUse = this.delegate;
        if (delegateToUse == null) {
            synchronized (this.delegateMonitor) {
                delegateToUse = this.delegate;
                if (delegateToUse == null) {
                    WebApplicationContext wac = findWebApplicationContext();
                    if (wac == null) {
                        throw new IllegalStateException("No WebApplicationContext found: " +
                                "no ContextLoaderListener or DispatcherServlet registered?");
                    }
                    delegateToUse = initDelegate(wac);
                }
                this.delegate = delegateToUse;
            }
        }

        // Let the delegate perform the actual doFilter operation.
        invokeDelegate(delegateToUse, request, response, filterChain);
    }

其中的delegateToUse就是从webapplicationcontext中取出来的：

@Override
    protected void initFilterBean() throws ServletException {
        synchronized (this.delegateMonitor) {
            if (this.delegate == null) {
                // If no target bean name specified, use filter name.
                if (this.targetBeanName == null) {
                    this.targetBeanName = getFilterName();
                }
                // Fetch Spring root application context and initialize the delegate early,
                // if possible. If the root application context will be started after this
                // filter proxy, we'll have to resort to lazy initialization.
                WebApplicationContext wac = findWebApplicationContext();
                if (wac != null) {
                    this.delegate = initDelegate(wac);
                }
            }
        }
    }