There we used an HttpInterceptor class to
intercept the contents of the JBI exchange and print them out on the console. We will
enhance the code from that sample to demonstrate how we can integrate XStream
with other JBI classes in ServiceMix.
Sample Use Case
In the SOA scenarios, we use the XML formatted messages to transport payload
across nodes. Whether SOAP formatted or not, XML provides a flexible mechanism
to transport data, which can be validated if required using the XML schemas. Let us
also build our sample around this. Hence, we will assume that we have an external
client sending an XML payload to the ESB. Let us see how we can interact with this
data inside the bus.
This is diagrammatically represented in the following figure:
HTTP Client
NMR
ESB
6
2 5
3 4
1
XStreamInspector HttpInterceptor HttpConnector
Chapter 12
[ 227 ]
The sample use case will consist of the following components:
HTTP Client: The HTTP Client is a client external to the ESB which interact
with the HTTP Connector inside the ESB to send the request message and get
the response back.
HTTP Connector: The HTTP Connector is a ServiceMix HttpConnector
component configured to listen to a specific port.
Pages:
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317