On Mon, Feb 6, 2012 at 5:43 PM, jsanca <[email protected]> wrote: > Hi All, > > As a common practice in Wicket we create IValidator objects for each > component we need to add a validation, there are some scenarios when we use > the same validator for several objects, so I was wondering if there is any > issue if I create a pooling to provide this validators > > Thread Safe issues >
Potentially. > Concurrency issues > Potentially. > Any other issue Potentially. Really, the question is: why? Sounds like premature optimization. Until you see that validators actually cause a problem there's no need to do it. If they do cause a problem, I can almost 300% guarantee that pooling them won't be the way to solve it. -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
