I was working with Johannes on the problem... a quick follow up:

We'd prefer if we could add the validator to the component to allow
better reuse instead of somehow doing validation on form level.
However, the problem currently is, that ListView is no subclass of
FormComponent so it doesn't inherit the required behavior.

Is there a reason for this separation or why can't all components play
together with Forms? I think, a design based on interfaces instead of
abstract superclasses would allow greater flexibility here.

Regards,

-- 
Stefan Matthias Aust // Truth until paradox


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to