i've just debugged a problem with our apps since updating wonder to the
latest nightly. the issue was no db connectivity, which was caused by a
wrong connection url. the connection url was specified in the applications
properties, but then also in the WebObjects.properties file in my user home
directory. since updating to the latest wonder the value specified in my
WebObjects.properties file was not overriding that specified in the
applications properties file.
I have another eclipse workspace which is at Wonder 9808 and i can confirm
that identical revisions of our code run against that specific wonder
revision do not exhibit the same behaviour: the values specified in the
WebObjects.properties file override the application properties as expected -
so it appears to have been introduced some time since then.
I can see in the svn commit logs that there was a chunk of quite major
refactoring done to ERXConfigurationManager on 22 september (wonder 9923 /
9925 / 9926 / 9927 - the latter of which is the current version). the
javadoc wasn't modified through those revisions so i presume there was no
intention to change the behaviour ?
i've also just done a silly test to make sure. i've put a property in my
application properties file called "sillytest" and set it to "foo". I've
then specified the same property in my WebObjects.properties file and set it
to "bar". just before loadConfiguration is called (line 204 of
ERXConfigurationManager) the value of this property is "bar". just after it
is "foo". so ERXConfigurationManager is switching the value for that
property from the one specified in WebObjects.properties to the value
specified in the application's properties.
Get latest updates about Open Source Projects, Conferences and News.