JMX's technical needs can be said to separate management functions from functional interfaces. For example, a cache interface interface icache {Object GET (Object Key); Void Put (Object Key, Object Value);} But a specific implementation class may have many parameters to adjust, such as the maximum size of the cache. These configurable parameters are generally related to the specific implementation, ie, related to the example, without directly involving the functionality to be implemented. For example, the implementation class can have a setmaxSize () and getMaxSize () method. If these configuration methods are defined in the function interface, the bloated and unnecessary and unnecessary and unnecessary methods of the function interface will cause dependence. If you only call the implementation class, you can only use the reflection, but the Java Class is limited as the amount of information loaded by the metadata, and a specification is required to supplement the information. JMX is such a specification.
