tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Updated: (TAPESTRY-731) Extend RequestDisplay component (used on the Exception page) to also report the internal status of key Tapestry services
Date Tue, 08 Nov 2005 16:26:20 GMT
     [ http://issues.apache.org/jira/browse/TAPESTRY-731?page=all ]

Howard M. Lewis Ship updated TAPESTRY-731:
------------------------------------------

      Summary: Extend RequestDisplay component (used on the Exception page) to also report
the internal status of key Tapestry services  (was: Application monitor page)
    Assign To: Howard M. Lewis Ship

> Extend RequestDisplay component (used on the Exception page) to also report the internal
status of key Tapestry services
> ------------------------------------------------------------------------------------------------------------------------
>
>          Key: TAPESTRY-731
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-731
>      Project: Tapestry
>         Type: New Feature
>   Components: Framework
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship

>
> Had the following idea:
> What if there was an event interface that could be implemented by various services, whose
job was to "report status"; things like pool sizes, loaded pages, components, etc.  
> Lets call the event interface MonitorListener
> public void monitorStatusRequested(MonitorEvent event);
> Service implementations could register with the service (say tapestry.monitor.MonitorEventCoordinator).
> A page or component could uses the coordinator service to query the services of Tapestry
and format it into an HTML report.  Leverage the DescriptionReceiver interface (the event
could implement the interface, or provide a receiver object that does).  The "Engine" tab
of the Inspector could make use of this as well.
> This would be a great way to gain some introspection into the underlying status of Tapestry
without cluttering up all the service interfaces.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message