avalon-phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Huw Roberts <...@mmlive.com>
Subject Patch to Create a 'Local' Management Context (= SystemManager)
Date Sat, 13 Jul 2002 06:40:58 GMT

This patch implements the concept of a 'local' management context that
objects are registered with.  I think its better than spreading the JMX
naming scheme in different parts of the code.  The big change is the
addition of the getSubContext() method to SystemManager.  The contexts are
organized into hierarchy like this:

	Component List
		Component 1
		Component 2
	Application List
		Application 1
			Block List
				Block 1
				Block 2
		Application 2
			Block List
				Block 1
				Block 2

JMX naming is then derived by 'walking' up to the top level context, which
is the 'real' SystemManager.

I've tested it with NoOpSystemManager and MX4JSystemManager and haven't
encountered any problems.

An itemized list of changes:

- Added method getSubContext( String parent, String type ) to create a

- Modified naming code slightly to be compatible with new scheme

- Added inner class SubContext, which implements SystemManager and acts as
the local context

- Changed so applications register with the 'application' list context

- Changed so blocks register with the application's block list context

- Changed so components are registered with the component list context

The diff was made with the cvs diff -u >> patch diff from the
jakarta-avalon-phoenix/src/java directory.  I hope this is right - or is it
better to diff each class seperately?

This is part of the Management Proposal idea i sent out last week.  I think
these are the only interfaces changes that are required and all the rest of
the work would be isolated behind SystemManager interface.

Please let me know what you think.

- Huw

View raw message