[CONTROLLER-1966] Expose MXBean naming to downstreams Created: 23/Oct/20 Updated: 25/Feb/21 |
|
| Status: | Confirmed |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | CDS management API |
| Description |
|
With MXBeans format published, it is still an implementation detail where those MBeans crop up – leaving downstreams open-coding those paths. Expose proper naming constants and utility methods to create ObjectNames and locate existing MBeans. Since this functionality requires javax.management module for its operation, it should live separately in cds-mgmt-jmx. |