Uploaded image for project: 'Citrus'
  1. CITRUS-180

Attribute validation xsi:type namespace dependent

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0, 1.1, 1.2, 1.3
    • Fix Version/s: 1.3.1
    • Component/s: citrus-core
    • Labels:
      None

      Description

      When having XML type inheritance in a WSDL or XSD the message content contains xsi:type attributes. These XML type definitions do have a namespace prefix inside the attribute value like this:

      <myElement xsi:type="ns1:MyType">

      Citrus is validating these type attributes as normal attribute values with the namespace prefix as part of the test value. This leads to hardcoded namespace prefixes in expected message content which is not very comfortable, especially when namespace prefixes do change from time to time.

      Need to implement a strategy for handling those xsi:type definitions in message content independent from namespace prefix.

        Attachments

          Activity

            People

            • Assignee:
              deppisch Christoph Deppisch
              Reporter:
              deppisch Christoph Deppisch
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: