Like CORBA, skeletons are server-side only.  Hence the client code will never use a skeleton.
 
In Axis, the skeleton classes are removed recently and the <name>Impl class is called directly.  This depends on whether you are using the beta-1 build or building from the latest CVS snapshot.
 
Charles
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 08, 2002 12:03 PM
To: [EMAIL PROTECTED]
Subject: Does a stub always need a skeleton ?

I'm wondering if it is possible to deploy my service the usual way (as explained in chapter "Publishing Web Services with Axis") and then use the automatically generated wsdl file to let the wsdl2java tool generate the client-side bindings necessary to excess the service. Or do I always have to deploy a generated skeleton in case I want to use a client stub?

If it is possible: Why do I need a skeleton at all?

If it is not possible: Where am I supposed to get the wsdl file from, if I don't have a service yet? I mean, it then seems to me like a circle: in order to get a wsdl file I need a service (at least an interface), and when I then execute the wsdl2java this is exactly what is generated (among other classes).

What do I understand wrong?

 

Martina


This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.

Reply via email to