Build the GBeanInfo with the attribute name that case-insensitively.
--------------------------------------------------------------------

                 Key: GERONIMO-4719
                 URL: https://issues.apache.org/jira/browse/GERONIMO-4719
             Project: Geronimo
          Issue Type: Improvement
      Security Level: public (Regular issues)
    Affects Versions: 2.1.5, 2.2
            Reporter: Rex Wang
             Fix For: 2.1.5, 2.2


Currently, we build the GBeanInfo attribute according to the java code 
convention.However, when user set the attribute throught the plan, he have to 
pay attention to the case of the attribute name, such as:
        <gbean 
name="org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car,j2eeType=GBean,name=uniquename2"
 load="false" 
gbeanInfo="org.apache.geronimo.tomcat.connector.Http11ConnectorGBean">
            <attribute name="keepAliveTimeout">60000</attribute>
            <attribute name="maxThreads">40</attribute>
            <attribute name="acceptCount">10</attribute>
            <attribute name="connectionTimeout">60000</attribute>
            <attribute name="connectionLinger">-1</attribute>
            <attribute name="address">0.0.0.0</attribute>

but when it comes to the rar plan, we always use the first upper case word to 
define the properties, such as:
            <config-property-setting name="Password"/>
            <config-property-setting name="LoginTimeout"/>
            <config-property-setting 
name="DatabaseName">SystemDatabase</config-property-setting>
            <config-property-setting name="UserName"/>
and that causes the program logic in the config module builder should deal with 
that specificly...programmer might hate that..


So, It will be good to support the case-insensitive attribute name, at least, 
we should support the FIRST letter case-insensitive word so that we do not need 
to code specificly for that in builder.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to