FUSE Tools

WS-I Basic Profile 1.1 and Schema Reference Behaviors and Specifications

2009-09-16T00:01:00.000-07:00

What is the need for WS-I Basic Profile?

WS-I Basic Profile defines specification for WSDL document to avoid the confusion present in WSDL specification. As per WSDL specification following example is valid but as per WS-I it is incorrect

<wsdl:definitions name="StockQuote"
targetNamespace="http://example.com/stockquote/definitions"
xmlns:stock="http://example.com/stockquote/schemas""
...
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

< wsdl:import namespace="http://example.com/stockquote/schemas"
location="http://example.com/stockquote/stockquote.xsd"/>

< wsdl:message name="GetLastTradePriceInput">
< wsdl:part name="body" element="xsd1:TradePriceRequest"/>
</ wsdl:message>
...
</ wsdl:definitions>

As per WS-I Basic Profile we can import only WSDL document using wsdl:import. For importing XSD document we need to use xsd:import within wsdl:type section as follows:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="StockQuote"
targetNamespace="http://example.com/stockquote/definitions"
xmlns:stock="http://example.com/stockquote/schemas"
...
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<xsd:schema targetNamespace="urn:myschema"
xmlns:stock="http://example.com/stockquote/schemas"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://example.com/stockquote/schemas" schemaLocation="http://example.com/stockquote/stockquote.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="GetLastTradePriceInput">
< wsdl:part name="body" element="stock:TradePriceRequest"/>
</wsdl:message>
...
</wsdl:definitions>

What am I going to discuss in this post?

On reading the spec it is not immediately clear what the point means and having examples would be really useful. So I am going to discuss the points from the spec related to types/elements visibility with several examples. WS-I Basic Profile provides specifications for WSDL, SOAP, XML, XML Schema and many other things related to Web Services. Among these, I am going to discuss about the visibility of types defined in the Type section of WSDL as well as imported / included types from XML schema (XSD). Also how XML schema data types are visible within schema document as well as across imported and included schema documents.

I will begin with visibility for XSD document and later discuss the type visibility for WSDL document

Visibility for XSD document along with sample XML document

Import XSD document inside another XSD document

Types, elements, attributes and groups defined in imported XSD document should be visible inside current XSD document

Example:

SubSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://subNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://subNamespace.com"
xmlns="http://subNamespace.com">
<xsd:complexType name="AComplexTypeInSubSchema">
<xsd:sequence>
<xsd:element name="SomeData" type="xsd:string">
</xsd:element>
<xsd:element name="SomeMoreData" type="xsd:string">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

MasterSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://masterNamespace.com"
xmlns:ssns="http://subNamespace.com"
xmlns:tns="http://masterNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://subNamespace.com" schemaLocation="SubSchema.xsd"/>
<xsd:complexType name="AComplexTypeInMaster">
<xsd:sequence>
<xsd:element name="MasterTypeData1" type="xsd:string"/>
<xsd:element name="ElementFromSubSchemaType" type="ssns:AComplexTypeInSubSchema"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="ElementFromMasterSchemaType" type="tns:AComplexTypeInMaster"/>
</xsd:schema>

As shown in above examples "AComplexTypeInSubSchema" is defined in "SubSchema.xsd" which becomes visible in MasterSchema.xsd after "SubSchema.xsd" is imported inside "MasterSchema.xsd".
Note: "AComplexTypeInSubSchema" is accessible in MasterSchema.xsd using namespace prefix ssns defined for its namespace "http://subNamespace.com"

Sample XML Document using ElementFromMasterSchemaType

<?xml version="1.0" encoding="UTF-8"?>
<com:ElementFromMasterSchemaType xsi:schemaLocation="http://masterNamespace.com file:/C:/Schemas/importedtypes/MasterSchema.xsd"
xmlns:com="http://masterNamespace.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<MasterTypeData1>string</MasterTypeData1>
<ElementFromSubSchemaType>
<SomeData>string</SomeData>
<SomeMoreData>string</SomeMoreData>
</ElementFromSubSchemaType>
</com:ElementFromMasterSchemaType>

Types, elements, attributes and groups defined in nested imported XSD document not be visible inside current XSD document

Example:

SubSchema2.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://subNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://subNamespace2.com"
xmlns="http://subNamespace.com">
<xsd:complexType name="ANestedComplexTypeInSubSchema">
<xsd:sequence>
<xsd:element name="SomeData" type="xsd:string">
</xsd:element>
<xsd:element name="SomeMoreData" type="xsd:string">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

SubSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://subNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://subNamespace.com"
xmlns:ssns="http://subNamespace2.com"
xmlns="http://subNamespace.com">
<xsd:import namespace="http://subNamespace2.com" schemaLocation="SubSchema2.xsd"/>
<xsd:complexType name="AComplexTypeInSubSchema">
<xsd:sequence>
<xsd:element name="SomeData" type="xsd:string">
</xsd:element>
<xsd:element name="SomeMoreData" type="xsd:string">
</xsd:element>
<xsd:element name="ElementFromNestedSubSchemaType" type="ssns:ANestedComplexTypeInSubSchema"/><!-- This is valid -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

MasterSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://masterNamespace.com"
xmlns:ssns="http://subNamespace.com"
xmlns:tns="http://masterNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://subNamespace.com" schemaLocation="SubSchema.xsd"/>
<xsd:complexType name="AComplexTypeInMaster">
<xsd:sequence>
<xsd:element name="MasterTypeData1" type="xsd:string"/>
<xsd:element name="MasterTypeData2" type="xsd:string"/>
<xsd:element name="ElementFromNestedSubSchemaType" type="ssns:ANestedComplexTypeInSubSchema"/><!-- This is not valid -->
<xsd:element name="ElementFromSubSchemaType" type="ssns:AComplexTypeInSubSchema"/><!-- This is valid -->
</xsd:sequence>
</xsd:complexType>
<xsd:element name="ElementFromMasterSchemaType" type="tns:AComplexTypeInMaster"/>
</xsd:schema>

