Tim Moores wrote:I don't think you'll find much about this, as it is a very specialized topic. Studying the source code of a tool that does it (like SOAPUI, IIRC) might help. Or maybe you can even reuse some of its code, depending on licensing issues.
Tim Moores wrote:I don't think you're using the word "proxy" correctly; I don't see where one would be involved here.
So what you actually want to do is to enter the URL of a WSDL, and then access methods defined in that WSDL without any prior knowledge of what's in the WSDL? I think SOAPUI can do that.
Tim Moores wrote:Now I'm confused. What does a proxy have to do with a WS invocation? Should the client access the WS through a proxy? Or what kind of proxy is this?
Tim Moores wrote:What is a "client web service" - are you writing a client for an existing WS? Or are you writing a WS that accesses some other WS that is designated by the WSDL info you're passing to the first WS? TellTheDetails