Since you are most likely using SOAP over HTTP, you have the same tools used
to protect other HTTP services -- you can require client certificates,
restrict to certain IPs, use HTTP basic authentication, etc., which can all
be set up using your web application server. But these are probably usef
mplex - probably more buggy, too.
On Mon, 2003-01-27 at 14:24, Benjamin Tomasini wrote:
> I would just modifiy the server-config.wsdd manually. Same effect.
>
> On Mon, 2003-01-27 at 14:26, James Flagg wrote:
> >
> > Greetings all,
> >
> > According to the Axi
Greetings all,
According to the Axis documentation, the way to deploy web services using
WSDD is to invoke the AdminClient from the command line:
% java org.apache.axis.client.AdminClient deploy.wsdd
which connects to the Axis servlet on localhost:8080 and registers the
service.
However, I hav
Hi Cory,
I think that Keith is right. If you run ant with the "-verbose" flag, it
will show you more information about the exception being thrown, and you
will probably see that it can't load Wsdl2javaAntTask because it can't load
a class that Wsdl2javaAntTask requires. At least that's what I e
Greetings all,
I have just started using Axis and I'm having a problem with the WSDL2Java
tool. It always gives me a deploy.wsdd file containing only an empty
tag. Here's the steps I take.
1. Generate the WSDL file from an existing Java interface, using Java2WSDL.
There are no errors, and the
