no, it is not that common because you still have not defined what the
"common" object that knows about both values is. usually this is the
model, and it is not that uncommon to do this:
new form() {
onsubmit() {
if (!getmodel().validate()) { error("something went bad"); }
}
}
ie validate after the form has been submitted
-igor
On Wed, Sep 22, 2010 at 10:54 AM, splitshade
<martin.dil...@googlemail.com> wrote:
>
> Hi again,
>
> well, i think the validator would be applied to the form, to which both
> panels are added, but you are right, there is nothing that is aware of both
> components (or more exactly on the inner components of the panels).
>
> Model-Validation sounds good, but the Model itself is updated after
> validation-phase,
> so propably i would need to implement further logic in updateModel().. or
> something.
>
> But I'm confused that there is no default way of handling such problems,
> this is a common use case, isn't it? Ok, not all too common, but possible.
>
> Thanks for your help!
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Inter-Component-Validation-or-how-to-marry-two-strangers-tp2550675p2550781.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
