@@ -0,0 +1,1181 @@
+package org.springframework.security.config;%0A%0Aimport org.springframework.beans.factory.config.BeanDefinitionHolder;%0Aimport org.springframework.beans.factory.xml.BeanDefinitionDecorator;%0Aimport org.springframework.beans.factory.xml.ParserContext;%0Aimport org.w3c.dom.Node;%0A%0A/**%0A * No longer used in Spring Security 3, other than to report a warning. The &lt;custom-filter&gt; elements should%0A * be placed within the &lt;http&gt; block. See SEC-1186.%0A *%0A * @author Luke Taylor%0A * @version $Id$%0A */%0Apublic class CustomFilterBeanDefinitionDecorator implements BeanDefinitionDecorator %7B%0A%0A    public BeanDefinitionHolder decorate(Node node, BeanDefinitionHolder holder, ParserContext parserContext) %7B%0A        parserContext.getReaderContext().warning(%22The use of %3Ccustom-filter /%3E within a filter bean declaration %22 +%0A                %22is not supported in Spring Security 3.0+. If you are using Spring 3.0+, you should be place the %22 +%0A                %22%3Ccustom-filter /%3E element within the %22 +%0A                %22%3Chttp%3E block in our configuration and add a 'ref' attribute which points to your filter bean%22,%0A                parserContext.extractSource(node));%0A%0A        return holder;%0A    %7D%0A%7D%0A

Remove functionality from CustomFilterBeanDefinitionDecorator and report a warning instead.