RE: Form/Input Handling Problem

[Burke, Rodney]

I figured out what was going on and it was not because of the extra
commandButton added in the middle, as I previously thought.

Solution:

Basically my page looks like this

form
  commandButton (x3)

  panelStack

     panelGroup id=A
          panelTabbedPane id=tabA1
               panelTab
                input components ...
               /panelTab
        /panelTabbedPane
     /panelGroup

     panelGroup id=B  
          panelTabbedPane id=tabB1
               panelTab
                input components ...
               /panelTab
        /panelTabbedPane
     /panelGroup
   /panelStack

   commandButton (x3)
 /form

But the panel stack resulted in only half the input components being
submitted in the form. That is, either group A or B would be submitted
based on panel stack selection, which resulted in missing inputs for the
other group (since all inputs are in same form), hence the error
message.

The fix was simply to reorganize the page such that each panel group was
a self contained form, as follows:

  panelStack
     panelGroup id=A
        form
           commandButton (x3)
               panelTabbedPane id=tabA1
                  panelTab
                   input components ...
                  /panelTab
            /panelTabbedPane
           commandButton (x3)
        /form
     /panelGroup

     panelGroup id=B  
        form
           commandButton (x3)
               panelTabbedPane id=tabB1
                  panelTab
                   input components ...
                  /panelTab
            /panelTabbedPane
           commandButton (x3)
        /form
    /panelGroup
 /panelStack

Thanks,
Rodney

-----Original Message-----
From: Andrew robinson [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 06, 2005 4:20 PM
To: MyFaces Discussion
Subject: Re: Form/Input Handling Problem

Hmmm... sorry, then not sure why you would be getting that message then.

On 11/6/05, Burke, Rodney <[EMAIL PROTECTED]> wrote:
> Andrew,
>
> To my knowledge, I am not disabling control on client side.
> Is there some specific configuration parameter that I should check?
>
> The message seems to indicate that input values are not being posted
> when the button is pressed, strange.
>
> Thanks,
> Rodney
>
> -----Original Message-----
> From: Andrew robinson [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 04, 2005 4:14 PM
> To: MyFaces Discussion
> Subject: Re: Form/Input Handling Problem
>
> I have received this warning when I disable the control using
> javascript on the client-side & therefore the browser will not post
> the value back (I believe). Are you disabling controls on the client
> side?
>
> On 11/4/05, Burke, Rodney <[EMAIL PROTECTED]> wrote:
> > Does anyone know why I'm getting the following form/input error?
> >
> > Here's my scenario:
> >
> > I have a jsp page which uses an <h:form> and there are three
> > <h:commandButton>s at the very top and the very bottom of the form.
> > The form woks fine until I add another <h:commandButton> in the
middle
> > of the form. At which point the following message is displayed
> multiple
> > times when I press any of the submit buttons.
> >
> > "WARN  [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."
> >
> > My commandButtons are structured like this:
> >
> > <h:commandButton id="force_audio_blend"
> >
> >             action="#{controlGEM.forceAudioBlend}"
> > value="#{resource_msg['label_control_force_audio_blend']}"  />
> >
> >
> > Thank You,
> > Rodney
> >
> >
>