To make the content ready for an XPath query
match later in the flow, we use the extraneous WhiteSpace Transformer
component which will trim out all extraneous white spaces from the SOAP
request payload and normalize it into a single line.
Content-based router: The ContentBased Router is used for all kinds of
content-based routing. We earlier discussed that we have designed the SOAP
request so as to include a version specific value in the targetNamespace
attribute for the SOAP request. Hence now we will use a ContentBased
Router which is a servicemix-eip component. This component will inspect
the value for the namespace attribute corresponding to the targetNamespace
attribute of the WSDL embedded in the SOAP request and see the matching
rule configured at the component-level. Depending upon the match, the
ContentBased Router will route the SOAP request message to any one of the
set of Transformer Pipelines configured.
Transformer pipeline: The pipeline is a standard EIP component and hence
is available readily as a standard JBI EIP component in ServiceMix. The
pipeline component is an integration bridge between an In-Only (or Robust-
In-Only) MEP and an In-Out MEP.
Pages:
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376