Axis2
  1. Axis2
  2. AXIS2-4972

Second letter capital of a variable value is coming null in server side.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3, 1.6.1
    • Fix Version/s: None
    • Component/s: deployment
    • Labels:
    • Environment:
      Java 1.6 ,apache-tomcat-6.0.14, Eclipse

      Description

      I am using "Axis2_Service_Archiver_1.3.0" eclipse plugin to deploy and publish my service in tomcat 6.0.14.
      In that one method takes the Object input and that object has 7 variables.
      Now the issue is when i call the services from my client side app. one variable value is coming null in server but others are working correctly.
      That variable's 2nd letter is Capital letter is it the problem ?
      Variable name is "mCouponCode" .

      Other variable like 'redeemDate' are working correctly.

      In WSDL file it looks like below. (I have pasted the wsdl part here)

      ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      <xs:complexType name="RedemptionUpdateRequest">
      <xs:sequence>
      <xs:element name="last4digitsOfCardNo" nillable="true" type="xs:string"/>
      <xs:element name="mCouponCode" nillable="true" type="xs:string"/>
      <xs:element name="mobileNo" nillable="true" type="xs:string"/>
      <xs:element name="pvrTxnId" nillable="true" type="xs:string"/>
      <xs:element name="redeemDate" nillable="true" type="xs:string"/>
      <xs:element name="redeemLocation" nillable="true" type="xs:string"/>
      <xs:element name="redeemTime" nillable="true" type="xs:string"/>
      </xs:sequence>
      </xs:complexType>

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

        Activity

        Hide
        nadir amra added a comment -

        My question is what is the setter name for mCouponCode?

        I myself have been trying to determine if there is any way using a POJO class one can define an element in the WSDL where the first character is uppercase. For example, if one has a variable in a class called TempIn, and you have a setter method, setTempIn, the generated element name is WSDL is:

        <xs:element minOccurs="0" name="tempIn" nillable="true" type="xs:string"/>

        which is not what I want. What is curious is that if you have TEmpIn, and the setter is setTEmpIn, then the generated element name is:

        <xs:element minOccurs="0" name="TEmpIn" nillable="true" type="xs:string"/>

        Note that the element name matches.

        And if I have a variable tEmpIn, the setter is setTEmpIn, the element name in WSDL that is generated is:

        <xs:element minOccurs="0" name="TEempIn" nillable="true" type="xs:string"/>

        Finally, if I have a variable tempIn, with setter of setTempIn then the element name in WSDL is:

        <xs:element minOccurs="0" name="tempIn" nillable="true" type="xs:string"/>

        So I am wondering whether this is working correctly and if there is a way for the first character in an element name to be uppercased which the next character is in lowercase?

        I am running 1.5.6. I will try with newest and see what happens but wanted to document my findings.

        Show
        nadir amra added a comment - My question is what is the setter name for mCouponCode? I myself have been trying to determine if there is any way using a POJO class one can define an element in the WSDL where the first character is uppercase. For example, if one has a variable in a class called TempIn, and you have a setter method, setTempIn, the generated element name is WSDL is: <xs:element minOccurs="0" name="tempIn" nillable="true" type="xs:string"/> which is not what I want. What is curious is that if you have TEmpIn, and the setter is setTEmpIn, then the generated element name is: <xs:element minOccurs="0" name="TEmpIn" nillable="true" type="xs:string"/> Note that the element name matches. And if I have a variable tEmpIn, the setter is setTEmpIn, the element name in WSDL that is generated is: <xs:element minOccurs="0" name="TEempIn" nillable="true" type="xs:string"/> Finally, if I have a variable tempIn, with setter of setTempIn then the element name in WSDL is: <xs:element minOccurs="0" name="tempIn" nillable="true" type="xs:string"/> So I am wondering whether this is working correctly and if there is a way for the first character in an element name to be uppercased which the next character is in lowercase? I am running 1.5.6. I will try with newest and see what happens but wanted to document my findings.
        Hide
        Sagara Gunathunga added a comment -

        I haven't test this myself but I also think this won't happen in latest releases, please test with 1.6.1 too and let us know your results.

        Show
        Sagara Gunathunga added a comment - I haven't test this myself but I also think this won't happen in latest releases, please test with 1.6.1 too and let us know your results.
        Hide
        nadir amra added a comment -

        Hi Sagara,

        I have tried it in 1.6.1 and it behaves the same way. So there is no way for a field in a class to have starting character in uppercase and the second character in lowercase and thus generate an element name that starts with an uppercase and second character is in lowercase? I assume this is a bug? And if so, what area of the code does one need to look at to see what can be done?

        Thanks.

        Show
        nadir amra added a comment - Hi Sagara, I have tried it in 1.6.1 and it behaves the same way. So there is no way for a field in a class to have starting character in uppercase and the second character in lowercase and thus generate an element name that starts with an uppercase and second character is in lowercase? I assume this is a bug? And if so, what area of the code does one need to look at to see what can be done? Thanks.
        Hide
        nadir amra added a comment -

        Anyone know what area of the code relates to the problems described in this issue?

        Show
        nadir amra added a comment - Anyone know what area of the code relates to the problems described in this issue?

          People

          • Assignee:
            Unassigned
            Reporter:
            Mahendra
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 221h
              221h
              Remaining:
              Remaining Estimate - 221h
              221h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development