Forum Discussion
redfish4ktc2
13 years agoSuper Contributor
ok, it seems the code has been modified between soapui 3.6.1 and 4.0.0
I think i you pass through this portion of code at runtime, it is because the xsd has not been found previously (see the for loop with the return just before the 2 if File.separator conditions). The last 2 ifs are a final attempts to access to the file from the HD when the defined path uses wrong file separator (for example, the projet uses windows separator and you have imported it on linux)
I suspect the following happen: in your wsdl files used during import in soapui, xsd are referenced with absolute path (not relative) so they can not be resolved at 1st attempt (the for loop), then try with the file separator substitution and generate a wrong path to the xsd
A user report me that this could be an issue when using that kind of configuration with the mock as war feature (ie servlet runner), see https://github.com/redfish4ktc/maven-so ... t-16164542
Can you check your wsdl please and tell me if you are in this situation?
I think i you pass through this portion of code at runtime, it is because the xsd has not been found previously (see the for loop with the return just before the 2 if File.separator conditions). The last 2 ifs are a final attempts to access to the file from the HD when the defined path uses wrong file separator (for example, the projet uses windows separator and you have imported it on linux)
I suspect the following happen: in your wsdl files used during import in soapui, xsd are referenced with absolute path (not relative) so they can not be resolved at 1st attempt (the for loop), then try with the file separator substitution and generate a wrong path to the xsd
A user report me that this could be an issue when using that kind of configuration with the mock as war feature (ie servlet runner), see https://github.com/redfish4ktc/maven-so ... t-16164542
Can you check your wsdl please and tell me if you are in this situation?