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

Posted to dev@beehive.apache.org by "Julie Zhuo (JIRA)" <de...@beehive.apache.org> on 2005/08/25 00:46:08 UTC

[jira] Closed: (BEEHIVE-846) add a "PageFlow registered" event to the EventReporter

     [ http://issues.apache.org/jira/browse/BEEHIVE-846?page=all ]
     
Julie Zhuo closed BEEHIVE-846:
------------------------------


Verified at rev239468. There is a EnventReporter bvt test and it has been passing.

> add a "PageFlow registered" event to the EventReporter
> ------------------------------------------------------
>
>          Key: BEEHIVE-846
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-846
>      Project: Beehive
>         Type: Improvement
>   Components: NetUI
>     Versions: TBD
>  Environment: all
>     Reporter: David Read
>     Assignee: Julie Zhuo
>     Priority: Minor
>      Fix For: V1

>
> Currently the set of PageFlows in a webapp aren't know until they are invoked.  If you want to do things like integrate monitoring via JMX, you need a lazy instantiation model.  If there were an event generated when a PageFlow was registered, you'd have a hook to know that something "new" was now part of the webapp.  

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