Hi Ceki - the purpose of this configuration pattern is to be able to bundle the logback.xml file into the application WAR file, and have it reference a variable to where it can find the environment-specific configuration maintained externally. We don't want to have our customers needing to rebuild the war file for different environments. So the deployment context descriptor of the app would define the environment variables which logback picked up on via JNDI/comp/env, and the war file never changed.

Is there another way to achieve this configuration pattern with the new configuration behavior? I'd think that anyone using logback in a war package would need this type of mechanism.