Problem with path of xsds on linux

hi,

the code displayed on soapui xref is really not up to date whereas it is supposed to be the code of the last version, see the class header which is 'soapUI, copyright (C) 2004-2010 eviware.com'

The current code for the class you mentioned can be seen here: https://github.com/SmartBear/soapui/blo ... oader.java

What soapui version are you using?

Hi,

Thanks for the quick response.

I know that it's old, the other one I mentioned looks the same as that of github, which is the most recent and for some reason it replaces the '/' with '\\'

I have the version 4.5.2 which replaces the '/' with '//' as it is shown in the github version. I found the other one from 2010 and thought that it has been changed by mistake in the last version, resulting in changing the paths with '/' to paths with '\', which is my current issue if you see the log messaage I posted.

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?

hi again,
i search on the forum and found the following posts related to your problem. Smartbear Support seems to state that if the wsdl definition is cached, you shouldn't have the issue but I am not sure it really works with the mock as war feature (they are all related to the mock runner)
* viewtopic.php?f=2&t=2549 (with SmartBear answer)
* viewtopic.php?f=5&t=2075
* viewtopic.php?f=4&t=11371
* viewtopic.php?f=5&t=13613
* viewtopic.php?f=13&t=8433

I used instructions from https://github.com/redfish4ktc/maven-so ... kAsWarGoal to generate wars. Originally SoapUI was used in Windows, so project file contained C:\... references.

When mocks generated with that are put to Tomcat in Ubuntu, it writes errors and paths with C:\... in catalina.out, but still works fine.

hifist could you provide the tomcat logs please and your soapui project please (if it does not contains sensible data)?
I need this to reproduce the problem