On 10/01/2013, at 9:42 PM, Johann Werner <
email@hidden> wrote:
Though this will only touch you if you are using the special property files that were introduced on 8 April 2012 by ERXPorperties.optionalPropertiesLoader(), i.e.:
Just to be clear, you're saying this is a backwards compatible change, in that there will be no change to property load order unless I actively do something? And what is the something? What causes that method to run? The Javadocs on that method in the integration branch explain (in outline) what that method does, but not under what circumstances it would be called. That is, how does one use these special properties files, or are they just picked up if they exist?
Properties.[Framework]
Properties.[Framework].[Username]
Properties.log4j
Properties.log4j.[Username]
Properties.database
Properties.database.[Username]
Properties.multilanguage
Properties.multilanguage.[Username]
Properties.migration
Properties.migration.[Username]
Ken Ishimoto updated the wiki accordingly: http://wiki.wocommunity.org/display/documentation/Project+Wonder+Properties+Files
The update to the wiki seems to add the new property file names to the list, but not much more.
Probably the only person using this (up to now ;-) is Ken himself so this shouldn't affect most of us.
I am guessing that the summary here is that it's all automagic: if I make no changes, then property load order remains the same. If I add one of those new files, it's loaded in the order indicated. Could someone confirm this for a start, and then perhaps elaborate on the rationale behind the new system? I assume it's just a nice way to split up what can otherwise be monolithic Properties files (so that I would put, say, database connection parameters in Properties.database), but I'd like to know for sure. A few paragraphs in the wiki would be super-helpful. Finally, the top-level Javadoc comment in that class would now seem to be stale given these changes.