I'm +1 only because while we break validation for this, I may be able to push through my setResourceKey(String) change. If it's not currently thread-safe, why are all the validators singletons?
On 7/20/05, Erik van Oosten <[EMAIL PROTECTED]> wrote: > +1 > > Wicket should not depend too much on the cleverness of the average > programmer, especially when we talk about making code thread safe. I > have seen this being underestimated too often already. > > Regards, > Erik. > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
