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. As per that, our aim here is to send the message to an In-
Out MEP component (a content retriever in our case) and then to route the
out message from that component to the next chain in the flow (which again
in our case is a second pipeline).
???
???
???
???
???
Web Service Versioning
[ 272 ]
Content retriever: The functionality of this component is to extract the
payload part from the incoming SOAP request. Hence, we trim out the
SOAP envelope and body tags, and extract only the contents within the body
element to be sent to the next component. We said that we need to invoke
a web service and you might wonder why we want to extract the payload
alone rather than sending the whole SOAP request to the target web service.
The reason why we are doing this will be evident when we review the HTTP
Provider. Content Retriever will send the out part of the message back to the
transformer pipeline.
Pages:
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377