ok, one thing I am still unsure about, and that is : is server-config.wsdd
mandatory. I always thought you could get by without it, but now I dont
think so.

tell me whether is needed or not and I will change the JSP file to match the
spec

----- Original Message -----
From: "Tom Jordahl" <[EMAIL PROTECTED]>
To: "'axis-dev'" <[EMAIL PROTECTED]>
Sent: Friday, June 21, 2002 7:58 AM
Subject: RE: [SUBMIT] configuration test JSP


>
> +1 for Beta 3.
>
> --
> Tom Jordahl
>
>
> -----Original Message-----
> From: Steve Loughran [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 20, 2002 7:48 PM
> To: axis-user; axis-dev
> Subject: [SUBMIT] configuration test JSP
>
>
> Right, here is an iteration of the happy axis jsp that looks at the system
> and probes for various classes and prints out helpful messages pointing
> readers at download urls.
>
> Mandatory JARS: axis, jaxrpc, saaj.
> Optional JARs: activation, mail
> Optional resources: server-config.wsdd
> (optional cos you may be about to run the admin client against the server)
>
> if anything we need is missing, the response is a 500 error, that
something
> like http unit or ant's <get>, <waitfor><url> and <condition><url> tasks
> will pick up. so you can use it during an automated deploy and test
process;
> verifying that stuff is there before you run the more complex tests.
>
> To use: drop into your axis webapp, or any other webapp that uses the Axis
> libraries. Point browser at it. read response.
>
> Feature creep: customise install hints based on server identity, probe for
> more things, like xml signing.
>
> I want to add this to beta-3 with some docs unless anyone has any major
> objections. Given the #of emails on getting axis to work with tomcat, I
hope
> nobody will veto the idea.
>
> -Steve
>

Reply via email to