java - Why the emphasis on typed attributes/methods in MBean definition? -


from oracle's definition of mbeans:

mbeans managed beans, java objects represent resources managed. mbean has management interface consisting of:

  1. named , typed attributes can read , written.
  2. named , typed operations can invoked
  3. typed notifications can be> emitted mbean

why emphasis on typed in each of points above? java typed language , attributes/methods in java class have type attached them. finding definition confusing. or missing fundamental here? using typed mean different?

jmx has more restrictive typing characteristics because often, types providing form of "identity" or signature bean attribute or operation. in addition, jmx supports notion of open types complex type broken down primitive definitions can represented externally jvm (perhaps in jconsole specific class might not in classpath.)

don't hung on though... means mbean's attributes defined name, , type. no surprise there :)


Popular posts from this blog

Php - Delimiter must not be alphanumeric or backslash -

trac - Modifying workflow to add a status and split on ticket type -

Delphi interface implements -