Axis2
  1. Axis2
  2. AXIS2-4534

A non nillable element can be provided with an empty tag and thus resulting in null pointer errors

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: None
    • Component/s: adb
    • Labels:
      None
    • Environment:
      Linux, Java 1.5 (I think), Axis2-1.4

      Description

      In a complex element our wsdl states:

      <xs:element maxOccurs="1" minOccurs="1" name="Content" type="xs:base64Binary"/>

      i.e. the element is not nillable.

      For some reason the user of the service provided it with an empty tag, i.e. <Content/>.
      The result was, that in the method within the skeleton the Content parameter was preset with null, which was not taken into account by the logic.
      I would have expected the deserialisation to throw an error to the service user that an empty tag is not alloved.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Carsten Sierks
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development