uly 2004 15:32
> To: [EMAIL PROTECTED]; 'Anand Natrajan'
> Subject: RE: WSDD and WSDL
>
>
> That's a big help! Thanks!
> Just one other thing, if I have a more complicated java class
> that I wish to deploy as a web service, does that mean I use
> a
From: Anand Natrajan [mailto:[EMAIL PROTECTED]
> Sent: 29 July 2004 15:23
> To: [EMAIL PROTECTED]
> Subject: Re: WSDD and WSDL
>
> Suzy,
>
> WSDDs are Axis artifacts - they're present just to tell Axis what
> service
> you intend deploying. Subsequent to deploying a WSDD
Hi,
you need WSDL for generating skelotons and stubs as well as publishing
your service detail.(for a simple case).
Once you have generated your skelotons and stubs,you don't really need wsdl.
You need to deploy your service detail. Then only axis engine will be able
to invoke your webservice.
Th
t: 29 July 2004 15:23
To: [EMAIL PROTECTED]
Subject: Re: WSDD and WSDL
Suzy,
WSDDs are Axis artifacts - they're present just to tell Axis what
service
you intend deploying. Subsequent to deploying a WSDD you have a web
service
(running inside Axis), and can get to the service's WSDL.
JWS
Suzy,
WSDDs are Axis artifacts - they're present just to tell Axis what service
you intend deploying. Subsequent to deploying a WSDD you have a web service
(running inside Axis), and can get to the service's WSDL.
JWS files also are Axis artifacts, I believe (this one I not so sure about).
If you
I’m just looking for
clarity as to exactly how the web service deployment descriptor works. How is it interrelated with wsdl in axis?
Do I still create the WSDL by deploying a jws file? Once tested using the AdminClient
class in axis how is processed from there?
Any help would be great
This is my wsdd file
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";
xmlns:ns1="AutoUploaderService" >
AutoUploaderService
languageSpecificType="java:javax.activati
