[
http://jira.jboss.com/jira/browse/JBJMX-102?page=comments#action_12345164 ]
Peter Becker commented on JBJMX-102:
------------------------------------
Dimitris,
this was not an issue of JSR-77 compliance (JSR-77 is too unspecific to say anything about
that), but more about usability of the MEJB. As it is implemented now, it is quite
useless, because it hides about 50 % of the information that is available e.g. in the
JBoss console.
Peter
JSR-77 / MEJB support does not work for many MBeans
---------------------------------------------------
Key: JBJMX-102
URL:
http://jira.jboss.com/jira/browse/JBJMX-102
Project: JBoss JMX
Issue Type: Bug
Affects Versions: JBossAS-4.0.0
Environment: Obeyed on Windows XP with newest JBoss 4.04 release
Reporter: Peter Becker
My administration client cannot access many (about 50 %) of the MBeans in the MEJB
because they use non-serializable classes. I receive lots of exceptions like
java.io.NotSerializableException: org.jboss.mx.loading.UnifiedLoaderRepository3
java.io.NotSerializableException: org.jboss.tm.TxManager
java.io.NotSerializableException: org.jboss.tm.XidFactory
java.io.NotSerializableException: java.lang.reflect.Method
java.io.NotSerializableException: java.util.Hashtable$ValueCollection
The exceptions occur when I try to read the MBean attributes. The JBoss classes used by
MBeans need to be Serializable, and they must not use non.-Serializable classes to make
the JSR-77 feature work 100%.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira