Tapestry
  1. Tapestry
  2. TAPESTRY-1197

Unable to re render dojo widgets when responsebuilder updates a component in the form

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.1.1
    • Fix Version/s: 4.1.1
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Firefox 2.0, Windows XP, Tomcat 4.1

      Description

      Unable to re render dojo widgets when responsebuilder updates a component in the form.. I attached the full project of the example... how the bug occur

        Activity

        Hide
        Keith added a comment -

        Attached the file that will clearly shows the bug

        Show
        Keith added a comment - Attached the file that will clearly shows the bug
        Hide
        Andreas Andreou added a comment -

        Problem seems to be with the dropdown date-time pickers...

        The ajax response contains tapestry.widget.synchronizeWidgetState for them, but
        since updateComponents (or in this case cycle.getResponseBuilder().updateComponent )
        doesn't contain them, their html isn't included in the response

        So you get errors like "createWidget() Node not found with specified id of 'dob'."

        Show
        Andreas Andreou added a comment - Problem seems to be with the dropdown date-time pickers... The ajax response contains tapestry.widget.synchronizeWidgetState for them, but since updateComponents (or in this case cycle.getResponseBuilder().updateComponent ) doesn't contain them, their html isn't included in the response So you get errors like "createWidget() Node not found with specified id of 'dob'."
        Hide
        Jesse Kuhnert added a comment -

        "Oops" . Not sure how this got overlooked but it's almost fixed now. Just need to make sure all the correct logic is in place for all widgets before committing/releasing.

        Show
        Jesse Kuhnert added a comment - "Oops" . Not sure how this got overlooked but it's almost fixed now. Just need to make sure all the correct logic is in place for all widgets before committing/releasing.
        Hide
        Jesse Kuhnert added a comment -

        Form based widget components weren't using the same logic as normal widget components for figuring out whether or not they should execute or destroy their client side widget equivalents. Added this logic in.

        Show
        Jesse Kuhnert added a comment - Form based widget components weren't using the same logic as normal widget components for figuring out whether or not they should execute or destroy their client side widget equivalents. Added this logic in.

          People

          • Assignee:
            Unassigned
            Reporter:
            Keith
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development