we are setting the locale because then you don't have to get it from the request yourself. Thats the wicket way. Abstract you from the http request and response objects.
johan On 1/5/07, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
in my opinion, i even dont understand why the core sets a locale, wicket itself dont need it - everything that is needed should be specified by the application programmer - if he needs a locale he will put one into a extended class as nice as he wants it (and with J5EE its relly nice as you can have a Static CustomClass getCustomClass returning your CustomClass) and if he neednt a locale he will not take care about it... just my 2 cents > -----Ursprüngliche Nachricht----- > Von: Eelco Hillenius [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 5. Januar 2007 06:45 > An: [email protected] > Betreff: http://issues.apache.org/jira/browse/WICKET-151 > > any others have an opinion about > http://issues.apache.org/jira/browse/WICKET-151 ? > > Eelco >
