I understand that Mike, but shouldn't read-only throw the same error
(judging by the error message)?
I had client-side javascript for disabling elements too, but found it
unwieldy in the context of JSF lifecycle and complex component IDs. I am
much happier having it on the server-side, but when that is too
heavyweight I add some AJAX to lighten up the request.
It's just another option you might want to consider Oliver. By all
means, give Mike's suggestion a try as he generally knows what he is
talking about and it should be a "quicker fix".
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Mike Kienenberger wrote:
Jeff, he's doing this with javascript (clientside). Doing it in a
JSF-way would move that to server-side. The best thing to do is to
make it read-only.
On 3/15/07, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
Or better yet, disable it in a JSF way - ie, using the "disabled"
attribute of the component along with an "immediate" submit.
Mike Kienenberger wrote:
> JSF expects to get a value back from this component when the form is
> submitted. If you disable the element from javascript, that doesn't
> happen. Instead of disabling it, make it read-only.
>
> http://webdesign.about.com/od/forms/a/aa071805.htm
>
> On 3/15/07, Pfau, Oliver <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> what is meaning of this message:
>>
>> "WARNING: There should always be a submitted value for an input if
it is
>> rendered, its form is submitted, and it is not disabled or read-only
>> . Component : <...inputText>"
>>
>> <...inputText> is an input text field which could be enabled or
disabled
>> by javascript. I have other input text fields without this message.
Any
>> idea ?
>>
>> Regards,
>> Oliver
>>
>
>
>
