The reason for the Stack order, provided I recall correctly, assume you have self-contained component with all default properties required. Next you place the component in your apps, but you want to change the default properties, than the only place outside the jar is the any of the parent properties files. Make sense?
Ok, it makes sense (though I just replied to Igor it didn't :)) And thinking a little bit about it, I guess it is better than what I proposed from the view point of reusable components. So strike that.
To Johans point, I think the current implementation is too inflexible, it is far to difficult to change/extend/limit the search order easily if required. IMO this general design problem needs to be fixed.
Yep, I agree. The logic should be brought back to one place. So... we could open an issue for that, right? Eelco
