Carsten Ziegeler wrote:
Luca Morandini schrieb:
Carsten Ziegeler wrote:
Luca Morandini wrote:
This was neatly solved by the use of WEB-INF/cocoon/properties, since it
was loaded after the "classpath:*" chain.
Yes, you're right. Hmm, perhaps we should load properties from
WEB-INF/classes last. I'll have a look at that as well.
Last ? Hmm... I'm not sure I got you point.
Yepp, the properties system works in the way that the last definition
wins. And this means that project-wide stuff has to be loaded last.
So, the chain you propose is (sorted by order of loading):
1) WEB-INF/classes/META-INF/cocoon/properties (block-wide stuff).
2) WEB-INF/classes/cocoon/properties (project-wide stuf).
In truth, I don't find the use of "classes" for configuration stuff done
outside JARs particularly intuitive... I'd rather stick with
WEB-INF/cocoon/properties.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
