Hi, at the moment, the content of the properties file drives what is expected in the ConfigurationComposite. If there are more properties than there are declared and matching Proprety<> methods, then there is an Exception.
This might have been rational back in the days when this was discussed first time, but if we are heading towards supporting external and perhaps more exotic configuration "supply-chains", then I think it would be more logical that the ConfigurationComposite simply reads what it wants and ignores everything else. AND then would could have this super cool addition that if no files are found that works, fall back to System.getProperties() and System.getenv() as the final backups. WDYT? Cheers -- Niclas Hedhman, Software Developer http://polygene.apache.org - New Energy for Java
