I've also had it happen if the page changes and the facelets component tree (or jsp page) is still cached somewhere. Same idea -- the expected submitted page elements do not match the actual submitted page elements.
On 6/5/07, Shane Petroff <[EMAIL PROTECTED]> wrote:
I am having some strange navigation problems (once again...) and the only clue I have is the warning below. HtmlRendererUtils - 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. In Googling the error message, it seems that the problem should be related to using Javascript to disable a control which my-faces expects to get a value from. The warning goes on to name the component in question, but there isn't any Javascript which touches these text areas, in fact there isn't any Javascript which disables anything. The components which are (in theory) causing the warning are certainly not disabled visually and for the most part they all contain text. They also happen to be created in Java code, so there is no jsp to post here. Can anyone give me a more detailed interpretation of what the warning means and when it arises? -- Shane
