WSDL is the universal standard XML for describing a (web) service interface
("web" is misleading
here - WSDL works GREAT for describing ANY service interface) including message
structure and
types (using XSD), protocols, and locations (host urls). (note, this is WSDL
combined with
SOAP-Bindings - WSDL itself is much more abstract - basically just describe the
operations an
interface will support - the soap-binding tags are required to map theinterface
to some
soap-specific aspects just as XML Schema tags are needed to add type
descriptions to the
inteface description).
WSDD is an XML used by the Axis engine to control what the Axis server deploys
(what classes
handle which services, what classes handle serializing the XML to/from the
object model,
which services are deployed on a server, and so forth). the WSDL certainly
drives what's in
the WSDD, but a WSDL alone doesn't tell Axis enough to know the HOW behind the
WHAT described
by the WSDL.
and UDDI, as far as i know, is still just a good idea that doesn't get that
much use, at least
within intranets, but i may be mistaken on this - of all the services i've
worked on (which is
only a handfull) NONE of them used UDDI because you code your clients to your
service
interface, so the WSDL isn't really needed at runtime, and typically clients
already know where
the service is running (more or less).
the only thing i know that generates a wsdd is the wsdl2java tool with the -s
flag.
> What is the different between WSDD and WSDL. My understanding is
> WSDD - is used to deploy a webservice on the webserver
> WSDL- Is used to publish the web service in the UDDI.
> Is that right ?
> What is the best way to create a WSDD for a webservice defined in the java
> ( have access to the source code). Where can I find more information on
> WSDD- a tutorial on how to create WSDD. Are there any open source tools that
> help create WSDD.
> Thanks a lot in advance. !
>
