Attribute validation xsi:type namespace dependent

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.

Environment

None

Status

Assignee

Christoph Deppisch

Reporter

Christoph Deppisch

Labels

None

Epic Name <span class="error">&#91;deprecated, this field is no longer being used&#93;</span>

None

External issue ID

None

Components

Fix versions

Affects versions

1.0
1.1
1.2
1.3

Priority

Minor