In the above examples MasterSchema.xsd is importing SubSchema.xsd and SubSchema.xsd is further importing SubSchema2.xsd. As I mentioned above nested imported types are not visible in the current schema document. Therefor, using ANestedComplexTypeInSubSchema which is defined in SubSchema2.xsd is invalid for MasterSchema.xsd but same thing is valid inside SubSchema.xsd since it is directly importing SubSchema2.xsd
As per the previous example using AComplexTypeInSubSchema inside MasterSchema.xsd is valid, since we have imported SubSchema.xsd in MasterSchema.xsd

If imported XSD file has included some XSD files then type, elements, attributes and groups defined in that nested included XSD file should be visible inside current XSD document

Example:

SubSchema2.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://subNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://subNamespace2.com"
xmlns="http://subNamespace.com">
<xsd:complexType name="ANestedComplexTypeInSubSchema">
<xsd:sequence>
<xsd:element name="SomeData" type="xsd:string">
</xsd:element>
<xsd:element name="SomeMoreData" type="xsd:string">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

SubSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://subNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://subNamespace.com"
xmlns="http://subNamespace.com">
<xsd:include schemaLocation="SubSchema2.xsd"/>
<xsd:complexType name="AComplexTypeInSubSchema"> <!-- This is valid -->
<xsd:sequence>
<xsd:element name="mysubelement" type="xsd:string">
</xsd:element>
<xsd:element name="nestedIncludedElement" type="ANestedComplexTypeInSubSchema">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

MasterSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://masterNamespace.com"
xmlns:ssns="http://subNamespace.com"
xmlns:tns="http://masterNamespace.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://subNamespace.com" schemaLocation="SubSchema.xsd"/>
<xsd:complexType name="AComplexTypeInMaster">
<xsd:sequence>
<xsd:element name="MasterTypeData1" type="xsd:string"/>
<xsd:element name="ElementFromSubSchemaType" type="ssns:AComplexTypeInSubSchema"/> <!-- This is valid -->
<xsd:element name="myNestedIncluedElement" type="ssns:ANestedComplexTypeInSubSchema"/><!-- This is valid -->
</xsd:sequence>
</xsd:complexType>

<xsd:element name="ElementFromMasterSchemaType" type="tns:AComplexTypeInMaster"/>
</xsd:schema>

In the above examples MasterSchema.xsd is importing SubSchema.xsd and SubSchema.xsd is further including SubSchema2.xsd. As I mentioned above nested included types are not visible in the current schema document. Therefor, using ANestedComplexTypeInSubSchema which is defined in SubSchema2.xsd is valid for MasterSchema.xsd and also inside SubSchema.xsd since it is directly importing SubSchema2.xsd
Sample XML Document using ElementFromMasterSchemaType in MasterSchema.xsd

<?xml version="1.0" encoding="UTF-8"?>
<com:ElementFromMasterSchemaType
xsi:schemaLocation="http://masterNamespace.com file:/C:/Schemas/nestedImport/MasterSchema.xsd"
xmlns:com="http://masterNamespace.com"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<MasterTypeData1>string</MasterTypeData1>
<ElementFromSubSchemaType>
<mysubelement>string</mysubelement>
<nestedIncludedElement>
<SomeData>string</SomeData>
<SomeMoreData>string</SomeMoreData>
</nestedIncludedElement>
</ElementFromSubSchemaType>
<myNestedIncluedElement>
<SomeData>string</SomeData>
<SomeMoreData>string</SomeMoreData>
</myNestedIncluedElement>
</com:ElementFromMasterSchemaType>

Include XSD document within another XSD

Types, elements, attributes and groups defined in included XSD file should be visible inside current XSD document

Examples

A.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

B.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace">
<xsd:include schemaLocation="A.xsd"/>
<xsd:element name="BAElement" type="BType"/>
<xsd:element name="AElementInsideB" type="AType"/> <!-- Valid Included Type  -->
<xsd:complexType name="BType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

As shown in the above example B.xsd is including A.xsd and hence AType is visible inside B.xsd

Types, elements, attributes and groups defined in nested included XSD file should be visible inside current XSD document

Example

A.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

B.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace">
<xsd:include schemaLocation="A.xsd"/>
<xsd:element name="BAElement" type="BType"/>
<xsd:element name="AElementInsideB" type="AType"/> <!-- This is valid Included Type  -->
<xsd:complexType name="BType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

C.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace">
<xsd:include schemaLocation="B.xsd"/>
<xsd:element name="CElement" type="CType"/>
<xsd:element name="AElementInsideC" type="AType"/>    <!-- This is valid Nested included Type -->
<xsd:element name="BElementInsideC" type="BType"/>    <!-- This is valid direct included Type -->
<xsd:complexType name="CType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

In the above examples B.xsd is including A.xsd and C.xsd is including B.xsd, i.e. A.xsd is nested included inside C.xsd. As I mentioned above the AType defined in A.xsd is visible inside B.xsd as well as C.xsd

If included XSD files has imported some XSD file then those types, elements, attributes and groups defined in that nested imported XSD file must not be visible inside current XSD document.
If we want to make types, elements, attributes and groups from nested imported XSD document visible then need to explicitly import that XSD document.

Exammple

D.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/anothernamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/anothernamespace">
<xsd:element name="DElement" type="DType"/>
<xsd:complexType name="DType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

B.xsd

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace"
xmlns:dn="http://example.org/anothernamespace">
<xsd:import namespace="http://example.org/anothernamespace" schemaLocation="D.xsd"/>
<xsd:element name="BAElement" type="BType"/>
<xsd:element name="DElementInsideB" type="dn:DType"/> <!-- Valid use of Imported Type  -->
<xsd:complexType name="BType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

C.xsd (Invalid use of nested import)

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace">
<xsd:include schemaLocation="B.xsd"/>
<xsd:element name="CElement" type="CType"/>
<xsd:element name="AElementInsideC" type="BType"/><!-- This is valid, included Type -->
<xsd:element name="DElementInsideC" type="dn:DType"/&gt;<!-- This is not valid, nested imported Type -->
<xsd:complexType name="CType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

C.xsd (Valid use of imported type)

<?xml version="1.0"?>
<xsd:schema targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://example.org/mynamespace"
xmlns:dn="http://example.org/anothernamespace">
<xsd:include schemaLocation="B.xsd"/>
<xsd:import namespace="http://example.org/anothernamespace" schemaLocation="D.xsd"/>
<xsd:element name="CElement" type="CType"/>
<xsd:element name="AElementInsideC" type="BType"/><!-- This is valid, included Type -->
<xsd:element name="DElementInsideC" type="dn:DType"/><!-- This is valid, imported Type -->
<xsd:complexType name="CType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

