Dan,
Here are also simple questions, not particularly aimed at you:
Why would your service be responsible for what the subscriber does to handle the responses? If the interface is fully specified by the wsdl then the client will be able to consume it.
What, specifically, are you doing that you need to concern yourself with client-side handlers?
I'm not being a smartie here. I see a lot of posts similar to yours and I wonder why:
1) the provider wants to be responsible for the subscriber - frankly I'd love it if our enterprise IT even *thought* about providing usable client code. I will absolutely settle for a wsdl which doesn't make me hand-code parsers for every string-wrapped xml document.
2) so many services don't seem to be designed as services - it's as if the cart is driving the horse, as in "we already have the application/interfaces/classes that we'd like to expose as a web service" . . .
3) SOAP is decided as the solution when the problem hasn't been analyzed
Elaine
Dan O'Neill wrote:
I'm tired trying to get them to work. Do Client-side service-specific handlers work? If you put them in client-config.wsdd? I know that if I change them to global they work?
I've got some working by using setClientHandlers() in the client code but I don't always have the luxury of changing people's java client?
<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
