You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Suzy Fynes <su...@sentenial.ie> on 2004/07/29 15:19:30 UTC
WSDD and WSDL
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!
Thanks,
Suzy
RE: WSDD and WSDL
Posted by Chandrasegaram Jeyakumaran <jk...@opensource.lk>.
Hi,
Sorry I didn't really see the replies for this mail. That's why my reply
came.
Ok if you have a complexed java class then what would be the easy way?
I can suggest what I am doing with this.(I don't know whether it is the
right method. But I used to do this)
1)generate the wsdl for your complexed class.(Java2WSDL)
2)Then using that wsdl generate the skelotons.(WSDL2Java)
3)Ok then there will be a service impl class. Fill the logics of your
methods there.
4)Then fine you won't have any headaches. Deploy the service using
adminclient.
Everything will be fine.:)
regards,
Jeyakumaran
> 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 wsdd file to
> deploy it?If so where does the wsdl come from?
>
> -----Original Message-----
> From: Anand Natrajan [mailto:an4m@cs.virginia.edu]
> Sent: 29 July 2004 15:23
> To: axis-user@ws.apache.org
> 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 files also are Axis artifacts, I believe (this one I not so sure
> about).
> If you have really simple webservices, then you can get around the long
> process (write a java interface, java2wsdl it to get a WSDL, wsdl2java
> the
> WSDL to get server skeletons and a WSDD file) and simply deploy the JWS
> file
> instead. It's a quickie web service straight from your Java code.
> Doesn't
> work for complex types though. Again, once you have deployed a JWS file,
> you
> have a web service (again running inside Axis), and you can get to the
> service's WSDL.
>
> As a radically different example, if you were in the .NET world and
> wanted
> to deploy a service inside IIS, you wouldn't have WSDDs and JWS files.
> Instead, you'd write a C#/J#/VB/VC++ class, tag the class as a
> WebService,
> tag some methods as WebMethods and then turn on the .NET blender. At the
> end
> of it, you'd get a deployable executable. Running that simply installs
> your
> web service (running inside IIS this time). After that, consult your
> friendly IIS manual to figure out how to get the WSDL for the service.
>
> Hope that made a few things clearer.
>
> Anand
>
> On Thu, 29 Jul 2004, Suzy Fynes wrote:
>
> : 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!
> : Thanks,
> : Suzy
>
>
>
>
Lanka Software Foundation
Promoting opensource in Srilanka
RE: WSDD and WSDL
Posted by Suzy Fynes <su...@sentenial.ie>.
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 wsdd file to
deploy it?If so where does the wsdl come from?
-----Original Message-----
From: Anand Natrajan [mailto:an4m@cs.virginia.edu]
Sent: 29 July 2004 15:23
To: axis-user@ws.apache.org
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 files also are Axis artifacts, I believe (this one I not so sure
about).
If you have really simple webservices, then you can get around the long
process (write a java interface, java2wsdl it to get a WSDL, wsdl2java
the
WSDL to get server skeletons and a WSDD file) and simply deploy the JWS
file
instead. It's a quickie web service straight from your Java code.
Doesn't
work for complex types though. Again, once you have deployed a JWS file,
you
have a web service (again running inside Axis), and you can get to the
service's WSDL.
As a radically different example, if you were in the .NET world and
wanted
to deploy a service inside IIS, you wouldn't have WSDDs and JWS files.
Instead, you'd write a C#/J#/VB/VC++ class, tag the class as a
WebService,
tag some methods as WebMethods and then turn on the .NET blender. At the
end
of it, you'd get a deployable executable. Running that simply installs
your
web service (running inside IIS this time). After that, consult your
friendly IIS manual to figure out how to get the WSDL for the service.
Hope that made a few things clearer.
Anand
On Thu, 29 Jul 2004, Suzy Fynes wrote:
: 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!
: Thanks,
: Suzy
Re: WSDD and WSDL
Posted by Anand Natrajan <an...@cs.virginia.edu>.
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 have really simple webservices, then you can get around the long
process (write a java interface, java2wsdl it to get a WSDL, wsdl2java the
WSDL to get server skeletons and a WSDD file) and simply deploy the JWS file
instead. It's a quickie web service straight from your Java code. Doesn't
work for complex types though. Again, once you have deployed a JWS file, you
have a web service (again running inside Axis), and you can get to the
service's WSDL.
As a radically different example, if you were in the .NET world and wanted
to deploy a service inside IIS, you wouldn't have WSDDs and JWS files.
Instead, you'd write a C#/J#/VB/VC++ class, tag the class as a WebService,
tag some methods as WebMethods and then turn on the .NET blender. At the end
of it, you'd get a deployable executable. Running that simply installs your
web service (running inside IIS this time). After that, consult your
friendly IIS manual to figure out how to get the WSDL for the service.
Hope that made a few things clearer.
Anand
On Thu, 29 Jul 2004, Suzy Fynes wrote:
: 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!
: Thanks,
: Suzy
Re: WSDD and WSDL
Posted by Chandrasegaram Jeyakumaran <jk...@opensource.lk>.
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.
That deployment is done in the wsdd file.
Here wsdl plays no role with this.
For jws it is an instant deployment.
I think it is better to have a look at axis userguide which explains these
stuffs in detail.
regards,
Jeyakumaran
> 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!
> Thanks,
> Suzy
>
Lanka Software Foundation
Promoting opensource in Srilanka