We have provided two SOAP request files for testing. They are:
SoapRequest20061231.xml
SoapRequest20070101.xml
As is evident from their names, SoapRequest20061231.xml has 20061231
embedded as the version in the body whereas SoapRequest20070101.xml
has 20070101 as its version. The readers are free to change this version
values to their own figures to test whether or not the router behaves
appropriately. If required, the readers can also add more clauses to the
rules in the content-based router and understand the behavior.
Web Service Versioning
[ 280 ]
Transformer pipeline: The pipeline is a standard EIP component and is an
integration bridge between an In-Only (or Robust-In-Only) MEP and an
In-Out MEP. By receiving an In-Only MEP by the pipeline, it will send the
input message in an In-Out MEP to the transformer destination and then in
turn forward the response in an In-Only MEP to the target destination. Let us
look at our pipeline configuration shown in the following code:
endpoint="pipelineTransformBefore20061231">
service="test:pipelineServiceBefore20061231" />
The pipeline receives the SOAP request in an In-Only MEP.
Pages:
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388