Re: WSDL - Missing something obvious w/ Header

[Sathya Sankar]

Not sure why the generated WSDL is inconsistant but as a workaround you can

add a "<wsdlFile>" tag to the WSDD and point to your WSDL. I usually do that to

let my clients see the WSDL I coded, instead of an Axis generated one.

TMG <[EMAIL PROTECTED]> wrote:

I would like to add a header to several of my services to require some
simple authorization (using CVS tree of Axis 1.2RC2).

An example of one of the service's wsdl binding is a follows:


transport="http://schemas.xmlsoap.org/soap/http"/>

style="document"/>

use="literal" />








When using wsdl2java to generate the server and/or client stubs the
deploy.wsdd has the correct type mapping for the authorization message
and the __BindingStub.java has the serialization/deserialization
methods, but the PROBLEM is that there is no header listed when the wsdl
is queried on the deployed service (e.g.
http://my.com/context/services/myservice?wsdl ). Thus, there is no way
for the client (consumer of service) to know that they need to create
and pass a header. That is, the wsdl returned shows the binding listed
above, sans the header on the .

I must be missing something obvious!

Thanks,

Tom Gordon

---

Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.