The current solution is simple, but I thought there were objections because the Validator API is fairly independent of the internal wicket?
That was not the immediate concern, as classes implementing both interface would suffer the same problem. However, it is a point that still needs some thinking. So, I think we're close to a workable solution right now. But maybe not the perfect yet if you take this coupling into account. How would a completely decoupled version work though? Eelco
