Hence we are specifying soap and soapAction
together. However, soap will wrap the request in the SOAP envelope. We
don't want the body content wrapped in two levels of SOAP envelope. That
is why in the Content Retriever component (we already have seen this short
while ago) we extract only the contents within the body element to be send to
the next component.
Remote web service: This is a normal web service which can be deployed in
any web container infrastructure.
JMS provider: The SOAP response is placed back in the queue configured
in the JMS Provider component from where the client program picks up
the message.
HTTP consumer: The HTTP Consumer components configured here are
just to help you to send arbitrary messages to the sample set up for any
ad-hoc testing.
???
???
???
??? ???
???
Chapter 14
[ 273 ]
We have now seen the major components configured for the sample application and
how the message flows through them. We also have a few more settings so that we
can actually demonstrate that we can control multiple versions of web services to be
exposed to clients in the covenant-based settings.
Pages:
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379