It's ok, just wanted to verify if this was the current usage of the
name. Always easier to have a workaround than to ask for some big
change which probably does not benefit too many people ;)
(not using id as js validator works with name, but it can also
optionally work with embedded css class metadata. Going to use that
approach now)
Thanks!
On 24 Oct 2007, at 12:43 PM, Eelco Hillenius wrote:
I am trying to integrate my wicket application to use jquery
validator plugin, and specifying the rules in a js file.
The js file will need to identify the input by the name of
the input.
It worked fine in plain html markup, but when I ran it in
wicket I
was unable to validate. Apparently wicket modifies the name of the
input.
It does this so that it can find the form submitted values back. It
might be possible to 'fix' this but that is possibly hairy. An easy
workaround is to use the same ids for your form components as the
names you want to use.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]