On 7/25/06, Jesse Alexander (KSFD 121)
<[EMAIL PROTECTED]> wrote:
> As just pointed out to me by Mike K. my solution goes against the jsf
> 1.1 spec. All of the form data will not be maintained as it would by
> using javascript+commandLink.
But, at least for those that are forced to use No_JS mode, you provide a
solution.
Thanks
I think it should be ok, that a commandlink does not preserve the
form-data.
That's what the buttons are for...
<h:commandLink> is supposed to preserve form-data. However,
outputLink does not, and you should be able to use that.
But as I noted in the jira issue, there's no reason why we can't
support this as an option for t:commandLink -- t:commandLink isn't
restricted by the JSF specification.
Just make sure that all of the implications for using it without
javascript are clearly documented in your patch.
