i'm thinking off the top of my head, but i don't think this is a problem.
the locale /always/ comes from the session. in component.java:
public final Locale getLocale()
{
return getSession().getLocale();
}
Juergen Donnerstag wrote:
While playing a bit with this idea. A container's constructor does not
know the current locale (required to find the markup). Though you
might use getSession(), it is actually the wrong session/locale you
are using, as it is the session/locale of the current page which
requested to load the new one. At the time the new page gets rendered,
the locale might have been changed.
Juergen
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
