We'd have to have a good reason the break the API. And it's just something you'd prefer to be different, but it doesn't give you troubles you can't get around, right? :-)
Eelco On Mon, Jun 9, 2008 at 3:21 AM, Stefan Simik <[EMAIL PROTECTED]> wrote: > > Oh yes :-) > I think, that taking Locale from session could be the most used => the most > suitable default strategy. > Session is the most used place for storing Locale. > I think, that preferred way should be getting Locale from Session as > default. > Passing Locale parameter to the PackageResource constructor does'nt seem to > me like a better way. > Who wants, can subclass PackageResource and override in you own specific > way. > What do you think about it ? > > Stefan > > > > > That's just by design to not make the assumption where the locale > comes from. But you can override the class and pass > Session.get().getLocale() and you're done :-) > > Eelco > > -- > View this message in context: > http://www.nabble.com/PackageResource---why-does%27nt-get-Locale-directly-from-Session---tp17696134p17730001.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
