axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott McCoy <...@cpan.org>
Subject Re: Arbitrary Authenitcation Types (based on SOAP Headers)
Date Fri, 10 Feb 2006 19:06:06 GMT
I didn't get a response to this, so I thought I'd re-post it.

I just want a handler, before my handler, to get some values from the header
and have the ability to stop the request.

How does that happen?

On 2/8/06, Scott McCoy <tag@cpan.org> wrote:
>
> 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
>

Mime
View raw message