How to use a custom property to define a mock service's listening port?
We are developing an application that is pretty connected, i.e. it communicates with about a dozen of surrounding services via SOAP requests. During testing these services are mocked, i.e. we defined about a dozen of mock services in a "mocks-soapui-project.xml".
These mocks can all run on the same system and even the same port, but in different environments they should be able to listen on DIFFERENT port numbers. I would thus like to use a custom property, say "MockPort", to specify the Port-field in the SOAP MockService Options-dialogue. However, that doesn't seem to be possible. Entering something like ${#Project#MockPort} in said configuration field is ignored, i.e. after clicking OK the former port number is displayed again.
Is there any way or trick to use placeholders in the SOAP MockService Options dialogue? Or how could one change the listening port of multiple mocks in one go?
In that context I have another question: what is the priority between an items default properties and its custom properties? I tried to define a Custom Property "Port" in the MockService Properties in an attempt to overrule the default property with the same name but obviously that does not work as I had hoped. Is maybe such a "property overwriting" possible somehow?