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/10 04:53:12 UTC

[jira] Created: (BEEHIVE-269) Dynamically created trees don't work as runAtClient because they don't get named

Dynamically created trees don't work as runAtClient because they don't get named
--------------------------------------------------------------------------------

         Key: BEEHIVE-269
         URL: http://issues.apache.org/jira/browse/BEEHIVE-269
     Project: Beehive
        Type: Bug
  Components: NetUI  
    Versions: V1Beta    
    Reporter: Daryl Olander
    Priority: Critical
     Fix For: V1Beta


Dynamically created trees don't go through the path that names the tree, so they don't work when runAtClient is on.  We need to move the name path out of the tree creations and expression update condition and do this for all tree when they are runAtClient.

-- 
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-269) Dynamically created trees don't work as runAtClient because they don't get named

Posted by "Daryl Olander (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-269?page=history ]

Daryl Olander reassigned BEEHIVE-269:
-------------------------------------

    Assign To: Daryl Olander

> Dynamically created trees don't work as runAtClient because they don't get named
> --------------------------------------------------------------------------------
>
>          Key: BEEHIVE-269
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-269
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Daryl Olander
>     Priority: Critical
>      Fix For: V1Beta

>
> Dynamically created trees don't go through the path that names the tree, so they don't work when runAtClient is on.  We need to move the name path out of the tree creations and expression update condition and do this for all tree when they are runAtClient.

-- 
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-269) Dynamically created trees don't work as runAtClient because they don't get named

Posted by "Krista Baker (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-269?page=history ]
     
Krista Baker closed BEEHIVE-269:
--------------------------------


Verified that dynamically created trees can be runAtClient and now get named.

> Dynamically created trees don't work as runAtClient because they don't get named
> --------------------------------------------------------------------------------
>
>          Key: BEEHIVE-269
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-269
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Krista Baker
>     Priority: Critical
>      Fix For: V1Beta

>
> Dynamically created trees don't go through the path that names the tree, so they don't work when runAtClient is on.  We need to move the name path out of the tree creations and expression update condition and do this for all tree when they are runAtClient.

-- 
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-269) Dynamically created trees don't work as runAtClient because they don't get named

Posted by "Karen Stutesman (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-269?page=history ]

Karen Stutesman reassigned BEEHIVE-269:
---------------------------------------

    Assign To: Krista Baker  (was: Karen Stutesman)

> Dynamically created trees don't work as runAtClient because they don't get named
> --------------------------------------------------------------------------------
>
>          Key: BEEHIVE-269
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-269
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Krista Baker
>     Priority: Critical
>      Fix For: V1Beta

>
> Dynamically created trees don't go through the path that names the tree, so they don't work when runAtClient is on.  We need to move the name path out of the tree creations and expression update condition and do this for all tree when they are runAtClient.

-- 
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-269) Dynamically created trees don't work as runAtClient because they don't get named

Posted by "Daryl Olander (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-269?page=history ]
     
Daryl Olander resolved BEEHIVE-269:
-----------------------------------

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

The code path was moved out of the path that updates the data expression.  The result is that any tree, if it is runAtClient and hasn't been named then it will get named.

> Dynamically created trees don't work as runAtClient because they don't get named
> --------------------------------------------------------------------------------
>
>          Key: BEEHIVE-269
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-269
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Alejandro Ramirez
>     Priority: Critical
>      Fix For: V1Beta

>
> Dynamically created trees don't go through the path that names the tree, so they don't work when runAtClient is on.  We need to move the name path out of the tree creations and expression update condition and do this for all tree when they are runAtClient.

-- 
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-269) Dynamically created trees don't work as runAtClient because they don't get named

Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-269?page=history ]

Alejandro Ramirez reassigned BEEHIVE-269:
-----------------------------------------

    Assign To: Karen Stutesman  (was: Alejandro Ramirez)

Please verify

> Dynamically created trees don't work as runAtClient because they don't get named
> --------------------------------------------------------------------------------
>
>          Key: BEEHIVE-269
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-269
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Daryl Olander
>     Assignee: Karen Stutesman
>     Priority: Critical
>      Fix For: V1Beta

>
> Dynamically created trees don't go through the path that names the tree, so they don't work when runAtClient is on.  We need to move the name path out of the tree creations and expression update condition and do this for all tree when they are runAtClient.

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