Difference between MBean and MXBean

Question 1

MXBeans are just a special kind of MBeans. The main difference is that MXBean restrict the data types, so that they are "more compatible" with potential clients.

As example: a MBean can expose attributes of a data type Foo. Now the client also needs to have this type Foo to make sense of the attribute.

The MXBean tries to restrict the data types to those "already available" - java.lang.* etc.

See this tutorial

Question 2

MBeans :

Can be any of java objects, in which we can store/retrive Serializable/Externalizable objects using methods.

Based on the design pattern used in objects, we can differentiate either Standard(static) or Dynamic. Recommended to maintain Interface class name suffixed with MBean.

MXBeans :

reference only a pre-defined set of types. Recommended to maintain Interface class name suffixed with MXBean. Implements interface of Dynamic or customized JavaBean.

Using MXBean, We can facilitate any client to use MBeans. Additional details required to use MXBean.

Refer Here

Question 3

An MXBean is an MBean which is constrained to open types, basically primitive types, Strings and compositions thereof. Due to these constraints, an MXBean can get used without class loading and that makes them interoperable even with non-Java clients. You can find the specification here: http://docs.oracle.com/javase/7/docs/api/javax/management/package-summary.html#package_description

Question 4

MBeans can be any of java objects, in which we can store/retrive Serializable/Externalizable objects using methods. Based on the design pattern used in objects, we can differentiate either Standard(static) or Dynamic. Recommended to maintain Interface class name suffixed with MBean

MXBeans reference only a pre-defined set of types. Recommended to maintain Interface class name suffixed with MXBean. Implements interface of Dynamic or cusotmized JavaBean. Using MXBean, We can facilitate any client to use MBeans.

Refer MBean vs MXBean