i think that was done so you can override properties of deeper components.
suppose i create a custom component, and this component uses key my.key in its markup and provides a default value in its .properties file. so how do you override that? right now its simple, just redefine my.key in the parent's properties file - since you built the parent you are in control there. -igor On 11/18/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 11/18/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > we should first go through it for the given language and then do it for the > default language > But quickly looking at that. > That won't be an easy fix, because the iteration through components is in > Localizer and the iteration over locale/style is in > XxxxStringResourceLoader Yeah, I noticed that too. The functionality is a bit shattered. > My personal opinion about the current resource loading that it does to much, > we support to many cases. It should be simplified. This one time I don't agree that simpler is better. We/ our users need real power here. What do you think about the the other point I mentioned? Eelco
