You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Business Use Case for the JMS Binding Example

The JMS Binding example shows how to connect the JMS bindings to a simple service component inside ServiceMix.

A hypothetical business scenario: A web application to apply for a Tax ID Number. This example shows a web-based Tax ID Application form. The user enters data, such as first and last name, date of birth, and place of birth, in the web application form. The web form sends the request to the "JMSServlet" servlet. The servlet publishes the request on the JMS submission topic. The applicationFormReceiver, which is a JMS Binding component that subscribes to the submission topic, receives the request. The applicationFormReceiver sends the data to the formProcessor via the NMR. The formProcessor is a service engine that assigns the appropriate TIN to the user. The formProcessor then publishes the response to the result topic. A message driven bean (MDB) subscribes to the result topic, receives the response message, updates the TaxID database with the new Tax ID, and notifies the user that the request has been fulfilled. The user can then check the database to get the requested tax id number.

The following diagram illustrates this:

Online Application for Tax ID No. System

  • No labels