Hello Anne, Op zondag 17-02-2008 om 14:20 uur [tijdzone -0500], schreef Anne Thomas Manes: > Do you have a WSDL that goes with the service? You can use WSDL2java > to generate a client proxy for you. That will make things easier for > you.
Yes. In the mean time I have generated a client proxy. I have narrowed down my problem to the following: the (.NET) web service returns a custom SOAP header called 'TicketHeader' which it expects to be returned to it, as a SOAP header, on subsequent client requests. It appears that proxy classes generated on .NET retain this custom header automatically whereas Axis-generated proxy classes do not. My first approach to solve this was to try and get the SOAP request message from the call's messagecontext in the proxy classes, in order to insert the header manually. However, I found out that the request message is generated only after the call is invoked. So, my second approach was to register a custom handler on the client side that inserts the TicketHeader header upon invoke(). Unfortunately, although I can verify that I added my custom handler to the handler chain in the service's handler registry by calling super.service.getHandlerRegistry().getHandlerChain(), it is never invoked. I wonder what what be the cause for this. Any suggestions on how to debug it? regards, -- Reinout van Schouwen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
