I'd prefer to leave it in as it gives the _deployer_ choice as to whether to expose the innards of time shceduling to JMX view or to hide them completely.
I planned to offer second entry point to all the cornerstone blocks....
Also, it did work in phoenix without the 'implements' change.
Regards,
- Paul
Modified: src/java/org/apache/avalon/cornerstone/blocks/scheduler
DefaultTimeScheduler.java
Log:
Implements MonitorableSchedulerMBean.
Do we need MonitorableScheduler?
Revision Changes Path
1.26 +1 -1 jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/blocks/scheduler/DefaultTimeScheduler.java
Index: DefaultTimeScheduler.java
===================================================================
RCS file: /home/cvs/jakarta-avalon-cornerstone/src/java/org/apache/avalon/cornerstone/blocks/scheduler/DefaultTimeScheduler.java,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- DefaultTimeScheduler.java 18 Oct 2002 10:14:01 -0000 1.25
+++ DefaultTimeScheduler.java 24 Dec 2002 04:13:57 -0000 1.26
@@ -34,7 +34,7 @@
*/
public class DefaultTimeScheduler
extends AbstractLogEnabled
- implements TimeScheduler, Serviceable, Startable, Disposable, Runnable
+ implements TimeScheduler, Serviceable, Startable, Disposable, Runnable, MonitorableTimeSchedulerMBean
{
private final Hashtable m_entries = new Hashtable();
private final PriorityQueue m_priorityQueue =
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
