[jbosstools-issues] [JBoss JIRA] (JBIDE-24226) Fix Jolokia Mbean listing in JMX navigator to have it matching the RMI based implementation
[
https://issues.jboss.org/browse/JBIDE-24226?page=com.atlassian.jira.plugi...
]
Aurélien Pupier commented on JBIDE-24226:
-----------------------------------------
it seems that the elements in the JMX Navigator are grouped by the property in the order
they are provided. the order is not the same with Jolokia at this place
org.jboss.tools.jmx.core.tree.NodeBuilder.addToTree(Node, ObjectName,
MBeanServerConnection) for instance:
for RMI:
{noformat}
type=MemoryManager,name=CodeCacheManager,
type=MemoryManager,name=CodeCacheManager,
type=MemoryManager,name=CodeCacheManager,
{noformat}
for Jolokia:
{noformat}
name=CodeCacheManager,type=MemoryManager,
name=CodeCacheManager,type=MemoryManager,
name=CodeCacheManager,type=MemoryManager,
{noformat}
Fix Jolokia Mbean listing in JMX navigator to have it matching the
RMI based implementation
-------------------------------------------------------------------------------------------
Key: JBIDE-24226
URL: https://issues.jboss.org/browse/JBIDE-24226
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.4.4.AM1
Reporter: Aurélien Pupier
Attachments: image-2017-04-05-10-05-18-535.png
If I understand well, for RMI, the top level Mbean are grouped by types. For Jolokia
there is no grouping.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)