As shown in the above example B.xsd is importing D.xsd so it is valid to use DType in B.xsd
In invalid C.xsd we are including B.xsd in C.xsd. In this case using BType inside C.xsd is valid case but using DType inside C.xsd is invalid since it is not imported in C.xsd and hence it is not visible as I mentioned before
To make DType visible inside C.xsd we must import D.xsd in C.xsd as shown in the valid example above

Visibility for WSDL document along with sample WSDL document

Importing WSDL/XSD document using <wsdl:import>

Types, elements, attributes and groups defined in imported WSDL/XSD document must not be visible inside current WSDL document, but the other parts of the imported WSDL are visible inside current WSDL(read next point for more details)

Examples

listing5.wsdl

<?xml version="1.0"?>
<wsdl:definitions targetNamespace="urn:listing5"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema targetNamespace="urn:listing5"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/2001/XMLSchema"/>
<xsd:complexType name="Phone">
<xsd:sequence>
<xsd:element name="areaCode" type="xsd:int"/>
<xsd:element name="exchange" type="xsd:int"/>
<xsd:element name="number" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
</wsdl:definitions>

listing.wsdl

<?xml version="1.0"?>
<wsdl:definitions targetNamespace="urn:listing4"
xmlns:tns="urn:listing4"
xmlns:listing5="urn:listing5"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:import namespace="urn:listing5" location="listing5.wsdl"/>
<wsdl:types>
<xsd:schema targetNamespace="urn:listing4"
xmlns:listing5="urn:listing5"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/2001/XMLSchema"/>
<xsd:complexType name="Address">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="phone" type="listing5:Phone"/><!-- This is imported type form listing5.wsdl which not valid according to Basic Profile -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="GetAddressRequest">
<wsdl:part name="name" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="GetAddressResponse">
<wsdl:part name="address" type="listing5:Phone"/><!-- This is imported type form listing5.wsdl which not valid according to Basic Profile -->
</wsdl:message>
<wsdl:message name="GetPhoneRequest">
<wsdl:part name="name" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="GetPhoneResponse">
<wsdl:part name="phone" type="listing5:Phone"/><!-- This is imported type form listing5.wsdl which not valid according to Basic Profile -->
</wsdl:message>
<wsdl:portType name="AddressBook">
<wsdl:operation name="getAddress">
<wsdl:input message="tns:GetAddressRequest"/>
<wsdl:output message="tns:GetAddressResponse"/>
</wsdl:operation>
<wsdl:operation name="getPhone">
<wsdl:input message="tns:GetPhoneRequest"/>
<wsdl:output message="tns:GetPhoneResponse"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>

In the above example listing.wsdl is importing listing5.wsdl using wsdl:import and we are using xsd type Phone defined in listing5.wsdl inside listing.wsdl which looks correct when you see this first time. But as per basic profile this is not allowed and listing.wsdl is invalid WSDL document as per basic profile WS-I
If we want to import some type in WSDL document then we must declare it inside XSD document and import this using xsd:import I will discuss xsd:import in more details in following points

<wsdl:import> must be used only for importing another WSDL description other than wsdl:type section and <wsdl:import> must not be used to import an XSD schema document. We must use <xsd:import> to import XSD schema documents

Examples

Imported.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="Imported"
targetNamespace="http://www.example.org/Imported/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.example.org/Imported/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema targetNamespace="http://www.example.org/Imported/">
<xsd:element name="NewOperationResponse" type="xsd:string"/>
<xsd:element name="NewOperationRequest" type="xsd:string"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="NewOperationResponse">
<wsdl:part element="tns:NewOperationResponse" name="NewOperationResponse"/>
</wsdl:message>
<wsdl:message name="NewOperationRequest">
<wsdl:part element="tns:NewOperationRequest" name="NewOperationRequest"/>
</wsdl:message>
<wsdl:portType name="Imported">
<wsdl:operation name="NewOperation">
<wsdl:input message="tns:NewOperationRequest"/>
<wsdl:output message="tns:NewOperationResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ImportedSOAP" type="tns:Imported">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="NewOperation">
<soap:operation soapAction="http://www.example.org/Imported/NewOperation"/>
<wsdl:input>
<soap:body parts="NewOperationRequest" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body parts="NewOperationResponse" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="Imported">
<wsdl:port binding="tns:ImportedSOAP" name="ImportedSOAP">
<soap:address location="http://www.example.org/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Master.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:ESBP_TO_WSDL/xsd/examples/Master"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/examples/Master"
xmlns:imp="http://www.example.org/Imported/">
<wsdl:import namespace="http://www.example.org/Imported/" location="Imported.wsdl"/>
<wsdl:types>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="xsd:anyType">
</wsdl:part>
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput" type="xsd:anyType">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="MasterPortType">
<wsdl:operation name="Master">
<wsdl:input message="tns:Request">
</wsdl:input>
<wsdl:output message="tns:Response">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MasterSOAPBinding" type="tns:MasterPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="Master">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/examples/Master:MasterPortType:MasterRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/examples/Master" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/examples/Master" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="MasterService">
<wsdl:port name="MasterPort" binding="tns:MasterSOAPBinding">
<soap:address location="http://localhost:2580/process/Master"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="ImportedService">
<wsdl:port name="ImportedPort" binding="imp:ImportedSOAP"><!-- Referring to imported binding which is correct as per WS-I Basic Profile -->
<soap:address location="http://localhost:2580/process/Imported"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

In the above examples we are importing Imported.wsdl into Master.wsdl and we are referring to binding ImportedSOAP defined inside Imported.wsdl into Master.wsdl which is correct use of wsdl:import as per WS-I Basic Profile Specifications

Importing XSD using <wsdl:import> is not valid, we must use <xsd:import> for importing XSD file inside WSDL file

Example

Sample.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="urn:ESBP_TO_WSDL/xsd/examples/Master" xmlns:imp="http://www.example.org/Imported/" targetNamespace="urn:ESBP_TO_WSDL/xsd/examples/Master" >
<wsdl:import namespace="http://www.example.org/Imported/" location="Imported.wsdl"/> <!-- This is valid, importing wsdl document using wsdl:import  -->
<wsdl:import namespace="http://www.example.org/Imported/" location="Imported.xsd"/> <!-- This is invalid, we must use xsd:import to import xsd file as per basic profile -->

