<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    隨筆-295  評論-26  文章-1  trackbacks-0
    Class FilterChainProxy
    java.lang.Objectextended by org.acegisecurity.util.FilterChainProxy
    All Implemented Interfaces:
    Filter, InitializingBean, ApplicationContextAware

    public class FilterChainProxy
    extends Object
    implements Filter, InitializingBean, ApplicationContextAware

    Delegates Filter requests to a list of Spring-managed beans.

    通過一系列的由spring托管的beans ,代理過濾請求。
    FilterChainProxy 通過在web.xml中定義的FilterToBeanProxy 被加載,F(xiàn)ilterChainProxy 將會通過init(FilterConfig), destroy() and doFilter(ServletRequest, ServletResponse, FilterChain)調用,調用每一個在其中定義的過濾器。

    The FilterChainProxy is loaded via a standard FilterToBeanProxy declaration in web.xml. FilterChainProxy will then pass init(FilterConfig), destroy() and doFilter(ServletRequest, ServletResponse, FilterChain) invocations through to each Filter defined against FilterChainProxy.

    ?
    ??? FilterChainProxy? 是通過一個標準的FilterInvocationDefinitionSource 來實現(xiàn)配置的,每個可能的FilterChainProxy應該服務的URI模式都必須進入
    ??????????? 第一個搭配的URI模式將會被用來定義處理請求的所有的過濾器,就是說只適配第一組過濾器,后面的其他過濾器將無效。
    FilterChainProxy
    is configured using a standard FilterInvocationDefinitionSource. Each possible URI pattern that FilterChainProxy should service must be entered. The first matching URI pattern located by FilterInvocationDefinitionSource for a given request will be used to define all of the Filters that apply to that request. NB: This means you must put most specific URI patterns at the top of the list, and ensure all Filters that should apply for a given URI pattern are entered against the respective entry. The FilterChainProxy will not iterate the remainder of the URI patterns to locate additional Filters. The FilterInvocationDefinitionSource described the applicable URI pattern to fire the filter chain, followed by a list of configuration attributes. Each configuration attribute's ConfigAttribute.getAttribute() corresponds to a bean name that is available from the application context.

    FilterChainProxy respects normal handling of Filters that elect not to call Filter.doFilter(javax.servlet.ServletRequest, javax.servlet.ServletResponse, javax.servlet.FilterChain), in that the remainder of the origial or FilterChainProxy-declared filter chain will not be called.

    It is particularly noted the Filter lifecycle mismatch between the servlet container and IoC container. As per FilterToBeanProxy JavaDocs, we recommend you allow the IoC container to manage lifecycle instead of the servlet container. By default the FilterToBeanProxy will never call this class' init(FilterConfig) and destroy() methods, meaning each of the filters defined against FilterInvocationDefinitionSource will not be called. If you do need your filters to be initialized and destroyed, please set the lifecycle initialization parameter against the FilterToBeanProxy to specify servlet container lifecycle management.

    If a filter name of TOKEN_NONE is used, this allows specification of a filter pattern which should never cause any filters to fire.



    大盤預測 國富論
    posted on 2007-09-12 16:20 華夢行 閱讀(1941) 評論(0)  編輯  收藏 所屬分類: Spring
    主站蜘蛛池模板: 一级毛片**免费看试看20分钟| 亚洲国产高清美女在线观看| 免费国产叼嘿视频大全网站| 亚洲国产成人精品无码一区二区 | 亚洲AV无码欧洲AV无码网站| 男女免费观看在线爽爽爽视频| 国产精品亚洲色婷婷99久久精品| 亚洲成人午夜在线| 亚洲精品无码av天堂| 永久久久免费浮力影院| 精品国产无限资源免费观看| 成人A片产无码免费视频在线观看| 亚洲高清国产拍精品熟女| 久久亚洲精品国产精品黑人| 伊人久久大香线蕉亚洲| 亚洲国产高清在线一区二区三区| 成人黄页网站免费观看大全| 99re这里有免费视频精品| 日韩免费在线视频| 亚洲成人动漫在线| 国产自产拍精品视频免费看| 和日本免费不卡在线v| 国产成人免费高清激情视频| 亚洲精品在线免费看| 国产精品入口麻豆免费观看| 91久久成人免费| 青苹果乐园免费高清在线| 成人毛片免费视频| 亚洲电影日韩精品| 亚洲精品国产品国语在线| 亚洲精选在线观看| 亚洲夂夂婷婷色拍WW47| 一级毛片免费一级直接观看| 日本在线看片免费人成视频1000 | 亚洲AV美女一区二区三区| 亚洲福利视频一区二区三区| 亚洲熟女综合一区二区三区| 男女男精品网站免费观看| 精品无码国产污污污免费网站 | 久久精品免费网站网| 精品成在人线AV无码免费看 |