Integration Server 10.3 | Web Services Developer’s Guide | Omitting Well-Known Schema Locations from Generated WSDL
 
Omitting Well-Known Schema Locations from Generated WSDL
Integration Server includes an option to allow the URL for a well-known XML schema definitions namespace and schemaLocation attribute to be omitted from the import statement in the WSDL document generated for a provider web service descriptor.
During web service processing, which includes creating a web service descriptor from a WSDL document and generating a WSDL document for a provider web service descriptor, Integration Server de-references XML schema definitions that contain import statements with a schemaLocation attribute that specifies an external URL. To resolve the URLs, Integration Server requires a connection to the Internet.
Integration Server provides a configuration option to indicate that, when generating a WSDL document for a provider web service descriptor, Integration Serverwill not include the schemaLocation attribute for well-known namespaces. When the schemaLocation attribute is not present, an Integration Server that consumes the WSDL document will not de-reference the schemaLocation attribute value during web service processing. If a schemaLocation attributes in the WSDL document reference only the well-known namespace, then web service development can occur without an Internet connection.
The well-known namespaces that are affected by this setting are:
*http://www.w3.org/XML/1998/namespace
*http://www.w3.org/2003/05/soap-envelope
To configure Integration Server to omit the addition of schemaLocation for the above namespaces, set the watt.core.xsd.useKnownSchemaLocation server configuration parameter to false.
Note:
WS-I compliance requires that in a WSDL document, or files referenced by a WSDL document, all XML Schema imports must contain a schemaLocation attribute. If an XML Schema in the WSDL generated for a web service descriptor contains an import statement for either of the specified namespaces, setting watt.core.xsd.useKnownSchemaLocation to false breaks WS-I compliance