<wsdl:types>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="xsd:anyType"></wsdl:part>
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput" type="xsd:anyType"></wsdl:part>
</wsdl:message>
<wsdl:portType name="MasterPortType">
<wsdl:operation name="Master">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="MasterSOAPBinding" type='tns:MasterPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="Master">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/examples/Master:MasterPortType:MasterRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/examples/Master" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/examples/Master" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="MasterService">
<wsdl:port name="MasterPort" binding='tns:MasterSOAPBinding' >
<soap:address location="http://localhost:2580/process/Master"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="ImportedService">
<wsdl:port name="ImportedPort" binding='imp:ImportedSOAP' >
<soap:address location="http://localhost:2580/process/Imported"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

In the above Sample.wsdl document we have imported XSD schema documnet Imported.xsd using wsdl:import which is not allowed as per WS-I basic profile and we must use xsd:import to import XSD schema documents which I am going to discuss in the following points

Importing XSD file using <xsd:import> within <xsd:schema> section of <wsdl:types> section of WSDL document

Types, elements, attributes and groups defined in imported XSD schema document (using <xsd:import>) should be visible inside same <xsd:schema> section of <wsdl:types> section

Examples

A.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

A.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test"
xmlns:A="http://example.org/mynamespace"> <!-- Namespaces are declared here for imported XSD as well as for schema section namespace -->
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test">
<xsd:import namespace="http://example.org/mynamespace" schemaLocation="A.xsd"></xsd:import> <!-- Correct method of importing XSD schema socument in WSDL as per WS-I Basic Profile Specifications -->  
<xsd:element name="ElementOfTypeA" type="A:AType"></xsd:element> <!-- Imported Type from A.xsd -->
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="ElFromA" ref="A:AElement"/>  <!-- Imported element from A.xsd -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="A:AType"></wsdl:part><!-- Imported Type from A.xsd -->
<wsdl:part name="DefaultInput2" element="A:AElement"></wsdl:part>  <!-- Imported element from A.xsd -->
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput"
type="test:MyComplexType"></wsdl:part> <!-- Type from schema section -->
<wsdl:part name="DefaultOutput2"
element="test:ElementOfTypeA"></wsdl:part><!-- Element from schema section -->
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

In the above examples A.wsdl is importing A.xsd using xsd:import withing xsd:schema section of wsdl:types section of WSDL document which is correct way of importing XSD schema document inside WSDL document as per WS-I Basic Profile Specifications

Types, elements, attributes and groups defined in imported XSD file should not be visible inside another <xsd:schema> section of <wsdl:types> unless it is explicitly imported in that <xsd:schema> schema section using <xsd:import>

Examples

A.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

A.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test"
xmlns:A="http://example.org/mynamespace">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test">
<xsd:import namespace="http://example.org/mynamespace" schemaLocation="A.xsd">
</xsd:import>
<xsd:element name="ElementOfTypeA" type="AType">
</xsd:element>
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="ElFromA" ref="A:AElement"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2">
<xsd:import namespace="http://example.org/mynamespace"/>
<xsd:element name="ElOfTypeA" type="A:AType"/> <!-- This is valid since the namespace is imported here -->
<xsd:complexType name="AnotherComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="test:MyComplexType"/> <!-- This is invalid since the namespace is not imported here -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="A:AType">
</wsdl:part>
<wsdl:part name="DefaultInput2" element="A:AElement">
</wsdl:part>
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput" type="test:MyComplexType">
</wsdl:part>
<wsdl:part name="DefaultOutput2" element="test:ElementOfTypeA">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request">
</wsdl:input>
<wsdl:output message="tns:Response">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type="tns:sample_wsdl_import_xsdPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding="tns:sample_wsdl_import_xsdSOAPBinding">
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Types, elements, attributes and groups defined in imported XSD file should be visible in <wsdl:part> section of <wsdl:message> if the namespace of imported XSD file is declared as attribute of <wsdl:definitions>

Example

A.xsd

<?xml version="1.0"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"

targetNamespace="http://example.org/mynamespace"

xmlns="http://example.org/mynamespace">

<xsd:element name="AElement" type="AType"/>

<xsd:complexType name="AType">

<xsd:sequence>

<xsd:element name="elStr" type="xsd:string"/>

<xsd:element name="elInt" type="xsd:int"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

A.wsdl

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"

targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"

xmlns:test="urn:ESBP_TO_WSDL/esbp/test">

<wsdl:types>

<xsd:schema elementFormDefault="qualified"

targetNamespace="urn:ESBP_TO_WSDL/esbp/test"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:test="urn:ESBP_TO_WSDL/esbp/test">

<xsd:import namespace="http://example.org/mynamespace" schemaLocation="A.xsd"></xsd:import>

<xsd:element name="ElementOfTypeA" type="AType"></xsd:element>

<xsd:complexType name="MyComplexType">

<xsd:sequence>

<xsd:element name="streetNum" type="xsd:int"/>

<xsd:element name="streetName" type="xsd:string"/>

<xsd:element name="city" type="xsd:string"/>

<xsd:element name="state" type="xsd:string"/>

<xsd:element name="ElFromA" ref="A:AElement"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

<xsd:schema elementFormDefault="qualified"

targetNamespace="urn:ESBP_TO_WSDL/esbp/test"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2"

xmlns:test="urn:ESBP_TO_WSDL/esbp/test">

<xsd:import namespace="http://example.org/mynamespace" schemaLocation="A.xsd"></xsd:import>

<xsd:import namespace="urn:ESBP_TO_WSDL/esbp/test"/>

<xsd:element name="ElOfTypeA" type="A:AType"></xsd:element>

<xsd:complexType name="AnotherComplexType">

<xsd:sequence>

<xsd:element name="streetNum" type="xsd:int"/>

<xsd:element name="streetName" type="xsd:string"/>

<xsd:element name="city" type="xsd:string"/>

<xsd:element name="state" type="test:MyComplexType"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

</wsdl:types>

<wsdl:message name="Request">

