You guys are losing me. A developer has to know that a GET is being performed, the same way they have to know that any method is being invoked, because it has meaning specific to the task they're trying to accomplish.
Sam's suggestion to punt the retrieval of the response is fine from this POV, but I wonder what developers would think of it, and I'm not sure it would technically be conformant to the spec (though maybe the spec needs fixing). Glen's getSOAPResponse() method is confusing to me, because there already exists a way to invoke methods on objects, setOperationName(). Why would having two ways of doing the same thing be desirable? And if you're going to create a different way, why not reuse an existing one, like java.net.URLConnection.getContent() (modulo those awful java.net HTTP issues)? I understand that this a very different way of thinking of SOAP, i.e. not as a layer, but that's what the Web Method feature is for; exposing HTTP, through SOAP, to the developer. MB -- Mark Baker, CTO, Idokorro Mobile (formerly Planetfred) Ottawa, Ontario, CANADA. [EMAIL PROTECTED] http://www.markbaker.ca http://www.idokorro.com
