Luke Taylor (Migrated from SEC-1202) said:
SpringSecurityFilter was a good idea in terms of avoiding duplicated code, but the doFilter() and doFilterHttp() methods make the stack trace double the size and thus harder to read. It also looks like the overhead from Spring Security's filter chain is more than it actually is.
Luke Taylor said:
I've replaced the use of SpringSecurityFilter with spring-web's GenericFilterBean. Also removed the init() and destroy() methods from FilterChainProxy which called the corresponding filter chain methods, contradicting the description in the Javadoc.