Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
Description
The "Replace ServiceMBean and ServiceMBeanSupport " rule states:
JMX / MBeans is still fully supported as it is in the JDK specification. If your MBeans were extending the old JBoss EAP MBean support classes such as org.jboss.system.ServiceMBean and org.jboss.system.ServiceMBeanSupport, these do not exist in JBoss EAP 6+. These classes were hooked into the kernel in previous versions of JBoss EAP where everything was basically turned into an MBean.
and links to: https://access.redhat.com/solutions/121823
But if you go to that access article it says:
JMX / MBeans are still fully supported as they is in the JDK specification, and the proprietary JBoss MBean support classes org.jboss.system.ServiceMBean and org.jboss.system.ServiceMBeanSupport are supported as well except for these two classes were briefly removed in EAP 6.0 and restored in EAP 6.1 and higher (including EAP 7.x). Since we do not recommend using EAP 6.0 anymore due to it being many patches out of date this should not normally affect anyone.
Which if I am following this correctly means that the entire rule is mute. No change is needed, or at the very least it should be moved from "Mandatory" to "Optional"