You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Daryl Olander (JIRA)" <be...@incubator.apache.org> on 2005/02/12 19:35:12 UTC

[jira] Resolved: (BEEHIVE-226) expandOnServer doesn't apply expand/contract the nodes on the Client

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

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

This was actually a bigger problem than first described.  The problem was that the initialization code did not run so not only did the expand/collapse no get reflected (coreWeb/richtree/expandOnServer.jsp), the expand/collapse link was not set correctly.  The result was that on expansion, the node actually caused the page to post.

A good example of this working properly is coreWeb/tree/expand/Controller.jpf

> expandOnServer doesn't apply expand/contract the nodes on the Client
> --------------------------------------------------------------------
>
>          Key: BEEHIVE-226
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-226
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Alejandro Ramirez
>      Fix For: V1Beta

>
> When an expandOnServer node is expanded, we recursively render the children.  If one of the children is collapsed, we are currently not collapsing that node on the client.  The result is that the client and the server state mismatch.

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