We will see the
individual components first and understand the flow.
JMS client: In this sample, we use the JMS channel to send web service
requests. The JMS Client reads the SOAP request message from a file and
sends the message to the JMS Consumer queue configured in the ESB. One
point to be noted here is that we are going to use the targetNamespace
mechanism of the WSDL to implement the service versioning. If we open
the SOAP request, we can see how we have designed the SOAP request so
as to include a version specific value for the namespace attribute. The value
corresponds to the targetNamespace attribute of WSDL for the SOAP request.
JMS consumer: The JMS Consumer is a servicemix-jms component which
allows you to send JMS messages to the configured queue. A consumer role
for the servicemix-jms component implies the component is a consumer
to the NMR. Any messages coming to the queue will be transferred to the
targetService attribute for the JMS Consumer.
WhiteSpace transformer: A valid SOAP request can come in several forms,
all in a single long line or separated out into multiple lines, formatted with
indentations and spaces.
Pages:
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375