While doing so, we will also see how to use the Apache
Axis client-side APIs to send a request to and receive a response from the web
service, through the JMS channel rather than the normal HTTP channel. We may
not configure all of the QOS features for the JMS provider here such as transaction,
message persistence, or guaranteed delivery. Most of them are outside the standard
J2EE configurations and have to be done at the JMS provider-level based on the
vendor-specific mechanisms. Since this book is about JBI and ServiceMix and not
JMS, we will concentrate only on the binding part. Once we are successful in binding
the web service to JMS, then enabling other QOS features is similar to what we do in
the normal JMS configurations.
Chapter 11
[ 209 ]
ServiceMix Component Architecture for the
JMS Web Service
We will first look at the technical architecture for the whole component setup to see
how we can route messages through various ServiceMix components. The major
parties or roles taking part in the exchange are as follows:
External client (sending request and accepting response).
Pages:
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297