Sathya,
Thank you for the info ... although it didn't solve the problem, it was good to know about that option ;).
I spent some time with the archives today and found some things that lead me to the right answer.
The bindings were fine, the problem was that I didn't include the header as a "part" in my message. What I had incorrectly done instead, was create a separate message for the header. That works with other wsdl parsers, but not Axis 1.2.
So to complete the thread for anybody else who has this problem, to get headers to show up in the wsdl (e.g. http://<service>?wsdl ), you have to do two things:
1.) Create a message with two parts, one the header the other the body.
<wsdl:message name="setACLInput">
<wsdl:part name="auth" element="auth:authInfo"/>
<wsdl:part name="parameters" element="xsd:string"/>
</wsdl:message>
2.) Allocate the parts in the binding's input method (as in previous e-mail)
<wsdl:binding name="AccessControlSoapBinding" type="impl:AccessControl">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="setACL">
<wsdlsoap:operation soapAction="urn:my:com:wsdl/setACL" style="document"/>
<wsdl:input>
<wsdlsoap:header message="impl:setACLInput" part="auth" use="literal" />
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
Tom Gordon
Sathya Sankar wrote:
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:
snip...
