I just tried the new JMX access code in 1.2RC1 against an MX4J JMX server using MBeanClientInterceptor and encountered the following problem:
MX4J exposes all MBean attributes for my application MBeans (I used CruiseControl as a test case) as starting with a capital letter; the method getProjects() results in an attribute called 'Projects', while the MBeanClientInterceptor uses BeanUtils.findPropertyForMethod and comes up with a lower-case attribute name so getProjects() results in 'projects'. Obviously this causes a conflict, since the attribute is not present in allowedAttributes with its lower-case name.
Is this something that should be configurable in the MBeanClientInterceptor? Does the JMX spec say anything about default casing of attribute names?