[CXF-8655] Incorrect XSD resolution when the file name is the same in different folders

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0, 3.3.12, 3.4.5
• Fix Version/s: 3.5.2, 3.4.7, 4.0.0
• Component/s: Simple Frontend
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Ricardo Martin
• Created: 08/Feb/22 15:56
• Updated: 18/Sep/23 18:48
• Resolved: 16/Mar/22 16:27

Description

The attached gradle project contains a WSDL file which imports a XSD and it, in turn, imports another two XSD files with the same name but located in different directories. It triggers incorrect resolution of the XSD files. The structure is the following:

1) MyWebservice.wsdl
   1.1) imports schema/MyWebservice.xsd -> schema/MyWebservice.xsd
        1.1.1) imports ../../../common/common.xsd -> ../../common/common.xsd
        1.1.2) imports ../../common/common.xsd -> ../common/common.xsd
               1.1.2.1) imports ../../common/common.xsd -> ../../common/common.xsd

The resulting imports are:

1) http://localhost:8080/wsdl-test/MyWebservice?wsdl (OK)
   1.1) http://localhost:8080/wsdl-test/MyWebservice?xsd=schema/MyWebservice.xsd (OK)
        1.1.1) http://localhost:8080/wsdl-test/MyWebservice?xsd=../../common/common.xsd (KO)
        1.1.2) http://localhost:8080/wsdl-test/MyWebservice?xsd=../common/common.xsd (OK)
               1.1.2.1) http://localhost:8080/wsdl-test/MyWebservice?xsd=../../common/common.xsd (KO)

   
The URL http://localhost:8080/wsdl-test/MyWebservice?xsd=../../common/common.xsd in 1.1.1 returns invalid content. The content is the file in 1.1.2 (not 1.1.1) and besides the contained import is not rewritten in its location.
 

Steps To reproduce:

• Download attached maven project.

  unzip wsdl-test.zip
  cd wsdl-test/
  mvn clean package
  mvn jetty:run
  

• Go to the wsdl http://localhost:8080/wsdl-test/MyWebservice?wsdl and follow imports until http://localhost:8080/wsdl-test/MyWebservice?xsd=../../common/common.xsd and check the received output is incorrect.
• You can also execute the client while the jetty is running with:

  mvn exec:java
  

Issue Links

• links to: GitHub Pull Request #904