Hello All,
I have a specification that demands I use a SOAP Header element for credential verification, and from a technical perspective it needs to be highly reusable, with a technical requirement that it preceeds and stops processing of the SOAP Body. I've found what seems to be just the ticket, which is simply adding a component via the <requestFlow/> element in WSDL or WSDD...But the problem I'm having is that I'm having difficulty finding documentation on doing this.
Essentially, I have the following (mock) request envelope:
<Envelope xmlns="?soap">
<Header>
<authenticate username="..." password="..."/>
</Header>
<Body>
<purchase>
<order accountid=".." cardid=".." amount=".."/>
<order accountid=".." cardid=".." amount=".."/>
</purchase>
</Body>
</Envelope>
Nevermind the details of the SOAP Body, handlers for this are easily generatable by WSDL2Java, but how do I deal with the SOAP Header in a respectible and logical fasion (Axis
1.3) ?
Thanks,
Scott S. McCoy
- Arbitrary Authenitcation Types (based on SOAP Headers) Scott McCoy
- Re: Arbitrary Authenitcation Types (based on SOAP He... Scott McCoy
- RE: Arbitrary Authenitcation Types (based on SOAP He... Rave, Mark
- Re: Arbitrary Authenitcation Types (based on SOA... Scott McCoy
- Re: Arbitrary Authenitcation Types (based on... Rodrigo Ruiz
- Re: Arbitrary Authenitcation Types (base... Scott McCoy
- Re: Arbitrary Authenitcation Types ... Davanum Srinivas
