They are just for your convenience and they are not intended
to test the web service versioning mechanism per se. These clients are:
cd ch14\WebServiceVersioning\Client20061231.html
and
cd ch14\WebServiceVersioning\Client20070101.html
Web Service Versioning Operational
Perspective
At the operations perspective, we can use tools to edit the WSDLs to reflect this
change and then place all the WSDLs in a repository for the consumers to find or
even supply these WSDLs to the consumers. The consumers can then use their
conventional tools to generate client stubs and send SOAP requests to access the
service. The version aspect is not revealed to the clients, instead they are limited to
the WSDLs.
As we are using an ESB as the middleware messaging infrastructure, another option
is that the WSDLs can be retrieved from their original source (for example, http://
localhost:8080/AxisEndToEnd20061231/services/HelloWebService20061231?
WSDL) on demand basis from the client. Moreover, do an XSL transform to replace the
different endpoint addresses with a single covenant address and supply them.
Pages:
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399