[ mx4j-Bugs-838614 ] MBeanAttributeInfo validation of methods too restrictive

Bugs item #838614, was opened at 2003-11-09 00:39
Message generated for change (Comment added) made by biorn_steedom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=838614&group_id=47745

>Category: JMX implementation
>Group: Release 2.0.1
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Ward K Harold (wkharold)
>Assigned to: Simone Bordet (biorn_steedom)
Summary: MBeanAttributeInfo validation of methods too restrictive

Initial Comment:
MBeanAttributeInfo requires that getter/setter parameters 
passed to its constructors follow the StandardMBean naming 
conventions, i.e., getters start with "get" and setters start 
with "set". This unnecessarily restricts a DynamicMBean's 
ability to "wrap" a POJO.

----------------------------------------------------------------------

>Comment By: Simone Bordet (biorn_steedom)
Date: 2004-09-07 14:54

Message:
Logged In: YES 
user_id=128193

Unfortunately, the JMX specification does not allow to
record further information such as alternative names for
getters and setters.
Even if MX4J does this, serializing a MBeanAttributeInfo
will loose this information, resulting in the impossibility
to use the alternative names.
If you have further insights, please reopen this bug.
I am closing it as "Won't Fix"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=838614&group_id=47745


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click