Hi, 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).
-Matej On 8/30/07, Jonas <[EMAIL PROTECTED]> wrote: > > Hi, > > after having upgraded 1.3.0-beta3, I noticed that the Localizer now > complains > in the log if getString is called with 'null' as component, even though > the > javadoc > for this method states that the component is optional. > I'm not sure if the missing component has any further effects than > deactivating > the Localizer's cache (is that caching necessary anyway?) - could anyboy > shed > some light upon me? > A related question would be how to use the Localizer when I'm in a context > where I have no way of accessing the related component, e.g. for localized > Strings in a DynamicImageResource. Shouldn't I use the Localizer in that > case, > or what's the idea? > > Thanks, > Jonas >
