Yes, I understand that. However, as you typically register an
implementation of IStringResourceLoader in the Application's init. It
functions therefore only as a callback mechanism for Wicket itself. At
least, that is how I read the intent of the code.
Now I understand you are able to request the list of IStringResourceLoaders
yourself and then to clever things with them. So my question actually comes
down to: do we want to maintain the interface for a method that is not
needed for Wicket itself? (Or are there plans to use it from within
Wicket?)
The deprecation route does not work. Current implementation are rightly
using this method and should not get warnings because of that.
Regards,
Erik.
On Tue, 30 Jun 2009 08:04:07 -0400, James Carman
<[email protected]> wrote:
> It's part of a public interface. You can't just remove it. Maybe the
> internal Wicket code doesn't use it, but that doesn't mean that
> someone else doesn't. Where are you thinking of removing it from? A
> 1.4-rcx or 1.5? I'd say you probably need to deprecate it before you
> remove it.
>
> On Tue, Jun 30, 2009 at 6:58 AM, Erik van Oosten<[email protected]>
> wrote:
>>
>> Hi,
>>
>> I am writing a custom IStringResourceLoader and noticed that
>> IStringResourceLoader#loadStringResource(Class,String,Locale,String) is
>> not
>> called from anywhere except from within the implementations themselves.
>>
>> Shall we remove the method from the interface, or did I miss other uses?
>>
>> Regards,
>> Erik.
>>
>> --
>> Erik van Oosten
>> http://day-to-day-stuff.blogspot.com
>>
>>
