Troubleshooting XML schema messages for web service integrations

When you are using a Web Service Integration component, you might encounter error and warning messages if you use XML constructs that are not supported or have problems in Process Designer.

These errors and warnings occur when XML types that are not valid are generated for an external web service through a Web Service Integration component. You see these validation errors or warnings in the type generation panel of the Generate Types wizard, where you can copy them. The panel displays each error or warning and the exact line in the XML construct that is causing the problem. If an error occurs, you can select the Ignore problems and continue type generation to continue the type generation process.

The following tables list the messages you could see in the wizard and information about each message.

Error messages caused by XML constructs that are not valid

Message Description
CWTBG0019E: Unexpected exception during execution. Exception information: 'Unhandled simple type: StringArray. A list type is not supported.' For the external service discovery of a WSDL file, it is not supported, if the WSDL contains a simple type with a list element. For example:
<xsd:element name="StringArray" type="tns:StringArray"/> 
<xsd:simpleType name="StringArray"> 
   <xsd:list itemType="xsd:string"/> 
</xsd:simpleType>
If you try to create an External Service by discovering a WSDL file that contains such an element you get this error message.
To fix the error, use a complex type instead of a simple type, and set the minOccurs and maxOccurs attributes. For example:
<xsd:complexType name="StringArray"> 
   <xsd:sequence> 
      <xsd:element minOccurs="0" name="strings" type="xsd:string" maxOccurs="unbounded"> 
      </xsd:element> 
   </xsd:sequence>
</xsd:complexType>
  • The {0} complex type contains the {1} element that has a type of anySimpleType, which is not supported.
  • The {0} global element has a type of anySimpleType, which is not supported.
The anySimpleType type is not supported.

To fix the error, replace anySimpleType with an appropriate simple type.

The {0} complex type contains attribute {1} that is without a type or uses anySimpleType, which is not supported. The type has an attribute declaration without a type definition, which defaults to anySimpleType or an attribute with anySimpleType. Attributes of anySimpleType are not supported.

To fix the error, assign a simple type or replace anySimpleType with an appropriate simple type.

The {0} complex type contains anyAttribute. Attribute wildcards (anyAttribute) are not supported. Attribute wildcards permit an extension of the content model while providing some control to enforce a minimal constraint. Because wildcards are ignored,anyAttribute is not supported. The location of the wildcard is in XPath format.

To fix the error, replace anyAttribute with an appropriate attribute.

The {0} complex type has a simpleContent child, which is not supported. Complex types allow elements in their content to have a simple content element. Because simple content elements in a complex type are ignored, the simpleContent element is not supported.
The {0} complex type contains an 'any' element . Element wildcards (any) are not supported. Element wild cards, which allow flexibility on what is allowed in the content model, are not supported.

To fix the error, replace ANY with concrete elements.

  • The {0} complex type contains the {1} element that is directly or indirectly mapped to anyType, which is not supported.
  • The {0} global element directly or indirectly maps to anyType, which is not supported.
The anyType type is not supported.

To fix the error, replace anyType with an appropriate type.

The {0} complex type contains a group reference with maxOccurs of {1}. However, the maximum value of maxOccurs is 1. A model group definition associates a name with a model group so that you can reuse the model group. However, Process Designer has a maximum occurrence constraint on the maxOccurs attribute in the model group definition.

To fix the error, change the value of the maxOccurs attribute to 1.

The {0} complex type contains the {1} nested model group with a maxOccurs of {2}. However, the maximum value of maxOccurs is 1. Process Designer has a maximum occurrence constraint on the maxOccurs attribute in the model group definition even if the model group is nested within other elements.

To fix the error, change the value of the maxOccurs attribute in the identified model group to 1.

The {0} simple type is not handled. Union types are not supported. A union type creates a new type, which is the union of two or more simple types. Union types are not supported.

To fix the error, replace the union type with an appropriate simple type.

The {0} complex type extends the {1} complex type. However, the {1} type refers to xsi:type, which is not supported and might cause errors at run time. If you use a derived complex type in place of a specified base complex type, it is assumed that a relationship exists between the base type definition and the derived type. The xsi:type annotations are ignored and only instances of the base complex type are created.

Warning message caused by XML constructs that have problems

Message Description
  • The {0} complex type contains the {1} attribute with a value of "default", which is not supported.
  • The {0} complex type contains the {1} attribute with a value of "fixed", which is not supported.
Process Designer does not support attributes with default or fixed values. These values are ignored.

To remove this warning, if no corresponding attribute is present in an instance document, specify a value for the attribute other than default or fixed.

A type with name {0} already exists. Type names must be unique. Process Designer does not support using qualified or QNames for types. The location of the type is in XPath format. Process Designer generates different names for these types.
  • The {0} complex type contains the element {1} of the base64Binary type. The base64Binary type is transformed to String.
  • The {0} global element is of the base64Binary type. The base64Binary type is transformed to String.
  • The {0} complex type contains the element {1} of the hexBinary type. The hexBinary type is transformed to String.
  • The {0} global element is of the hexBinary type. The hexBinary type is transformed to String.
The base64Binary and hexBinary data types have validation rules that are supported in Process Designer. To prevent them from having values that are not valid in Process Designer, these data types are converted to strings.

To remove this warning, do not use the base64Binary and hexBinary types.

  • The {0} complex type contains the element {1} of the gYear type. The gYear type is transformed to String.
  • The {0} global element is of the gYeartype. The gYear type is transformed to String.
  • The {0} complex type contains the element {1} of the gYearMonth type. The gYearMonth type is transformed to String.
  • The {0} global element is of the gYearMonth type. The gYearMonth type is transformed to String.
The gYear and gYearMonth data types have validation rules that are supported in Process Designer. To prevent them from having values that are not valid in Process Designer, these data types are converted to strings.

To remove this warning, do not use the gYear and gYearMonth types.

  • The {0} complex type contains the element {1} of the normalizedString type. The normalizedString type is transformed to String.
  • The {0} global element is of the normalizedString type. The normalizedString type is transformed to String.
The rules to normalize whitespace values are not supported in Process Designer. To prevent the types from having values that are not valid in Process Designer, their normalized strings are converted to strings.

To remove this warning, do not use the normalizedString type.

  • The {0} complex type contains the element {1} of type {2}, which is transformed to Decimal. The Decimal type maps to xsd:double.
  • The {0} global element is of the type {1} is transformed to Decimal. The Decimal type maps to xsd:double.
All XML decimal numeric types, regardless of their precision, transform to the Decimal type in Business Automation Workflow. The Decimal type maps to the java.lang.Double data type through xsd:double.
  • The {0} complex type contains the element {1} of type {2}, which is transformed to Integer. TheInteger type maps to xsd:int.
  • The {0} global element is of the type {1}, which is transformed to Integer. The Integer type maps to xsd:int.
All XML integer numeric types, regardless of their precision, transform to the Integer type in Business Automation Workflow. The Integer type maps to the java.lang.Integer data type through xsd:int.
The {0} complex type extends the {1} complex type. The generated business object for {0} is flattened to include the elements and attributes that are defined in {1}. When a complex type has a base type, Process Designer includes all the elements and attributes from the base type to flatten business objects that are created from the complex type.
The {0} element contains the substitutionGroup attribute, which is not supported. Substitution groups are ignored. With a substitution group, you can specify elements that can replace another element in documents generated from the schema.
The {0} simple type contains the {1} restriction facet, which is not supported. Process Designer ignores the following XSD restriction facets:
  • maxInclusive
  • maxExclusive
  • minInclusive
  • minExclusive
  • enumeration