Return-Path: Delivered-To: apmail-beehive-dev-archive@www.apache.org Received: (qmail 83809 invoked from network); 6 Dec 2006 20:14:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Dec 2006 20:14:14 -0000 Received: (qmail 49132 invoked by uid 500); 6 Dec 2006 20:14:22 -0000 Delivered-To: apmail-beehive-dev-archive@beehive.apache.org Received: (qmail 49121 invoked by uid 500); 6 Dec 2006 20:14:22 -0000 Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Beehive Developers" Delivered-To: mailing list dev@beehive.apache.org Delivered-To: moderator for dev@beehive.apache.org Received: (qmail 57166 invoked by uid 99); 6 Dec 2006 18:35:50 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Message-ID: <14656086.1165430121121.JavaMail.jira@brutus> Date: Wed, 6 Dec 2006 10:35:21 -0800 (PST) From: "Carlin Rogers (JIRA)" To: dev@beehive.apache.org Subject: [jira] Created: (BEEHIVE-1162) Resetting the value of TreeElement attribute using TreeHtmlAttributeInfo is not handled correctly. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Resetting the value of TreeElement attribute using TreeHtmlAttributeInfo is not handled correctly. -------------------------------------------------------------------------------------------------- Key: BEEHIVE-1162 URL: http://issues.apache.org/jira/browse/BEEHIVE-1162 Project: Beehive Issue Type: Bug Components: NetUI Affects Versions: 1.0.1, 1.0.2, V.Next Reporter: Carlin Rogers Assigned To: Carlin Rogers Priority: Minor Fix For: V.Next When resetting the value of TreeElement attribute using TreeHtmlAttributeInfo, the AttributeRenderer still maintains the original attribute in a list and then it is applied to the markup of subsequent tree items. This is an issue between the TreeElement set of attributes and the AttributeRenderer. For example, if an attribute is applied to a tree item when the item is selected (via a selectNode() action) and reset to a different value when a different node is selected, the nodes that follow will have the old attribute applied to them. The TreeElement stores the attributes in a List. So trying to reset the attribute value in another operation using TreeElement.addAttribute() just adds a second entry to the list. For example, if a "style" attribute has already been set on a tree item and then addAttribute() is used to to change the value of the attribute on the node, it just adds it to the list. Now there's two attributes in the TreeElement attribute list with the same name ("style"). This makes the AttributeRenderer behave incorrectly, thinking that the first attribute exists and needs to be saved for other elements. There is a workaround for this issue. A page flow developer could call the public TreeElement.getAttributeList() method and search through the list to see if it contains a TreeHtmlAttributeInfo with the same attribute name and then reset the value of that attribute. -- 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