On Jul 13, 2004, at 6:01 PM, Gianny Damour wrote:
On 14/07/2004 9:17 AM, Gianny Damour wrote:
I have just updated the way GBean attribute names are derived:
When GBeans are proxied via RawGBeanInvokers, attribute names may start with an upper-case letter. For instance, if a GBean has a method "getFoo", then the implementation tries to find an attribute having the name "Foo". This was the behavior before my updates and I have restored it. Now, if such an attribute is not defined, then the implementation tries to find an attribute having the name "foo".
When GBeans are proxied via JMXGBeanInvokers, attribute names are derived based on the "exact" name embedded in the method name. For instance, if a GBean has a method "getfoo", then the implementation tries to find an attribute having the name "foo". This was the behavior before my updates and I have restored it.
Uh, I think you lost me. I suggest we first try an exact match using JMX standard MBean rules (getFoo looks for a method Foo) and if that fails we do a case insensitive match. What ever we do, it must be consistent between the GBeanInvokers, since the programmer has not input into the invoker type the container chooses.
-dain
