2008/6/30 Scott Swank <[EMAIL PROTECTED]>: > The ComponentStringResourceLoader uses an Iterator named something > like (no code in front of me) "ResourceNameIterator". This iterator > is used to find resources and markup. You can't just set it on the > Application.getResourceSettings (though I should create a jira & patch > for that...), so you have to subclass the main string and markup > loaders to use your own iterator. Then you put those loaders on > Application.getResouceSettings.
Yes, it would be useful to be able to replace/configure the ResourceNameIterator with a custom one (even be able to override a createResourceNameIterator method could be a useful quick fix). In the meantime I think I'll override the whole loadStringResources in Component*Loader. Igor, your suggestion is correct, but we are just moving away the messages from the application file because there are too many. For each "entity" we have two pages (the search/list and the detail/edit) sharing the same column headers/field labels. So this situation is recurring in our application and the file is growing too much. Thanks, bye Lorenzo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
