Because of its business and technical relevance to both service provider and service consumer, the lynchpin of the service versioning model is the service specification.
So instead of a complex WSDL specification you have a series of unit tests that make assertions about the service from both a provider and consumer point of view.
These methods are invoked by the WebSphere Application Server Web services runtime as part of the service invocation pipeline (on both consumer and provider sides).
We are rapidly shifting from an economy based on manufacturing and commodities to one that places the greatest value on information, services, support, and distribution.
Try viewing a television show on Hulu, a popular American video service, from Europe and it will tell you: “We’re sorry, currently our video library can only be streamed within the United States.”