Alex,
Try the latest nightly build, which has support for explicit headers in WSDL. They are added to the stub function call signature. There is ongoing work being discussed on the stub/call relationship and one of the hopes is to get a stub.addHeader() type of API, which is currently not possible with the way the stub and Call objects are done. -- Tom Jordahl Macromedia -----Original Message----- From: Alex Huang [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 2:11 PM To: [EMAIL PROTECTED] Subject: Soap header support with generated stubs... Hi all, I've been waiting anxiously for the release 1 of axis, hoping that it will bring soap header support in the generated client stubs. But I couldn't find any such support in release 1. Is there any plans for supporting this? Did I miss anything? I've already written the server so that it can parse out the soap header itself. That was fairly easy. The problem is on the client side. I want to be able to give the wsdl file, axis, and the generated stubs to my clients and let them make a call much like a method call, instead of having to package up the call themselves. I've even got so far as to write a class that the client can call to add arguments and generate a soap header. All I need is a way to add that to the stubs class and say use this header. Something like call.addHeader() in the generated stubs would be enough but I can't find anything like that. I even tried to add that method manually to the stubs that wsdl-to-java generated but for some reason the soap message that is actually sent is still missing the soap header. I know axis is released now but, for my work, I can't release if one day I have to go back to my clients and say "you don't package the call now, just use the stubs generated by axis." And packaging up the call is just very tedious for the client. They end up learning a lot more about soap and axis than I want them to. Any help here? Thanks in advance for any info, suggestions, dates for completion that you can provide. --Alex
