This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

to understand the web servcie architecture with example  RSS feed

 
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I deployed and called a simple web servcie,performing the sum of two numbers, by Axis1.4.
I refer the following link to work my web servcies http://lkamal.blogspot.com/2008/07/web-service-axis-tutorial-client-server.html
But as per web service architecture, I am not getting how the UDDI registry comes into the picture?
I will be very thankful if somebody can explain me the example used in the above link with respect to the web service architecture
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!

anish jain wrote:But as per web service architecture, I am not getting how the UDDI registry comes into the picture?


A UDDI registry can be used to register and categorize web services.
This will then enable web service clients to locate services using the registry, instead of having to know the address of their WSDL. This is one area in which (UDDI) registries still fill a relevant function.
Another area that a registry may be useful is if you have a large organization that require governance of services and associated data. As far as I know, such a registry would not be a pure UDDI registry, but also supply additional features.
One of the visions that people had in connection to UDDI registries were that clients would be able to locate all services performing a certain function and then selecting the preferred one, using certain criteria (for instance, cost, speed etc). This vision were, to my knowledge, never quite realized.
Best wishes!
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!