Hence the In-Only MEP used in JMS doesn't fit
well. A pipeline can solve this problem by providing a bridge between the two
protocols??”JMS and HTTP. This design is shown in the following figure:
You may also refer the Chapter 11 (Access Web Service using JMS Channel) to see an
implementation for this.
Enterprise Integration Patterns in ESB
[ 336 ]
Sample Use Case
The sample use case will have the following components:
JMS client: This is a normal external JMS client, placing XML messages onto
the JMS consumer component configured within the ESB.
JMS consumer: This is a servicemix-jms listening on queue "A". Any
incoming messages to this queue will be routed to the next component in the
flow chain which is the pipeline.
Pipeline: The Pipeline is a servicemix-eip component. The pipeline
receives an In-Only MEP from JMS consumer. The pipeline then sends
the same message in an In-Out MEP to the echo component. The echoed
response is send back to the pipeline which is then forwarded to the JMS
consumer in another In-Only MEP.
Echo component: The echo component echoes back any messages it receives.
Pages:
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452