Wicket
  1. Wicket
  2. WICKET-5300

ComponentRenderingRequestHandler does not clear renderedComponents (PrototypeApplication)

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.9.1, 7.0.0-M1
    • Fix Version/s: 6.10.0, 7.0.0-M1
    • Component/s: wicket
    • Labels:
      None

      Description

      A second click on the prototype link fails:

      The component [Component id = counter] was rendered already. You can render it only once during a render phase. Class relative path: org.apache.wicket.markup.html.basic.Label:counter
      MarkupStream: [unknown]
      at org.apache.wicket.Page.componentRendered(Page.java:210)
      at org.apache.wicket.Component.rendered(Component.java:2610)
      at org.apache.wicket.Component.internalRender(Component.java:2383)
      at org.apache.wicket.Component.render(Component.java:2307)
      at org.apache.wicket.core.request.handler.ComponentRenderingRequestHandler.respond(ComponentRenderingRequestHandler.java:70)

      ComponentUseCheck has to be enabled (e.g. development config). It seems ComponentRenderingRequestHandler does not clear the collection of renderedComponents in the page.

        Activity

        Hide
        Sven Meier added a comment -

        ComponentRenderingRequestHandler now calls #startComponentRender() / #endComponentRender() as XmlAjaxResponse does.

        Show
        Sven Meier added a comment - ComponentRenderingRequestHandler now calls #startComponentRender() / #endComponentRender() as XmlAjaxResponse does.

          People

          • Assignee:
            Sven Meier
            Reporter:
            Sven Meier
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development