I have fixed the Localizer problem and committed it to the trunk. Thanks for pointing out the problem!
-Dan On Tue, May 27, 2008 at 1:19 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > getLocaliazer() in a constructor cant be done i guess because it will > nog be able to find any resources, expect the application one > > On 5/26/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > When I use the BeanForm I consistently get this disturbing message in > > the feedback panel: > > > > "An error occurred on the server. Your session may have timed out." > > > > It appears to be caused by: > > > > WARN - Localizer - Tried to retrieve a localized > > string for a component that has not yet been added to the page. This > > can sometimes lead to an invalid or no localized resource returned. > > Make sure you are not calling Component#getString() inside your > > Component's constructor. Offending component: [MarkupContainer > > [Component id = bean, page = <No Page>, path = bean.BeanForm]] > > > > And indeed, the BeanForm does this in its constructor: > > > > String serverErrorMsg = > > getLocalizer().getString("beanFormError.msg", this, "An error occurred > > on the server. Your session may have timed out."); > > form.add( new Label("beanFormIndicatorErrorLabel", > serverErrorMsg) > > ); > > > > (Lines 174 and 175) > > > > I've checked this in 1.0 and in 1.1-SNAPSHOT (built it fresh from trunk). > > > > Am I the first one to encounter this? > > > > Martijn > > >