ler issues a fault if the
> user and password are not in the context, and Axis issues a 401 to the
> client.
>
> On 4/28/06, *Kevin O'Rourke* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Thanks for the information. Just to be sure I unde
efined as:
>
>
>
> type="java:org.apache.axis.handlers.http.HTTPAuthHandler"/>
>
>
> And each service has a request flow of:
>
>
>
>
>
>
> On 4/27/06, *Kevin O'Rourke* <[EMAIL PROTECTE
I'm trying to do authentication for my Axis web service using HTTP/Basic
over SSL, as this seemed to be the easiest option. The client is
written in Visual Basic .Net 2005.
I've added the HTTPAuthHandler to my WSDD file:
...
...
However no authentication is happ
Thanks for the information.
Anne Thomas Manes wrote:
> .NET doesn't support RPC/Literal (although Indigo will). For best
> interoperability with .NET, you want to use "wrapped" document/literal.
> (From a programming perspective, WRAPPED is pretty much identical to RPC
> style).
>
> In java2wsdl,
s.xmlsoap.org/soap/http"; />
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> HTH, James.
>
> -Original Message-
> Fro
Hi,
I'm writing a web service with Axis and am starting to get somewhere.
The service will have to interoperate with .Net (specifically VB.Net),
so I want to stick to WS-I Basic, which means I can't use RPC/Encoded.
In fact some of the Microsoft tools complain if they come across any
'use="encode
