I am having the same problem. Is there a solution for this yet? Or a workaround... perhaps I can manually edit the project file to replace absolute paths with ${projectDir} or something?
Some more details: I have created a SOAPUI project and mock service on a Windows development machine. The mock service supports the unit tests which are successfully run by several different developers (using SOAPUI standalone, SOAPUI plugin for Eclipse, and Maven SOAPUI plugin) with different folder structures on windows. The fact that the absolute paths to the XSDs embedded in the project file are only correct for my development machine and wrong for all the other developers doesn't seem to be an issue when running the mock service (it does seem to be an issue when updating the project definition).
I need to run the same mock service on our linux DEV box until the real web services are available. It seems that the mock service runner is trying to resolve the location of the xsd files when it starts up and is unable to do so on linux. I'm not sure why this is even necessary, because the entire contents of the XSDs is already embedded inside the project file. In any case, this problem is a show-stopper and prevents the mock service runner from functioning.
As it stands now, the choices seem to be:
1. Consolidate all XSDs into the WSDL file (undesireable because of the extra work and configuration management challenges it creates)
2. Don't use mock service runner
