Hi, Access to pages in Wicket is synchronized, i.e. only one thread can manipulate the page. So, if you use non-static member fields then there is no problem. If you use static ones then you need to verify that they are thread safe and can be used in such a way.
On Mon, Oct 15, 2012 at 5:07 AM, Ondrej Zizka <ozi...@redhat.com> wrote: > Hi all, > > for repeaters, I didn't like adding a new validators, attribute > modifiers etc for each single row. > So I create just one and pass the reference. > > 1) Is it ok to have just one at component instance level? > > 2) Is it ok to make it a static final instance at app level? > > And about thread safety in general - is there some info about Wicket's > classes, with some Do's and Don't's? > Since Wicket gives a lot of freedom regarding hacking on it, I guess > users should be aware. > > Thanks, > Ondra > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
