The following are just a few samples of logging statements that come out on my Tomcat 7 console. Most are coming from open saml or hibernate and I'm trying to prevent them from coming out. I am using logback and have the root logger and all other loggers at WARN or above and I can't figure out why certain libraries continue to log out INFO and DEBUG level statements. Any ideas?
14:40:45.360 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Username intialized and configuration cached
14:40:45.360 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - Initializing object provider {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken
14:40:45.360 [localhost-startStop-6] DEBUG org.opensaml.xml.Configuration - Registering new builder, marshaller, and unmarshaller for {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken
14:40:45.361 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken intialized and configuration cached
14:40:45.361 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - ObjectProviders load complete14:40:45.361 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - Preparing to load IDAttributes
14:40:45.361 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - IDAttribute {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd}Id has been registered
14:40:45.361 [localhost-startStop-6] DEBUG org.opensaml.xml.XMLConfigurator - IDAttributes load complete
14:40:45.361 [localhost-startStop-6] DEBUG org.opensaml.DefaultBootstrap - Initializing SAML Artifact builder factories