WSDL ODA generates XML Schema parsing warnings prior to business object generation

Technote (troubleshooting)


Despite the fact that a schema correctly imports another schema using the <import> statement, and the imported schema is in the correct location, WSDL ODA may present a warning.


WSDL ODA may present the following warning:

WARNING: XSD: The location 'SomeSchema.xsd' has not been resolved


The reason for the above behavior is due to the schema validation logic used by XSD Info set model. This type of behavior is seen when:

  1. The importing schema does not use any schema components from the imported schema.
  2. The importing schema uses components from the imported schema only in a wsdl:arrayType attribute. This happens as XSD Infoset Model does not parse this attribute as it is not defined by XML Schema. The following example shows this type of reference:
    <schema targetNamespace=" http://localhost:8100/ipcom/services/Order" xmlns="" xmlns:tns1="urn:PrefixPlanService" >
    <import namespace="" schemaLocation=""/>
    <import namespace="" schemaLocation=""/>
    <import namespace="urn:PrefixPlanService" schemaLocation="PrefixPlanService.xsd"/>

    <complexType name="ArrayOf_tns18_PrefixPlan">
    <restriction base="soapenc:Array">
    <attribute ref="soapenc:arrayType" wsdl:arrayType="tns1:PrefixPlan[]"/>

Resolving the problem

This warning does not effect the business object generation. You can ignore this warning and the business object generation will occur successfully.

If you have validated the WSDL and XSDs using other tools, then they can skip schema validation during business object generation by starting the WSDL ODA with the JVM parameter -Dvalidate=false.

Document information

More support for:

WebSphere Adapters Family
Adapter for Web Services

Software version:

3.0, 3.1, 3.2, 3.3, 3.4

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:


Reference #:


Modified date:


Translate my page

Content navigation