Luca Morandini wrote: > Carsten Ziegeler wrote: >> In the last months we changed the handling of properties and >> configurations files several times. >> >> The current implementation is a clean solution which reads configuration >> files from the classpath. While this is a very nice solution, especially >> for distributing components, it has the drawback that currently users >> have to put their own global configuration either into a jar file or >> into WEB-INF/classes/META-INF/cocoon. >> >> (I recently updated this mechanism to give properties from >> WEB-INF/classes precedence over jar files). > > Meaning they are loaded *after* the properties in JARs, right ? > Yes :) (And the last definition wins)
Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
