[jira] Resolved: (BEEHIVE-192) Tree names are not qualified into ScriptContainers

["Daryl Olander (JIRA)" <be...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/BEEHIVE-192?page=history ]
     
Daryl Olander resolved BEEHIVE-192:
-----------------------------------

     Assign To: Alejandro Ramirez  (was: Daryl Olander)
    Resolution: Fixed

This has been fixed. I have added a BVT to demonstrate the problem.  The issue is that having two trees, both with tagId="tree", they must appear in a ScriptContainer that creates a unique name.

See coreWeb/richTree/treeSC4 - which does this and contains JavaScript verifying that the tree and treeElements can be accessed.

> Tree names are not qualified into ScriptContainers
> --------------------------------------------------
>
>          Key: BEEHIVE-192
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-192
>      Project: Beehive
>         Type: Bug
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Alejandro Ramirez

>
> When you put two trees into the same page, if they have the same tagId value, the anchors generated for selection do not get fully qualified and therefore, the one tree will affect the other tree.
> Repo:
> Create two trees with the same name.
> Place each into a <scriptContainer> with generateIdScope="true"
> select a not in one tree.
> You'll notice that the node will also be selected in the other tree.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira