[jira] Resolved: (BEEHIVE-221) A tree in a scriptContainer below another tree in a scriptContainer doesn't runAtClient correectly

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

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

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

This was fixed a couple of days ago.  I reworked the initialization code on a Tree such that it can run twice if necessary.  The JavaScript will not initialize all trees that haven't yet been initialized each time it runs.  

In addition, by pushing the JavaScript up the ScriptContainer hierarchy, it will only run twice when you have two script containers without a common parent.

coreWeb/RichTree/treeSC2.jsp and coreWeb/RichTree/treeSC3.jsp demonstrate both conditions.

> A tree in a scriptContainer below another tree in a scriptContainer doesn't runAtClient correectly
> --------------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-221
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-221
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Alejandro Ramirez
>      Fix For: V1Beta

>
> If you have two scriptContainers each with a tree inside it, both tree having runAtClient set to true.  Expansion of the second Tree doesn't work.  The reason is that the tree init() javascript is run before the second tree is added to the HTML DOM.  
> The solution will be to actually allow running the tree init code more than once.

-- 
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