Thanks for that quick fix, a follow-up question though: Localizer uses IStringResourceLoader.loadStringResource(Component component, String key). While most of the IStringResourceLoader implementations correctly handle a null component as parameter, BundleStringResourceLoader doesn't - it needs a component to determine the locale. Wouldn't it make sense to use the Session locale as fallback if we don't have a component there?
cheers, Jonas On 8/30/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > > Yeah, it's a bug and it's already fixed. Either update to current trunk or > just set the logging treashold for Localizer class to ERROR. > > -Matej > > On 8/30/07, Jonas <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > It (1.3.0-beta3) does complain in if the component isn't added to the > page > > yet, > > but it also complains if the component is null. If I understand this > right > > (and if the javadoc is correct), it shouldn't complain in the latter > case. > > > > cheers, > > Jonas > > > > I'm not sure if this was fixed in 1.3, but the localizer should only > > > complain when the component is not yet added to it's parent (because > the > > > whole hierarchy can't be traversed to find the message). > > > > > >
