Yea, but if you don't create the validator yourself, you're totally
out of luck. What's wrong with validators holding state? They're just
going to attached to stateful components anyway. I mean, why stop
there? Let's make TextField thread safe too. :)

On 7/21/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> I guess resourceKey isn't such a good idea after all, as it breaks the
> thread safety we just introduced. It should be enough to remove this but
> make getResourceKey(FormComponent) overridable, so people can do this
> with annonymous classes. Slightly inconvient, but safe. And safe should
> win over inconvient.
> 
> Eelco
>


-------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to