<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:p="http://www.springframework.org/schema/p"
       xmlns:c="http://www.springframework.org/schema/c"
       xmlns:util="http://www.springframework.org/schema/util"
       xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
       http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util.xsd">

    <description>
        Log4J initialization.  Configuration options are sourced from cas.properties.  This allows deployers to externalize
        both cas.properties and log4j.xml, so that a single cas.war file can be deployed to multiple tiers or hosts without
        having to do any post configuration.  This approach helps to preserve configuration between upgrades.

        Deployers should not have to edit this file.
    </description>

    <bean id="log4jInitialization" class="org.jasig.cas.util.CasLoggerContextInitializer"
            c:logConfigurationField="log4jConfiguration"
            c:logConfigurationFile="file:///var/lib/tomcat6/webapps/cas4/WEB-INF/classes/log4j2.xml"
            c:loggerContextPackageName="org.apache.logging.log4j.web"/>

<!--
            c:logConfigurationFile="${log4j.config.location:classpath:log4j2.xml}"
-->


</beans>