Forum Discussion
OK, in that case it looks like normal behavior then - it just looks like some files aren't in the same place on your new machine.
By default SoapUI uses an absolute path for everything - so, if your SoapUI workspace knows about a project file at C:\Users\QuickBooksDev\myproject.xml on one machine, then if you open the same workspace on another machine, it needs to be in the exact same place on that machine (which it might not be e.g. if you have a different username).
You can change this behavior by opening the workspace on your source machine, and at the workspace level (at the top of the tree - yours is called "Projects"), change the Project Root property to ${workspaceDir} then save and exit. This will make paths to project files relative, so if the workspace and the project are in the same folder on the source machine, or if the projects are in subfolders from where the workspace is, then you should be able to copy that folder to another machine and open it in tact.
The same applies at the project level, when projects save paths to their related files (such as WSDLs, keystores etc). So, you can make the same change on all of your projects using ${projectDir}. Alternatively, you can just go ahead and import the projects as they are, and SoapUI will show a dialog box that lets you browse to find the new location of the files.
Related Content
- 2 years ago
- 2 years ago
Recent Discussions
- 15 years ago