Use Case For the Basic Example

The Basic example shows how to integrate an external application with the JBI bus (ServiceMix).
The same scenario applies to integrating legacy applications with the JBI bus as well.
The technique used in the Basic example could be used to integrate
SAP, Peoplesoft or other external applications, such as POJOs and EJBs that need to
communicate with each other or a legacy application, onto an enterprise service bus.

The purpose of this is to provide a way for different applications
to communicate in a common or "protocol neutral" way through the enterprise
service bus. In our example, the external applications are the same (JMS),
so obviously they could communicate directly; this is a simplification to
enable us to concentrate on the logical flow of the messages
rather than the details of transforming one type of message into another.

Recall from the JSR 208 specification the components for one legacy/external application
to talk to one another:

legacy/external app --> resource adapter --> |binding component (inside ESB) --> NMR -->
binding component |--> resource adapter --> legacy app.

(I will make a Dave Chappell like diagram of above for this use case, then map in
the Basic example components where they belong in the diagram.)

Etcetera, etc....

Note: The only downside that my hit is that example uses inbound messages
via the resource adapter, and most legacy applications won't support
inbound messaging iva the resource adapter. For example, I think all
the librados connectors only do outbound messaging.