Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <15557016.1157461943461.JavaMail.jira@brutus>
Date: Tue, 5 Sep 2006 06:12:23 -0700 (PDT)
From: "Michael Lipp (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Created: (TOMAHAWK-657)
 HtmlDataScrollerRenderer.renderScroller causes duplicate Ids
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

HtmlDataScrollerRenderer.renderScroller causes duplicate Ids
------------------------------------------------------------

                 Key: TOMAHAWK-657
                 URL: http://issues.apache.org/jira/browse/TOMAHAWK-657
             Project: MyFaces Tomahawk
          Issue Type: Bug
          Components: Data Scroller
    Affects Versions: 1.1.5-SNAPSHOT
            Reporter: Michael Lipp
            Priority: Blocker


HtmlDataScrollerRenderer.renderScroller modifies the sroller component's structure by adding command links to it. This works only once. However, it is perfectly legal to invoke lifecycle.render several times *without* calling lifecycle.execute in between (that's what portals to for portlets that have not participated in the current action).

Because the component structure is reused rather than recreated in this case, the added command links from the previous render invocation are still there. Adding the command links again eventually leads to duplicate ids.

Workaround (and probably fix as well): clear list of children at the start of renderScroller.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira