[jira] Commented: (BEEHIVE-8) JPF runtime should use standard control client initializer

[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