<wsdl:import namespace="namespace-name-of-the-WSDL-definition-to-be-imported"
location="location-of-the-WSDL-definition-to-be-imported"/>

Specifies the namespace name of the Import target WSDL definition.

In the namespace attribute of the wsdl:import element coded in the import source WSDL definition, specify the same namespace name as the namespace name of the Import target WSDL definition (targetNamespace attribute of the wsdl:definitions element).

The following table describes the relationship between the namespace of the import source WSDL definition and the namespace of the import target WSDL definition:

Table 26-1 Relationship of the namespaces for the WSDL definition (Import source/ import target)

No.	Import source WSDL definition	Import target WSDL definition	Conditions	Runtime operations
1	namespace attribute of the wsdl:import element	targetNamespace attribute of the wsdl:definitions element	Matching	Terminates normally.
2			Not matching	A warning message is output in the standard error output and log and the processing continues (KDJW51191-W). The elements of the import target WSDL definition and import source WSDL definition belong to the respective namespaces.
3	targetNamespace attribute of the wsdl:definitions element		Matching	A warning message is output in the standard error output and log and the processing continues (KDJW51192-W). The elements of the import target WSDL definition and import source WSDL definition belong to the same namespace.
4			Not matching	Terminates normally.

Specifies the location of the WSDL definition to be imported.

The conditions for the strings specified in the location attribute are as follows:

• You can specify the WSDL file available in the relative path, remote, or local using the URL format.
• The WSDL file included in the WAR file is issued as the meta data (except when a new WSDL file is generated). However, you need to take precautions when issuing the meta data. For details about the precautions for issuing the meta data, see 10.6(6) Notes for importing/including WSDL definition or XML Schema.
• Use characters defined in RFC 2396 and characters fulfilling xsd:anyURI. However, you cannot use RFC 2732 (IPv6).
• The strings are not case sensitive.
• The maximum length of the specifiable sting is not limited. However, an error occurs when you exceed the limit set for the OS.

The following table describes an example of coding of the location attribute:

Table 26-2 Example of specification of the location attribute (WSDL import functionality)

No.	Specified contents	Example of specification
1	Specifying the local WSDL file using the relative path#1	./wsdl/input.wsdl
2	Specifying the local WSDL file using the absolute path expressed with a URL (file://~) #1, 2	file:///C:/tmp/wsdl/input.wsdl
3	Specifying the remote WSDL file using a URL (http:~)#3	http://example.com:8080/fromjava/test?wsdl

#1

When you specify the WSDL file using the relative path or absolute path, specify the correct path. If the path is wrong and the WSDL file is not found, an error message is output in the standard error output and log and the processing ends (KDJW51197-E or KDJW51198-E).

#2

You cannot specify an absolute path string beginning with a drive such as "C:/~". If such a string is specified, an error message will be output in the standard error output and log and the processing will end (KDJW51199-E).

#3

When you specify a remote WSDL file using a URL, specify the correct URL. If the path is wrong and the WSDL file is not found, an error message will be output in the standard error output and log and the processing will end (KDJW51197-E or KDJW51198-E).