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/01 19:29:18 UTC
[jira] Created: (BEEHIVE-226) expandOnServer doesn't apply expand/contract the nodes on the Client
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
Assigned to: Daryl Olander
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
[jira] Closed: (BEEHIVE-226) expandOnServer doesn't apply expand/contract the nodes on the Client
Posted by "Krista Baker (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-226?page=history ]
Krista Baker closed BEEHIVE-226:
--------------------------------
Verified, expandOnServer nodes now expand and contract correctly on the client
> 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: Krista Baker
> 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
[jira] Assigned: (BEEHIVE-226) expandOnServer doesn't apply expand/contract the nodes on the Client
Posted by "Karen Stutesman (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-226?page=history ]
Karen Stutesman reassigned BEEHIVE-226:
---------------------------------------
Assign To: Krista Baker (was: Karen Stutesman)
> 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: Krista Baker
> 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
[jira] Resolved: (BEEHIVE-226) expandOnServer doesn't apply expand/contract the nodes on the Client
Posted by "Daryl Olander (JIRA)" <be...@incubator.apache.org>.
[ 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
[jira] Assigned: (BEEHIVE-226) expandOnServer doesn't apply expand/contract the nodes on the Client
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-226?page=history ]
Alejandro Ramirez reassigned BEEHIVE-226:
-----------------------------------------
Assign To: Karen Stutesman (was: Alejandro Ramirez)
Please verify
> 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: Karen Stutesman
> 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