Brad Davis wrote:
Precisely my point. localhost is really irrelevant; the point is, the SoapProxy should not freeze a deployment, no matter if the service lies on the same server or a different server.
If it's in the same VM, use internal://. If it's on another server, use http:// or https://. If you don't want to be dependent on the availability of the other server, use file:// or classpath://. What's the problem here?