Resolution of the validation error when a schema specifies multiple imports with different schemaLocation and same namespace

Cause

To see how to reproduce this problem, you can proceed as follows:

1. Create a new Simple Project
2. Create two XML Schemas with the same target namespace, but defining different elements, as in the following examples:
   
   Address.xsd
   <?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"    targetNamespace="http://www.example.org/common" xmlns:tns="http://www.example.org/common">
<element name="Address" type="string"></element>
</schema>
   
   Customer.xsd
   <?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org/common" xmlns:tns="http://www.example.org/common">
<element name="CustomerName" type="string"></element></schema>

3. Create a third schema having a different target namespace, and importing the previous two schemas, as in the following example:
   
   Order.xsd
   <?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org/Order" xmlns:tns="http://www.example.org/Order" xmlns:pref="http://www.example.org/common">
<import namespace="http://www.example.org/common" schemaLocation="Address.xsd"></import>
<import namespace="http://www.example.org/common" schemaLocation="Customer.xsd"></import>
<element name="Order"><complexType>
<sequence><element ref="pref:CustomerName"></element><element ref="pref:Address"></element></sequence></complexType></element></schema>

4. Validate the third schema, Order.xsd, and you will get the error:
   src-resolve: Cannot resolve the name 'pref:CustomerName' to a(n) 'element declaration' component.
   
   By extension, any WSDL referring this type of XML Schema is invalid. This defect is tracked as RATLC00475388