<wsdl:part name="DefaultInput" type="A:AType"></wsdl:part> <!-- This is not valid since namespace is not declared as attribute of wsdl:definitions -->

<wsdl:part name="DefaultInput2" element="A:AElement"></wsdl:part><!-- This is not valid since namespace is not declared as attribute of wsdl:definitions -->



</wsdl:message>

<wsdl:message name="Response">

<wsdl:part name="DefaultOutput"

type="test:MyComplexType"></wsdl:part>

<wsdl:part name="DefaultOutput2"

element="test:ElementOfTypeA"></wsdl:part>

<wsdl:part name="DefaultOutput3"

type="test2:AnotherComplexType"></wsdl:part><!-- This is not valid since namespace is not declared as attribute of wsdl:definitions -->



</wsdl:message>

<wsdl:portType name="sample_wsdl_import_xsdPortType">

<wsdl:operation name="sample_wsdl_import_xsd">

<wsdl:input message="tns:Request"></wsdl:input>

<wsdl:output message="tns:Response"></wsdl:output>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="sample_wsdl_import_xsd">

<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>

<wsdl:input>

<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>

</wsdl:input>

<wsdl:output>

<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="sample_wsdl_import_xsdService">

<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >

<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

Above A.wsdl is not valid according to basic profile, to make above example correct as per basic profile please check the following example

ValidA.wsdl

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"

targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"

xmlns:test="urn:ESBP_TO_WSDL/esbp/test"

xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2"

xmlns:A="http://example.org/mynamespace">

<wsdl:types>

<xsd:schema elementFormDefault="qualified"

targetNamespace="urn:ESBP_TO_WSDL/esbp/test"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:test="urn:ESBP_TO_WSDL/esbp/test">

<xsd:import namespace="http://example.org/mynamespace" schemaLocation="A.xsd"></xsd:import>

<xsd:element name="ElementOfTypeA" type="AType"></xsd:element>

<xsd:complexType name="MyComplexType">

<xsd:sequence>

<xsd:element name="streetNum" type="xsd:int"/>

<xsd:element name="streetName" type="xsd:string"/>

<xsd:element name="city" type="xsd:string"/>

<xsd:element name="state" type="xsd:string"/>

<xsd:element name="ElFromA" ref="A:AElement"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

<xsd:schema elementFormDefault="qualified"

targetNamespace="urn:ESBP_TO_WSDL/esbp/test"

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2"

xmlns:test="urn:ESBP_TO_WSDL/esbp/test">

<xsd:import namespace="http://example.org/mynamespace" schemaLocation="A.xsd"></xsd:import>

<xsd:import namespace="urn:ESBP_TO_WSDL/esbp/test"/>

<xsd:element name="ElOfTypeA" type="A:AType"></xsd:element>

<xsd:complexType name="AnotherComplexType">

<xsd:sequence>

<xsd:element name="streetNum" type="xsd:int"/>

<xsd:element name="streetName" type="xsd:string"/>

<xsd:element name="city" type="xsd:string"/>

<xsd:element name="state" type="test:MyComplexType"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

</wsdl:types>

<wsdl:message name="Request">

<wsdl:part name="DefaultInput" type="A:AType"></wsdl:part><!-- This is valid since namespace is declared as attribute of wsdl:definitions -->

<wsdl:part name="DefaultInput2" element="A:AElement"></wsdl:part><!-- This is valid since namespace is declared as attribute of wsdl:definitions -->

</wsdl:message>

<wsdl:message name="Response">

<wsdl:part name="DefaultOutput"

type="test:MyComplexType"></wsdl:part>

<wsdl:part name="DefaultOutput2"

element="test:ElementOfTypeA"></wsdl:part>

<wsdl:part name="DefaultOutput3"

type="test2:AnotherComplexType"></wsdl:part><!-- This is valid since namespace is declared as attribute of wsdl:definitions -->

</wsdl:message>

<wsdl:portType name="sample_wsdl_import_xsdPortType">

<wsdl:operation name="sample_wsdl_import_xsd">

<wsdl:input message="tns:Request"></wsdl:input>

<wsdl:output message="tns:Response"></wsdl:output>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="sample_wsdl_import_xsd">

<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>

<wsdl:input>

<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>

</wsdl:input>

<wsdl:output>

<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="sample_wsdl_import_xsdService">

<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >

<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

Types, elements, attributes and groups defined in nested imported XSD file should not be visible inside same <schema> section of <wsdl:types> as well as inside <wsdl:part> section of <wsdl:message>

Example

A.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespaceA">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

B.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespaceB"
xmlns:A=”http://example.org/mynamespaceA”>
<xsd:import namespace=”http://example.org/mynamespaceA”
schemaLocation="A.xsd"/>
<xsd:element name="BAElement" type="BType"/>
<xsd:element name="AElementInsideB" type="AType"/>
<xsd:complexType name="BType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

NestedInvalid.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test"
xmlns:B="http://example.org/mynamespaceB">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test">
<xsd:import namespace="http://example.org/mynamespaceB" schemaLocation="B.xsd"></xsd:import>
<xsd:element name="ElementOfTypeA" type="AType"></xsd:element>
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="ElFromA" ref="AElement"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput"
type="A:AType"></wsdl:part><!-- This is invalid use of type since this is from A.xsd the nested imported file-->

<wsdl:part name="DefaultInput2"
element="A:AElement"></wsdl:part><!-- This is invalid use of element since this is from A.xsd the nested imported file-->

</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput"
type="test:MyComplexType"></wsdl:part>
<wsdl:part name="DefaultOutput2"
element="test:ElementOfTypeA"></wsdl:part> <!-- This is invalid use of element since this is from A.xsd the nested imported file-->
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Including XSD document using <xsd:include> within <xsd:schema> section of <wsdl:types>

Types, elements, attributes and groups defined in included XSD document should be visible inside same <xsd:schema> section of <wsdl:types>

Example

A.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema><?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

