Should server MBeans interface be in common-api jar?

Type: New Feature
Status: Closed
Priority: 2 Major
Resolution: Fixed
Component/s: Management (JMX)
Labels:

Assignee: hhuynh
Reporter: hhuynh
Created: November 06, 2007
Votes: 0
Watchers: 0
Updated:
May 12, 2008
Resolved:
April 29, 2008

Description

I needed to build a watcher to automatically detect if there’s a split brain and health status of the cluster. However, the beans interface is in tc.jar file and I’d rather NOT depend on the whole jar. Should these beans interfaces moved to common-api jar instead?

Comments

Tim Eck 2007-11-06

I’m maybe go as far as saying the set of TC types involved in any “public” jmx beans should be in discreet jar (something like tc-jmx-api.jar)

Fiona OShea 2008-04-11

We think this is already done in trunk. Merging back to 2.6 when 2.6-stable1 is released.

Gary Keim 2008-04-29

There is now a terracotta-jmx-api jar but it doesn’t include every single thing that you need to deal with a cluster via JMX.