On 5/5/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> My question actually isn't about an alternate way to do it, but rather
> where is it stated that giving a particular hidden field some
> particular value will result in some particular JSF behavior?
> How did the author know that setting this hidden
> field's value to its id will do the trick in all JSF implementations?
The behavior of all the standard component renderers are documented in the
"render kit docs" that come with the RI ... and, indeed, the fact that
clicking on an <h:commandLink> must cause the form to be submitted is part
of the required behavior. The precise technique used is not mandated, but
it's certainly going to involve some sort of JavaScript.
Thanks, Craig. I'll look for said render kit docs. Again, it's not
the use of javascript or submission of the form I'm looking for. It's
the documentation for this:
//This is an emulation of the action link being clicked.
hform[form+':'+target].value=form+':'+target;
I want to know how the author knew this trick would work in all JSF
implementations. Unlike something like Struts, where I can just read
the source code to know what tricks will work, with JSF, I can't just
read the MyFaces source code, or the RI (when it even has source code,
cause some of it doesn't), to know the code I'll write will always
work.
thanks,
Hubert
