Roald Bankras (Migrated from SEC-1868) said:
Currently the SecurityNamespaceHandler logs an error if the FilterChainProxy is not available on the classpath.
This should be turned back to an if instead of a try/catch and it should definitely not log an error message
Rob Winch said:
Thank you for your bug submission. A fix has been pushed to master.
For the interested...This was introduced with the desire to provide the user with more details when FilterChainProxy failed to load (i.e. FilterChainProxy was not found, Filter was not found etc) and was being used. The fix I pushed to master changed the init method to use ClassUtils.isPresent again and removed the logger.error statement. To get more details it attempts to load FilterChainProxy again when reporting the error to get a detailed error message.