B.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:include schemaLocation="A.xsd"/>
<xsd:element name="BAElement" type="BType"/>
<xsd:element name="AElementInsideB" type="AType"/>
<xsd:complexType name="BType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Sample.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test"
xmlns:B="http://example.org/mynamespace">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace="http://example.org/mynamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:B="http://example.org/mynamespace">
<xsd:include schemaLocation="B.xsd"></xsd:import>
<xsd:element name="ElementOfTypeA" type="B:AType"></xsd:element><!-- This is nested element type from A.xsd -->
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="ElFromA" ref="B:BElement"/> <!-- This is included element from B.xsd -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="B:BType"></wsdl:part><!-- This is included type from B.xsd -->
<wsdl:part name="DefaultInput2" element="B:AElement"></wsdl:part><!-- This is nested included element from A.xsd -->
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput"
type="B:MyComplexType"></wsdl:part>
<wsdl:part name="DefaultOutput2"
element="B:ElementOfTypeA"></wsdl:part>
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Types, elements, attributes and groups defined in included XSD document should not be visible inside another <xsd:schema> section of <wsdl:types> unless it is explicitly imported in that <xsd:schema> schema section

Example

A.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema><?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:element name="AElement" type="AType"/>
<xsd:complexType name="AType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

B.xsd

<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://example.org/mynamespace"
xmlns="http://example.org/mynamespace">
<xsd:include schemaLocation="A.xsd"/>
<xsd:element name="BAElement" type="BType"/>
<xsd:element name="AElementInsideB" type="AType"/>
<xsd:complexType name="BType">
<xsd:sequence>
<xsd:element name="elStr" type="xsd:string"/>
<xsd:element name="elInt" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Sample.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test"
xmlns:B="http://example.org/mynamespace">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace=" http://example.org/mynamespace "
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:B=" http://example.org/mynamespace ">
<xsd:import namespace="http://example.org/mynamespace" schemaLocation="B.xsd"></xsd:import>
<xsd:element name="ElementOfTypeA" type="B:AType"></xsd:element><!-- This is nested type from A.xsd -->
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="ElFromA" ref="B:BElement"/> <!-- This is included element from B.xsd -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test="urn:ESBP_TO_WSDL/esbp/test">
<xsd:element name="ElementOfTypeA" type="B:AType"></xsd:element><!-- This is nested element type from A.xsd but it should not be visible in this schema section -->
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="ElFromA" ref="B:BElement"/> <!-- This is included element from B.xsd but this should not be visible here -->
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="B:BType"></wsdl:part><!-- This is included type from B.xsd -->
<wsdl:part name="DefaultInput2" element="B:AElement"></wsdl:part><!-- This is nested included element from A.xsd -->
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput"
type="test:MyComplexType"></wsdl:part>
<wsdl:part name="DefaultOutput2"
element="test:ElementOfTypeA"></wsdl:part>
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

Types, elements, attributes and groups defined in included XSD document withing <xsd:schema> section of <wsdl:types> section, should be visible in <wsdl:part> section of <wsdl:message> if the namespace of included XSD document is declared as attribute of <wsdl:definitions>
- Example: The previous example also explains this point
Types, elements, attributes and groups defined in nested included XSD document should be visible inside same <xsd:schema> section of <wsdl:types> as well as inside <wsdl:part> section of <wsdl:message> if included schema’s namespace is defined as attribute of <wsdl:definitions>
- Example: The previous example also explains this point

Visibility of types, elements, attributes and groups across multiple <xsd:schema> section of <wsdl:types> of WSDL document

Types, elements, attributes and groups defined in one <xsd:schema> inside <wsdl:types> should not be by default visible inside another <xsd:schema> section

Example

Sample.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test1="urn:ESBP_TO_WSDL/esbp/test1"
xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test1="urn:ESBP_TO_WSDL/esbp/test1">
<xsd:element name="MyComplexElement"
type="test1:MyComplexType"></xsd:element>
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/> s
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2">
<xsd:element name="MyElement" type="test1:MyComplexType" /><!-- This is not valid since namespace ("urn:ESBP_TO_WSDL/esbp/test1") of another schema section is not imported here  -->
<xsd:complexType name="AnotherCompleType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="test1:MyComplexType"></wsdl:part>
<wsdl:part name="DefaultInput2" element="test1:MyComplexElement"></wsdl:part>
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput" type="test2:AnotherCompleType"></wsdl:part>
<wsdl:part name="DefaultOutput2" element="test1:MyComplexElement"></wsdl:part>
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

If the namespace of one <xsd:schema> section is imported inside another <xsd:schema> section of <wsdl:types> then all types, elements, attributes and groups of the first <xsd:schema> section as well as included types, elements, attributes and groups should be visible inside another <xsd:schema> section of<wsdl:types> but imported types inside first <xsd:schema> section should not be visible in the another <xsd:schema> section

Example

Sample.wsdl

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
targetNamespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd"
xmlns:test1="urn:ESBP_TO_WSDL/esbp/test1"
xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2">
<wsdl:types>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test1="urn:ESBP_TO_WSDL/esbp/test1">
<xsd:element name="MyComplexElement"
type="test1:MyComplexType"></xsd:element>
<xsd:complexType name="MyComplexType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema elementFormDefault="qualified"
targetNamespace="urn:ESBP_TO_WSDL/esbp/test2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:test2="urn:ESBP_TO_WSDL/esbp/test2"
xmlns:test1="urn:ESBP_TO_WSDL/esbp/test1">
<xsd:import namespace="urn:ESBP_TO_WSDL/esbp/test1"/>
<xsd:element name="MyElement" type="test1:MyComplexType" /><!-- This is valid since namespace ("urn:ESBP_TO_WSDL/esbp/test1") of another schema section is explicitly imported and hence visible over here -->
<xsd:complexType name="AnotherCompleType">
<xsd:sequence>
<xsd:element name="streetNum" type="xsd:int"/>
<xsd:element name="streetName" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Request">
<wsdl:part name="DefaultInput" type="test1:MyComplexType"></wsdl:part>
<wsdl:part name="DefaultInput2" element="test1:MyComplexElement"></wsdl:part>
</wsdl:message>
<wsdl:message name="Response">
<wsdl:part name="DefaultOutput" type="test2:AnotherCompleType"></wsdl:part>
<wsdl:part name="DefaultOutput2" element="test1:MyComplexElement"></wsdl:part>
</wsdl:message>
<wsdl:portType name="sample_wsdl_import_xsdPortType">
<wsdl:operation name="sample_wsdl_import_xsd">
<wsdl:input message="tns:Request"></wsdl:input>
<wsdl:output message="tns:Response"></wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="sample_wsdl_import_xsdSOAPBinding" type='tns:sample_wsdl_import_xsdPortType' >
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sample_wsdl_import_xsd">
<soap:operation soapAction="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd:sample_wsdl_import_xsdPortType:sample_wsdl_import_xsdRequest"/>
<wsdl:input>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body namespace="urn:ESBP_TO_WSDL/xsd/SampleWSDLS/sample_wsdl_import_xsd" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="sample_wsdl_import_xsdService">
<wsdl:port name="sample_wsdl_import_xsdPort" binding='tns:sample_wsdl_import_xsdSOAPBinding' >
<soap:address location="http://localhost:2580/process/sample_wsdl_import_xsd"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

References:
http://www.ws-i.org
Basic Profile Explained in Simple Words

FUSE Integration Designer 1.2.1 Released

2009-08-04T01:52:00.000-07:00

The first Service Pack release of FUSE Integration Designer is now out. Version 1.2.1 hit the stands last week with a host of fixes and some new features. Top of the list are some of the mentioned usability requests –

Support for drag and drop from the palette of the EIP editor – You no longer have to click on the element, before you can drop it, simply drag and drop like everywhere else. The GMF guys really need to add native support for this.
Carrying over of the project classpath for the EIP launch configuration – this one caused a lot of grief and hair-pulling since the release of 1.2. Here’s a forum query of the problem - http://fusesource.com/forums/thread.jspa?threadID=988
Improved performance of Run/Debug

Some of the new features introduced in this release –

New EIP Components – You can now choose from a wider range of components for use in the EIP editor. New endpoints in FUSE Integration Designer:

FTP/SFTP

XSLT

Timer

Trace EIP Executions at INFO level – Use the FUSE Mediation Router Tracer Interceptor to log EIP executions. You can view your tracer log in the Console view.

Messaging Improvements - Specify where the reply should be sent for a JMS Message by setting the JSMReplyTo destintation value. Take a look at an article on the JMS Tooling here.

Installing 1.2.1 is easy and completely hassle-free. If you are upgrading from version 1.2, read the installation notes for those few extra steps to be performed.

If you don’t already have FUSE Integration Designer – get the zip now and experience the awesome FUSE Runtime in FUSE Integration Designer 1.2.1.

What's new in FUSE Integration Designer 1.2

2009-05-27T10:37:00.000-07:00

A new version of FUSE Integration designer is released last week and there are some new exciting features. Here is a very broad overview of all (well, almost all :-)) new features available.

The latest FUSE Integration designer can be downloaded from http://www.fusesource.com/downloads

Also, now there is no need to install it using Eclipse update site (which is really painful if there are some dependency issues) – but you can still install through the update site esp if want to try FID on unsupported platforms like Mac OS X and 64 bit Ubuntu Linux – the usual disclaimer follows – these are not supported!

Integrated tooling: The new FUSE Integration designer now includes tooling for ActiveMQ and ServiceMix. And all the tools are integrated like deploying EIP projects on ServiceMix, using FUSE Messaging in running an EIP diagram. FID 1.2 is has now a professional (or enterprise :-)) look with new Splash screen, Welcome screen, FUSE perspectives, New File wizards and also some cheat sheets.

New Splash screen for FID 1.2:

Welcome Screen: First time you launch FID

New file menu:

EIP Tooling

EIP Editor: A completely new (and powerful) graphical editor for EIP patterns. Has a new auto connected layout so that you need not worry about the connections. EIP editor has now a completely different and much clearer theme – new colors, new selection highlight, new breakpoint visualization.

EIP editor now supports almost all patterns and processors Camel 1.5 has. The list is too long (check the screen shots). There are some new endpoints added to the tooling – CXF, JBI, SEDA and Mock.

Run/ Debug improvements: A new preference for Camel Runtime home folder – Run uses this Camel to run the EIP, start the route using FUSE message, and many bug fixes.

Java DSL: In the preview release of FID (1.1 and 1.0), there is virtually no support for Java DSL. In this release, there is new Java DSL project (even though there is no visual editor or support for enhanced debugging – this might come in future releases), DSL project is quite useful to get start with Java DSL and also you can deploy the Java DSL on FUSE ESB (ServiceMix). Tooling will take care of packaging, deploy and starting the Java DSL.
New Expression Editor: There is now a new Expression editor that supports all the languages (including Bean expressions) by Camel.

FUSE ESB tooling

WTP Server integration: ServiceMix server is now integrated with WTP Server's framework. Now, we can start, stop, restart, publish projects on ServiceMix server from a single view.

FUSE ESB tooling support both 3.x and 4.x versions. ServiceMix console is integrated with Eclipse Console view.

Supports deploying EIP project, Java DSL project and also CXF projects on both FUSE ESB 3.x and FUSE ESB 4.x versions.

Messaging tooling

Like FUSE ESB tooling, this is also a completely new tooling added in FID 1.2.

New Messaging project: Useful to store all the messages and sender and listeners in a single project.

Send and/or Listen to a Queue and/or Topic: Can send a message to a topic or queue in a local or remote ActiveMQ server. Also, we store the messages received.

Send different types of messages like XML message, Text message, Message with Headers.

Add or Remove JMS header properties using Message editor

Web Services Tooling

New Annotation view: Now it is very easy add JAX-WS annotations to Java file using Annotation view.

Multiple deployment options: A CXF project can now be deployed on Tomcat (3.x, 4.x, 5.x, 6.x) and also on FUSE ESB (ServiceMix) service.

With lot of new features and improvements to existing tools in the new FUSE Integration designer, I like you to take a look by downloading it from http://fusesource.com/.

JMS Tooling in FUSE 1.2 Release

2009-05-01T21:32:00.000-07:00

JMS Tooling in FUSE 1.2 Release

One of the new things in FUSE 1.2 release is JMS Tooling. This allows you to quickly connect to FUSE Messaging Broker, send and receive Text, XML messages on different JMS destinations in a user friendly manner. It is very handy when you want to diagnose/inspect if some things go wrong with your messaging applications.

There is no eclipse based tooling available around Eclipse currently. FUSE 1.2 takes the pride in providing this for the first time.

What is provided in JMS Tooling?

It follows entirely a new approach in providing a tooling for JMS embracing the common, standard and user-friendly approaches. It works as JMS Test Client, where-in you create JMS Message Producers, JMS Message Consumers and send/receive different kinds of messages.

List of Features:

Message Editor to compose JMS Messages

Compose JMS Message, JMS Text and XML messages
Set required JMS Headers
Set required JMS Properties

Messages Editor to visualize the received messages

Manage received messages – save, remove etc.,
Send a message to JMSReplyTo destination
Set a Message History count to purge the old messages automatically

Create your messaging application as Projects

Easy way to keep your messaging applications as separate project
Integrate with source control system to persist and reuse the projects
No tight coupling between the messaging project and the messaging broker
Ability to create projects in offline mode

Create your JMS Message Producers/Consumers

Support to create Queue/Topic/Durable Topic destinations as producers & consumers
Ability to set producer/consumer properties like Time To Live, Delivery Mode and Message Selectors etc.,

Create your connection to FUSE Messaging Broker

Servers view allows you to create connections to FUSE Messaging Broker.
Deploy your messaging applications in FUSE Messaging Broker Connections

"Try-It" - Trying your hands on JMS Tooling:

You can download FUSE 1.2 from http://fusesource.com/products/fuse-integration-designer/

Extract the zip file to desired location on your system.
Run fuse.exe from \fuse-integration-designer-1.2\bin\

In this “Try-It” session, we will do the following…

Choosing Messaging Perspective
Creating a FUSE Messaging Connection
Creating a Messaging Project
Creating Message Producers and Consumers
Creating test JMS messages
Sending Messages
Viewing Received Messages

Choosing Messaging Perspective:

By default FUSE 1.2 starts in “FUSE” perspective, click on Open Perspective icon on the top right hand corner of FUSE product and choose “Messaging”. This will bring up the Project Explorer View and the Servers View.

Creating a FUSE Messaging Connection:

Go to Servers View, launch context-menu of Servers View and Choose "New.." option, you will see the following dialog.

Enter a desired name (e.g. FUSE Message Broker) to the Server and click on Next button. Enter the connection details for FUSE Messaging Broker and click Finish.

This will create a node in the Server's View. Note that the FUSE Messaging Broker should be started from outside of FUSE. We will start & connect to the server later, so that we will see how to create Messaging Projects in offline mode.

Creating a Messaging Project:

This is what you create as an equilavent to your Messaging Application. As an example let us assume that we have a JMS based appliation say "TrainEnquirySystem" which responds to customers requests by providing the requested information. To test the health of this system, we want to send test messages and inspect the received messages.

Launch Project Creation wizard from File -> New -> Messaging
Enter desired name for the project say "TrainEnquirySystem"
The same wizard allows you to choose existing FUSE Messaging Connections or create a new Connection.
Select the connection we created in the previous section from the drop down list.
After finishing the wizard, the project gets deployed under the chosen connection (in this case FUSE Message Broker)
Under the project two nodes will be created with the names "Senders" & "Listeners"

Creating Message Producers/Consumers:

As mentioned earlier, you can create Queue/Topic as Producers and Queue/Topic/Durable Topic as Consumers.
To Create a message producer, select "Senders" node, on the right click menu options choose "Add Destination" action.
This action will launch the following dialog. Enter destination name as "queryByPNR" and click OK.

To Create a message consumer, select "Listeners" node, on the right click menu options choose "Add Destination" action.
This action will launch the following dialog. Enter destination name as "queryByPNR" and click OK.

You can later explore the context menu of the senders and listeners you created.

Creating test JMS messages:

Launch Message Wizard from File -> New -> Message
Enter a file name say "testInput_queryByPNR.message" and click on Next button
In the next page you can choose the message type - choose XML (FUSE Message Broker) type for this example
Note - Only JMS based messages can be sent over JMS destinations.
Enter the message content in the body section. OR you can directly point to the file which you want to be sent as JMS message.

Sending Messages:

If you try to drag and drop "testInput_queryByPNR.message" on "queryByPNR" under "Senders" node, it will show a warning message saying Connection is unavailable.
This is because we did not connect to the server yet. The project is just using an offline connection. If you observe the project shows a red flag and all the listeners show a red dot prompting the user that there is no active connection available.

Start your FUSE messaging Broker from outside.
To bring the project to online mode, go to Servers View, select "Fuse Message Broker" and choose Messaging -> Connect option to really connect to the server.
If you observe, the project shows a green flag and all consumers become active.
At this stage your project should look similar to the following screen

To send a message, just drag and drop the testInput_queryByPNR.message on "queryByPNR" under "Senders" node

Viewing Received Messages:

Double click on "queryByPNR" under "Listeners"
This will open a Messages Editor, the top section shows the list of all received messages and the bottom section shows the details of the selected message.
You can explore the tool bar options and try on your own.
The following screen shows the Messages Editor

Conclusion:

This post is just the introduction to the JMS Elicpse Tools in FUSE1.2, look forward to see advanced use-cases in future.

If you have trouble using this tool, please post in FUSE tools forum

What's new in FID 1.1

2009-01-05T21:52:00.000-08:00

FUSE Integration Designer (FID) is a graphical editor for Camel Spring XML files.
Current version of FID (1.0) can be download from FUSE Source
The next version FID 1.1 - which is yet to be released - has lot of new features, enhancements and bug fixes.

Here is brief outline of new features in FID 1.1

New Patterns added:

New Endpoints:

Jetty Component

FID is migrated to the latest Eclipse version (i.e, 3.4.1)
Improvements to launch configurations

Run/Debug configuration now has a new Classpath tab (see the screen shot below). Components that require external jars files like for example JMS component requires ActiveMQ libraries can be given here.

Importing Camel XML files

Import camel xml files is now integrated to Eclipse Import wizard. It is now possible to import Camel XML files that are not present in the workspace.

Support for Error handling

A new tab called "Advanced Properties" is added to all Patterns and user can provide the error handler bean ref in that tab. For more information about Error Handling have a look at Camel documentation

However this is not a complete list - lot of bug fixes, minor enhancements - check the complete list of bugs fixed in 1.1 at http://fusesource.com/issues/secure/Dashboard.jspa

Classpath Tab in Launch configuration:

Error Handler Ref for patterns

Screenshot of FID editor

Welcome to FUSE Tools

2008-12-31T07:26:00.000-08:00

An unoffical blog about FUSE tools.