glassfish
  1. glassfish
  2. GLASSFISH-17831

Second submit (commandButton) fails in nested composites

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Duplicate
    • Affects Version/s: 3.1.1
    • Fix Version/s: None
    • Component/s: jsf
    • Labels:
      None

      Description

      I have developed a set of components using composites. I have layout components (<div>) and a button composite (h:commandButton). When hitting the button the action method is executed. The action does not lead to a different page. When hitting the button again the action method is not executed.

      I have found this problem in JSF 2.1.3-FCS with GlassFish 3.1.1.

        Issue Links

          Activity

          Hide
          Manfred Riem added a comment -

          See the associated JAVASERVERFACES issue for resolution.

          Show
          Manfred Riem added a comment - See the associated JAVASERVERFACES issue for resolution.
          Hide
          rogerk added a comment -

          Target subsequent release - too risky for this release and there is a workaround.

          Show
          rogerk added a comment - Target subsequent release - too risky for this release and there is a workaround.
          Hide
          rogerk added a comment -

          I've discovered that the action event is never queued for the second button click.
          When the page is first rendered, the id of the button is:
          j_idt7:j_idt9:j_idt10:button
          After the first button click, the id of the button is:
          j_idt10:button
          So the ButtonRenderer.decode method is looking for j_idt7:j_idt9:j_idt10:button as a request parameter
          (on postback), but it is j_idt10:button - so the action event is never queued.

          Show
          rogerk added a comment - I've discovered that the action event is never queued for the second button click. When the page is first rendered, the id of the button is: j_idt7:j_idt9:j_idt10:button After the first button click, the id of the button is: j_idt10:button So the ButtonRenderer.decode method is looking for j_idt7:j_idt9:j_idt10:button as a request parameter (on postback), but it is j_idt10:button - so the action event is never queued.
          Hide
          keesbroenink added a comment -

          I have button.css as an empty file. But you can put some style in it. It is not meants as markup. That is button.xhtml.

          Show
          keesbroenink added a comment - I have button.css as an empty file. But you can put some style in it. It is not meants as markup. That is button.xhtml.
          Hide
          rogerk added a comment -

          Can you tell me why button.css is not a stylesheet? You have this as composite component markup which makes no sense.

          Show
          rogerk added a comment - Can you tell me why button.css is not a stylesheet? You have this as composite component markup which makes no sense.

            People

            • Assignee:
              rogerk
              Reporter:
              keesbroenink
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: