[ http://issues.apache.org/jira/browse/TAPESTRY-731?page=comments#action_12356812 ]
Jesse Kuhnert commented on TAPESTRY-731: ---------------------------------------- Hmm..Yeah I suppose jmx-ing things is always a little more than a pain in the ass. I've been wanting to create a special exception page for tacos that would be displayed inline (or somewhere..maybe floating pane.,..dunno) and be a little more interactive. (Hiding/showing things/etc..) If you get somewhere with some of these notifies I'd be happy to help with the ui portion. (free of js libraries of course) > Application monitor page > ------------------------ > > 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 > > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
