Hi!
Although I do spontaneously agree with brr7907 that using soapUI for this might be overkill, the way to do it would be as follows:
1) Change your internal app to listen on another port/ip etc..
2) Set up a SOAP Monitor for your WSDL in soapUI, configure it as tcptunnel and set target to the new port/ip of the app and make sure that the SOAP Monitor is running on the public available port/ip (ie the one that your clients use)
-> In this setup soapUI should work as a "pass-through" receiving/forwarding requests/responses to/from your previous service. Make sure that it is before moving on :-)
3) To modify the response "on its way through" soapUI, you will have to use the "MonitorListener.afterProxy" event handler possibility (see
http://www.soapui.org/userguide/project ... dlers.html) to modify the data returned to the client (I'm preparing a blog-post on this, stay tuned)
Hope this helps!
regards,
/Ole
eviware.com
