You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by be...@incubator.apache.org on 2004/10/07 05:18:52 UTC
[jira] Created: (BEEHIVE-8) JPF runtime should use standard control client initializer
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/BEEHIVE-8
Here is an overview of the issue:
---------------------------------------------------------------------
Key: BEEHIVE-8
Summary: JPF runtime should use standard control client initializer
Type: Improvement
Status: Open
Priority: Major
Project: Beehive
Components:
NetUI
Fix Fors:
TBD
Versions:
TBD
Assignee: Rich Feit
Reporter: Kenneth Tam
Created: Wed, 6 Oct 2004 8:18 PM
Updated: Wed, 6 Oct 2004 8:18 PM
Description:
Pageflows currently support declarative controls via their own initialization code (in JavaControlUtils.java). They should use the standard control client initializer mechanism to do this (and get free event handler support at the same time). See http://nagoya.apache.org/jira/browse/BEEHIVE-7 for more details on how this should work.
---------------------------------------------------------------------
JIRA INFORMATION:
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-8) JPF runtime should use standard control client initializer
Posted by "Julie Zhuo (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-8?page=all ]
Julie Zhuo closed BEEHIVE-8:
----------------------------
The JavaControlUtils class is now using
Controls.initializeClient(null, controlClient, beanContext);
Verified at rev170936.
> JPF runtime should use standard control client initializer
> ----------------------------------------------------------
>
> Key: BEEHIVE-8
> URL: http://issues.apache.org/jira/browse/BEEHIVE-8
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Alpha
> Reporter: Kenneth Tam
> Assignee: Julie Zhuo
> Fix For: V1Beta
>
> Pageflows currently support declarative controls via their own initialization code (in JavaControlUtils.java). They should use the standard control client initializer mechanism to do this (and get free event handler support at the same time). See http://nagoya.apache.org/jira/browse/BEEHIVE-7 for more details on how this should work.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (BEEHIVE-8) JPF runtime should use standard control client initializer
Posted by be...@incubator.apache.org.
The following comment has been added to this issue:
Author: Rich Feit
Created: Wed, 6 Oct 2004 10:57 PM
Body:
Some of the control-side code (e.g., ControlBean.isControlClient) will need to change to avoid performance hits due to calls on reflection APIs. I can address that as part of this fix.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/BEEHIVE-8?page=comments#action_53796
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/BEEHIVE-8
Here is an overview of the issue:
---------------------------------------------------------------------
Key: BEEHIVE-8
Summary: JPF runtime should use standard control client initializer
Type: Improvement
Status: Open
Priority: Major
Project: Beehive
Components:
NetUI
Fix Fors:
TBD
Versions:
TBD
Assignee: Rich Feit
Reporter: Kenneth Tam
Created: Wed, 6 Oct 2004 8:18 PM
Updated: Wed, 6 Oct 2004 10:57 PM
Description:
Pageflows currently support declarative controls via their own initialization code (in JavaControlUtils.java). They should use the standard control client initializer mechanism to do this (and get free event handler support at the same time). See http://nagoya.apache.org/jira/browse/BEEHIVE-7 for more details on how this should work.
---------------------------------------------------------------------
JIRA INFORMATION:
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-8) JPF runtime should use standard control client initializer
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-8?page=history ]
Rich Feit resolved BEEHIVE-8:
-----------------------------
Assign To: Kenneth Tam (was: Rich Feit)
Resolution: Fixed
Kyle actually made this change a while ago...
> JPF runtime should use standard control client initializer
> ----------------------------------------------------------
>
> Key: BEEHIVE-8
> URL: http://issues.apache.org/jira/browse/BEEHIVE-8
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Alpha
> Reporter: Kenneth Tam
> Assignee: Kenneth Tam
> Fix For: V1Beta
>
> Pageflows currently support declarative controls via their own initialization code (in JavaControlUtils.java). They should use the standard control client initializer mechanism to do this (and get free event handler support at the same time). See http://nagoya.apache.org/jira/browse/BEEHIVE-7 for more details on how this should work.
--
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-8) JPF runtime should use standard control client initializer
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-8?page=all ]
Alejandro Ramirez reassigned BEEHIVE-8:
---------------------------------------
Assign To: Julie Zhuo (was: Kenneth Tam)
Please verify
> JPF runtime should use standard control client initializer
> ----------------------------------------------------------
>
> Key: BEEHIVE-8
> URL: http://issues.apache.org/jira/browse/BEEHIVE-8
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Alpha
> Reporter: Kenneth Tam
> Assignee: Julie Zhuo
> Fix For: V1Beta
>
> Pageflows currently support declarative controls via their own initialization code (in JavaControlUtils.java). They should use the standard control client initializer mechanism to do this (and get free event handler support at the same time). See http://nagoya.apache.org/jira/browse/BEEHIVE-7 for more details on how this should work.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-8) JPF runtime should use standard control client initializer
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-8?page=history ]
Rich Feit updated BEEHIVE-8:
----------------------------
Fix Version: V1Beta
(was: V1Alpha)
> JPF runtime should use standard control client initializer
> ----------------------------------------------------------
>
> Key: BEEHIVE-8
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-8
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Alpha
> Reporter: Kenneth Tam
> Assignee: Rich Feit
> Fix For: V1Beta
>
> Pageflows currently support declarative controls via their own initialization code (in JavaControlUtils.java). They should use the standard control client initializer mechanism to do this (and get free event handler support at the same time). See http://nagoya.apache.org/jira/browse/BEEHIVE-7 for more details on how this should work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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