After you commit the patch, could you send out a message. I need to grab the patch. Thanks, Dave
--- On Mon, 3/22/10, Jakob Korherr <[email protected]> wrote: From: Jakob Korherr <[email protected]> Subject: Re: WARN [HtmlRendererUtils]There should always be a submitted value To: "MyFaces Discussion" <[email protected]> Date: Monday, March 22, 2010, 2:12 PM Hi, Unfortunately I did not find a passage in the spec or in the spec javadoc that says that every EditableValueHolder has to have a submitted value. So I don't exactly know why this was added. I saw that this was added pretty early to MyFaces and so it is possible that it was just not thought of AJAX here, but frankly I don't know exactly. I think we should get rid of this warning, because it does not have any impact if the submitted value is null, because if this is the case, the value just won't be processed any further. In addition and as a reason of AJAX it is quite common to not submit all fields of a form in every request. I'll create a JIRA issue for this one and provide a patch. If no objections, I'll commit it in the next days! Thanks for the input! Regards, Jakob 2010/3/21 Dave <[email protected]> > It is normal to submit one value of a form for ajax. how to keep the > following warning from emitting. Thanks! > > WARN [HtmlRendererUtils] There should always be a submitted value for an > input if it is rendered, its form is submitted, and it was not originally > rendered disabled or read-only. You cannot submit a form after disabling an > input element via javascript. Consider setting read-only to true instead or > resetting the disabled value back to false prior to form submission. > Component : {Component-Path : ....} > > >
