WSDL is used to describe the interface of
a web service.
<tModel> UDDI documents
provide metadata descriptions of a web service and pointers to
specifications that describe their implementation. Given this
provision, WSDL documents tie into the UDDI data structures in a
couple of places:
document should be created for each WSDL
document supported by a web service. The
<tModel> describes the abstract service
type, not the service instance; if appropriate, the WSDL file pointed
to by the
<tModel> should not contain the
<port> elements. Omitting the
<port> elements allows a WSDL document to
describe many web services located in several different places. The
WSDL document’s URL should be listed as the value of
<overviewURL> element. A
<tModel> that references a WSDL document
should have a categorization taxonomy of
uddi-org:types; a categorization value of
wsdlSpec should be applied to it by using a
structure is created for each unique
URL access point used by the web service. The
<bindingTemplate> document references one or
<tModel> documents containing the WSDL
definitions supported at this access point.
document is created for each web
service. The document contains one
<bindingTemplate> for each of the access
points supported by the web service.
For example, if you implement one web service that has a single access point and is defined ...