You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Jan Vermeulen <ja...@isencia.com> on 2007/07/03 13:51:22 UTC
Re: Problem with latest changes in FormComponent:validate()
Thanks for adding the 'INullAcceptingValidator'. This solves our problem in a
clean way.
Just a small suggestion: I've seen that the CompoundValidator does not
implement this interface. Would it not be correct to assure that the
CompoundValidator is called always, and that the same logic of checking the
implementation of the interface is applied to all the validators in the
chain ?
Jan.
--
View this message in context: http://www.nabble.com/Problem-with-latest-changes-in-FormComponent%3Avalidate%28%29-tf3945885.html#a11410534
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Problem with latest changes in FormComponent:validate()
Posted by Jan Vermeulen <ja...@isencia.com>.
I'll take a look at it. Thanks.
Jan.
--
View this message in context: http://www.nabble.com/Problem-with-latest-changes-in-FormComponent%3Avalidate%28%29-tf3945885.html#a11411421
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Problem with latest changes in FormComponent:validate()
Posted by Ryan Sonnek <ry...@gmail.com>.
Jan,
Just wanted to follow up with on this. If you're looking for tight
integration of wicket with hibernate annotations, please check out the
wicketstuff-hibernate project. I really think this would work well for
you. You've obviously been working in this area for a while, so if there
are any things you can recommend for the wicketstuff-hibernate project that
would help your project, let me know.
http://jroller.com/page/wireframe/?anchor=hibernateannotationcomponentconfigurator
Ryan
On 7/3/07, Jan Vermeulen <ja...@isencia.com> wrote:
>
>
> Thanks for adding the 'INullAcceptingValidator'. This solves our problem
> in a
> clean way.
>
> Just a small suggestion: I've seen that the CompoundValidator does not
> implement this interface. Would it not be correct to assure that the
> CompoundValidator is called always, and that the same logic of checking
> the
> implementation of the interface is applied to all the validators in the
> chain ?
>
> Jan.
> --
> View this message in context:
> http://www.nabble.com/Problem-with-latest-changes-in-FormComponent%3Avalidate%28%29-tf3945885.html#a11410534
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
Re: Problem with latest changes in FormComponent:validate()
Posted by Eelco Hillenius <ee...@gmail.com>.
> Thanks for adding the 'INullAcceptingValidator'. This solves our problem in a
> clean way.
>
> Just a small suggestion: I've seen that the CompoundValidator does not
> implement this interface. Would it not be correct to assure that the
> CompoundValidator is called always, and that the same logic of checking the
> implementation of the interface is applied to all the validators in the
> chain ?
Sounds reasonable, but I didn't implement it. Matej/ Igor?
Eelco