March 2002
Intermediate to advanced
280 pages
8h 36m
English
Content preview from Java Web ServicesBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Using WSDL Definitions with UDDI
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:
A
<tModel>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<service>and<port>elements. Omitting the<service>and<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 the<overviewURL>element. A<tModel>that references a WSDL document should have a categorization taxonomy ofuddi-org:types; a categorization value ofwsdlSpecshould be applied to it by using a<categoryBag>element.A
<bindingTemplate>structure is created for each unique URL access point used by the web service. The<bindingTemplate>document references one or more<tModel>documents containing the WSDL definitions supported at this access point.A
<businessService>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 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.