You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by "Pfau, Oliver" <ol...@siemens.com> on 2007/03/15 11:18:03 UTC
MyFaces 1.1.5 warning message on console
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
Re: MyFaces 1.1.5 warning message on console
Posted by Mike Kienenberger <mk...@gmail.com>.
Thanks, Oliver. I've gone ahead and added an additional
recommendation as well.
On 3/19/07, Mike Kienenberger <mk...@gmail.com> wrote:
> Ok. It's good to know that.
>
> Can you open a JIRA issue noting that the error message should be
> changed to remove the "or read-only" part? It is probably worth
> noting that the warning should recommend changing from disabled to
> read-only.
>
> "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>"
>
>
> On 3/19/07, Pfau, Oliver <ol...@siemens.com> wrote:
> > Ok...I misunderstood this...the warning does not appear when I use readOnly...
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: weber.volker@googlemail.com [mailto:weber.volker@googlemail.com] Im Auftrag von Volker Weber
> > Gesendet: Montag, 19. März 2007 16:17
> > An: MyFaces Discussion
> > Betreff: Re: MyFaces 1.1.5 warning message on console
> >
> > Oliver,
> >
> > Mike asked you to toggle readonly instead of disabled.
> >
> > You will always get this message if you change the disabled state on
> > client to false.
> >
> > The reason is: for disabled input tags the value is not submitted to
> > the server,
> > on the server the related component is not disabled, so a value is
> > expected in the request.
> >
> > Regards,
> > Volker
> >
> > 2007/3/19, Pfau, Oliver <ol...@siemens.com>:
> > > I only toggle the disabled attribute of the input from true to false. If true the warning appears....if false it does not. I do not toggle read-only.
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Mike Kienenberger [mailto:mkienenb@gmail.com]
> > > Gesendet: Freitag, 16. März 2007 16:37
> > > An: MyFaces Discussion
> > > Betreff: Re: MyFaces 1.1.5 warning message on console
> > >
> > > Oliver,
> > >
> > > If the error goes away after you switch from disabled to read-only,
> > > can you please open a JIRA issue on the error message? We should
> > > change it to remove the part about read-only.
> > >
> > >
> > > On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> > > > No I am using no AJAX.
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> > > > Gesendet: Donnerstag, 15. März 2007 18:48
> > > > An: MyFaces Discussion
> > > > Betreff: Re: MyFaces 1.1.5 warning message on console
> > > >
> > > > Are you using AJAX?
> > > >
> > > > Pfau, Oliver 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
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
Re: MyFaces 1.1.5 warning message on console
Posted by Mike Kienenberger <mk...@gmail.com>.
Ok. It's good to know that.
Can you open a JIRA issue noting that the error message should be
changed to remove the "or read-only" part? It is probably worth
noting that the warning should recommend changing from disabled to
read-only.
"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>"
On 3/19/07, Pfau, Oliver <ol...@siemens.com> wrote:
> Ok...I misunderstood this...the warning does not appear when I use readOnly...
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: weber.volker@googlemail.com [mailto:weber.volker@googlemail.com] Im Auftrag von Volker Weber
> Gesendet: Montag, 19. März 2007 16:17
> An: MyFaces Discussion
> Betreff: Re: MyFaces 1.1.5 warning message on console
>
> Oliver,
>
> Mike asked you to toggle readonly instead of disabled.
>
> You will always get this message if you change the disabled state on
> client to false.
>
> The reason is: for disabled input tags the value is not submitted to
> the server,
> on the server the related component is not disabled, so a value is
> expected in the request.
>
> Regards,
> Volker
>
> 2007/3/19, Pfau, Oliver <ol...@siemens.com>:
> > I only toggle the disabled attribute of the input from true to false. If true the warning appears....if false it does not. I do not toggle read-only.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Mike Kienenberger [mailto:mkienenb@gmail.com]
> > Gesendet: Freitag, 16. März 2007 16:37
> > An: MyFaces Discussion
> > Betreff: Re: MyFaces 1.1.5 warning message on console
> >
> > Oliver,
> >
> > If the error goes away after you switch from disabled to read-only,
> > can you please open a JIRA issue on the error message? We should
> > change it to remove the part about read-only.
> >
> >
> > On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> > > No I am using no AJAX.
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> > > Gesendet: Donnerstag, 15. März 2007 18:48
> > > An: MyFaces Discussion
> > > Betreff: Re: MyFaces 1.1.5 warning message on console
> > >
> > > Are you using AJAX?
> > >
> > > Pfau, Oliver 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
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
>
AW: MyFaces 1.1.5 warning message on console
Posted by "Pfau, Oliver" <ol...@siemens.com>.
Ok...I misunderstood this...the warning does not appear when I use readOnly...
-----Ursprüngliche Nachricht-----
Von: weber.volker@googlemail.com [mailto:weber.volker@googlemail.com] Im Auftrag von Volker Weber
Gesendet: Montag, 19. März 2007 16:17
An: MyFaces Discussion
Betreff: Re: MyFaces 1.1.5 warning message on console
Oliver,
Mike asked you to toggle readonly instead of disabled.
You will always get this message if you change the disabled state on
client to false.
The reason is: for disabled input tags the value is not submitted to
the server,
on the server the related component is not disabled, so a value is
expected in the request.
Regards,
Volker
2007/3/19, Pfau, Oliver <ol...@siemens.com>:
> I only toggle the disabled attribute of the input from true to false. If true the warning appears....if false it does not. I do not toggle read-only.
>
> -----Ursprüngliche Nachricht-----
> Von: Mike Kienenberger [mailto:mkienenb@gmail.com]
> Gesendet: Freitag, 16. März 2007 16:37
> An: MyFaces Discussion
> Betreff: Re: MyFaces 1.1.5 warning message on console
>
> Oliver,
>
> If the error goes away after you switch from disabled to read-only,
> can you please open a JIRA issue on the error message? We should
> change it to remove the part about read-only.
>
>
> On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> > No I am using no AJAX.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> > Gesendet: Donnerstag, 15. März 2007 18:48
> > An: MyFaces Discussion
> > Betreff: Re: MyFaces 1.1.5 warning message on console
> >
> > Are you using AJAX?
> >
> > Pfau, Oliver 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
> > >
> > >
> > >
> >
> >
> >
> >
>
Re: MyFaces 1.1.5 warning message on console
Posted by Andrew Robinson <an...@gmail.com>.
I am using AJAX, and have seen this error. Is it possible to disable
this warning when it is expected due to AJAX functionality?
On 3/19/07, Volker Weber <v....@inexso.de> wrote:
> Oliver,
>
> Mike asked you to toggle readonly instead of disabled.
>
> You will always get this message if you change the disabled state on
> client to false.
>
> The reason is: for disabled input tags the value is not submitted to
> the server,
> on the server the related component is not disabled, so a value is
> expected in the request.
>
> Regards,
> Volker
>
> 2007/3/19, Pfau, Oliver <ol...@siemens.com>:
> > I only toggle the disabled attribute of the input from true to false. If true the warning appears....if false it does not. I do not toggle read-only.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Mike Kienenberger [mailto:mkienenb@gmail.com]
> > Gesendet: Freitag, 16. März 2007 16:37
> > An: MyFaces Discussion
> > Betreff: Re: MyFaces 1.1.5 warning message on console
> >
> > Oliver,
> >
> > If the error goes away after you switch from disabled to read-only,
> > can you please open a JIRA issue on the error message? We should
> > change it to remove the part about read-only.
> >
> >
> > On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> > > No I am using no AJAX.
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> > > Gesendet: Donnerstag, 15. März 2007 18:48
> > > An: MyFaces Discussion
> > > Betreff: Re: MyFaces 1.1.5 warning message on console
> > >
> > > Are you using AJAX?
> > >
> > > Pfau, Oliver 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
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
>
Re: MyFaces 1.1.5 warning message on console
Posted by Volker Weber <v....@inexso.de>.
Oliver,
Mike asked you to toggle readonly instead of disabled.
You will always get this message if you change the disabled state on
client to false.
The reason is: for disabled input tags the value is not submitted to
the server,
on the server the related component is not disabled, so a value is
expected in the request.
Regards,
Volker
2007/3/19, Pfau, Oliver <ol...@siemens.com>:
> I only toggle the disabled attribute of the input from true to false. If true the warning appears....if false it does not. I do not toggle read-only.
>
> -----Ursprüngliche Nachricht-----
> Von: Mike Kienenberger [mailto:mkienenb@gmail.com]
> Gesendet: Freitag, 16. März 2007 16:37
> An: MyFaces Discussion
> Betreff: Re: MyFaces 1.1.5 warning message on console
>
> Oliver,
>
> If the error goes away after you switch from disabled to read-only,
> can you please open a JIRA issue on the error message? We should
> change it to remove the part about read-only.
>
>
> On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> > No I am using no AJAX.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> > Gesendet: Donnerstag, 15. März 2007 18:48
> > An: MyFaces Discussion
> > Betreff: Re: MyFaces 1.1.5 warning message on console
> >
> > Are you using AJAX?
> >
> > Pfau, Oliver 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
> > >
> > >
> > >
> >
> >
> >
> >
>
AW: MyFaces 1.1.5 warning message on console
Posted by "Pfau, Oliver" <ol...@siemens.com>.
I only toggle the disabled attribute of the input from true to false. If true the warning appears....if false it does not. I do not toggle read-only.
-----Ursprüngliche Nachricht-----
Von: Mike Kienenberger [mailto:mkienenb@gmail.com]
Gesendet: Freitag, 16. März 2007 16:37
An: MyFaces Discussion
Betreff: Re: MyFaces 1.1.5 warning message on console
Oliver,
If the error goes away after you switch from disabled to read-only,
can you please open a JIRA issue on the error message? We should
change it to remove the part about read-only.
On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> No I am using no AJAX.
>
> -----Ursprüngliche Nachricht-----
> Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> Gesendet: Donnerstag, 15. März 2007 18:48
> An: MyFaces Discussion
> Betreff: Re: MyFaces 1.1.5 warning message on console
>
> Are you using AJAX?
>
> Pfau, Oliver 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
> >
> >
> >
>
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Mike Kienenberger <mk...@gmail.com>.
Oliver,
If the error goes away after you switch from disabled to read-only,
can you please open a JIRA issue on the error message? We should
change it to remove the part about read-only.
On 3/16/07, Pfau, Oliver <ol...@siemens.com> wrote:
> No I am using no AJAX.
>
> -----Ursprüngliche Nachricht-----
> Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
> Gesendet: Donnerstag, 15. März 2007 18:48
> An: MyFaces Discussion
> Betreff: Re: MyFaces 1.1.5 warning message on console
>
> Are you using AJAX?
>
> Pfau, Oliver 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
> >
> >
> >
>
>
>
>
AW: MyFaces 1.1.5 warning message on console
Posted by "Pfau, Oliver" <ol...@siemens.com>.
No I am using no AJAX.
-----Ursprüngliche Nachricht-----
Von: Jeff Bischoff [mailto:jbischoff@klkurz.com]
Gesendet: Donnerstag, 15. März 2007 18:48
An: MyFaces Discussion
Betreff: Re: MyFaces 1.1.5 warning message on console
Are you using AJAX?
Pfau, Oliver 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
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Jeff Bischoff <jb...@klkurz.com>.
Are you using AJAX?
Pfau, Oliver 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
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Mike Kienenberger <mk...@gmail.com>.
I'm not an expert, but the documentation I've read says that
disabled=true doesn't resubmit the form value and that read-only=true
does resubmit the form value. My guess is that the error message
above should be changed to remove the read-only caveat.
On 3/15/07, Jeff Bischoff <jb...@klkurz.com> wrote:
> 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 <jb...@klkurz.com> 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 <ol...@siemens.com> 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
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >>
> >
> >
> >
>
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Jeff Bischoff <jb...@klkurz.com>.
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 <jb...@klkurz.com> 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 <ol...@siemens.com> 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
>> >>
>> >
>> >
>> >
>>
>>
>>
>>
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Mike Kienenberger <mk...@gmail.com>.
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 <jb...@klkurz.com> 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 <ol...@siemens.com> 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
> >>
> >
> >
> >
>
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Jeff Bischoff <jb...@klkurz.com>.
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 <ol...@siemens.com> 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
>>
>
>
>
Re: MyFaces 1.1.5 warning message on console
Posted by Mike Kienenberger <mk...@gmail.com>.
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 <ol...@siemens.com> 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
>
Re: MyFaces 1.1.5 warning message on console
Posted by Josué Alcalde González <jo...@gmail.com>.
El jue, 15-03-2007 a las 11:18 +0100, Pfau, Oliver escribió:
> 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
I had the same problem in a very complex form.
My solution: reenable all the inputs in the client side before submit.