0

From Oracle's definition of MBeans:

MBeans are managed beans, Java objects that represent resources to be managed. An MBean has a management interface consisting of:

  1. Named and typed attributes that can be read and written.
  2. Named and typed operations that can be invoked
  3. Typed notifications that can be> emitted by the MBean

Why the emphasis on typed in each of the points above? Java is a strongly typed language and all attributes/methods in a Java class have a type attached to them. So I am finding this definition confusing. Or am I missing something fundamental here? Are they using typed to mean something completely different?

Geek
  • 26,489
  • 43
  • 149
  • 227

1 Answers1

0

JMX has more restrictive typing characteristics because often, the types themselves are providing a form of "identity" or signature to the bean attribute or operation. In addition, JMX supports the notion of Open Types where a complex type is broken down into its primitive definitions so it can be represented externally to the JVM (perhaps in JConsole where that specific class might not be in the classpath.)

Don't get hung up on it though... all it means is that an MBean's Attributes are defined by their name, and their type. No surprise there really :)

Nicholas
  • 15,916
  • 4
  • 42
  • 66