To run Configleon within a (non-web) Spring application, or integration test, is essentially the same as a web application. One difference is that the ApplicationPropertyConfigurer propertyResources bean property needs to be set to the classpath location where the .property files are.

<bean class="com.configleon.configurer.ApplicationPropertyConfigurer">
    <property name="propertyResources">
        <bean class="com.configleon.resource.ApplicationPropertyResources">
            <property name="resourcePath" value="classpath:/org/jmesa/resource" />
        </bean>
    </property>
</bean>

Another difference from a web application is that only two configuration files can be declared. You can declare a config-global.properties file to hold all the common attributes, and then a file that corresponds to the environment. So, for example, the test environment for the JMesa project could have a file called config-test.properties file.

Like always you can always see exactly what Configleon is doing by looking at the logging output.