[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Case sensitivity in injecting a bean's property

[scott.stark@jboss.org]

I noted the issue between bean and mbean property case a while ago:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92469

so I'm surprised this is a regression. I don't know why it would have worked because even though the correct case ala java beans for a setPort/getPort is port (based on java.beans.Introspector behavior/javadoc), jmx 1.2, page 40 states:
anonymous wrote : 
  | Case Sensitivity
  | All attribute and operation names derived from these design patterns are casesensitive.
  | For example, this means that the methods getstate and setState
  | define two attributes, one called state that is read-only, and one called State that
  | is write-only.
  | 
  | While case sensitivity applies directly to component names of standard MBeans, it is
  | also applicable to all component names of all types of MBeans, standard or dynamic.
  | In general, all names of classes, attributes, operations, methods, and internal
  | elements defined in the JMX specification are case sensitive, whether they appear as
  | data or as functional code when they are manipulated by management operations.
  | 

so there are conflicting naming conventions. All I can see that we do is to allow a property matching strictness setting that can be specified when referencing a bean property that would relax the case sensitivity issue.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004963#4004963

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004963