<definitions ... >
<binding ... >
<operation ... >
<input>
<soap:body... />
<soap:header message=...Referenz-auf-message-Element...
part=...Referenz-auf-part-Element...
use="literal|encoded"
encodingStyle="uri-list"
namespace="uri">
<soap:headerfault message=...?...
part=...?...
use="literal|encoded"
encodingStyle="uri-list"
namespace="uri">
<\soap:header>
<\input>
<output>
<soap:body... />
<soap:header message=...Referenz-auf-message-Element...
part=...Referenz-auf-part-Element...
use="literal|encoded"
encodingStyle="uri-list"
namespace="uri">
<soap:headerfault message=...Referenz-auf-message-Element...
part=...Referenz-auf-part-Element...
use="literal|encoded"
encodingStyle="uri-list"
namespace="uri">
<\soap:header>
<\output>
</operation>
...
</binding>
</definitions>
BTW: we couldn't figure out how AXIS reacts to this definition !
and 2.:
Yes you are right, thats the way how to do this.
Regards
Oliver
Von: Drooker, Matthew [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 14. Februar 2003 23:07
An: '[EMAIL PROTECTED]'
Betreff: SoapHeaders Help
Hello-
Got a quick question that's been killing us over here...
So here it is-
We plan on using SoapHeaders to enable some token exchanges to implement a custom security pattern. We have .NET client, Java clients, and old school VB6 clients. But on the server, Axis was to be the server component.
1. We need to figure out how to tell Axis that I want to inject a SoapHeader (tag)requirement in the WSDL. The SoapHeader element will be a complex type of some "token holder information". I know Axis1.1 has this support, but I cannot find any examples on how to get this functionality working. Is anyone out there doing this type of operation.
2. We will need to slurp out the SoapHeader before executing the target function. I'm pretty sure that will be with a custom Handler...But if anyone can confirm that would be cool.
Any help would be great-
Matthew
