I am confused ......the wsdl is not something that can be changed it is based on the machine name wehere the program runs and the port that is being used (i.e. http://machinename:portnumber/soap/services/processname?wsdl). When you move the orchestration from one machine to another (dev to test to production) it is the machine name or port that changes. the rets of the wsdl stays exactly the same. So it is up to the program making the call to the web service to adjust and call the one in dev or test or production. In most of the environments that I have seen the call to the WS is being done from a form. The form is programmed in such a way that the wsdl is built on the fly and the appropriate calls are made (based on whether the user wants to acces dev, test or production).
You are correct. Only the machine name changes, the rest of the service name remains the same as we move between env DEV, TEST, etc.
In our implementation, we are not calling webservices from the form but instead have a watched folder where all pdfs are dropped. The pdfs have xsd mapped to them. The workbench process applies a XSLT and calls the corresponding web service.
I also reposted in the Workbench forum and jasmin has suggested using the WebServiceSettingBean variable which I am trying to get working.
As per jasmin's post on the workbench forum the problem has been resolved.
Under the Web Service Options change the 'Option' to use 'variable' instead of 'literal'. Then click on the green + and it'll create a variable of type WebServiceSettingBean.
You can use a setValue before the web service step to configure that variable properly.
Wouldn't you have a different watch folder for each of those environments?