Versions Compared

Old Version 12

changes.mady.by.user Unknown User (lmalgeri)

Saved on

compared with

New Version 13

changes.mady.by.user Unknown User (lmalgeri)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. A user opens a web browser and access accesses a web form with a "zipcodezip code" input field and a submit button. The submit button sends the form and the zipcode zip code typed in by the user to a Servicemix HTTP binding component.
  2. The HTTP binding component creates an InOut exchange message through the client API. The message is sent through the NMR to the checkAvailability component.
  3. The checkAvailability component sends the request to the JMS queue.
  4. The webservice web service is implemented with as a message driven EJB (MDB), who's "onMessage" method is listening for messages on the queue.
  5. The MDB, processes the request and sends back a response to the checkAvailability component through a temporary queue. The response is either "true" (DSL service is available) or "false" (DSL service is not available).
  6. The checkAvailability component receives the response from the queue.
  7. The checkAvailability component responds to the HTTP client.
  8. The HTTP client sends the result back to the web form. The value of the result property is displayed and let's lets the user know whether or not DSL is available at the zipcodein the specified zip code area.

Details

The following table provides more details about the function of the checkAvailability component the Web Service MDB:

Component or Bean ID

Description

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7082248af981459f-e38cce34-4fab4758-bdfaa25b-4b7e294fa01ff086320b5868"><ac:plain-text-body><![CDATA[

checkAvailability

This component uses the WSIFBinding class to integrate WSIF to service mix as specified in the class property. Its definitionResource property is set to read the file classpath:org/servicemix/components/wsif/service.wsdl, which defines the WSDL file that will be used. This file can be found at [servicemix_src_install_dir]\src\test \resources\org\servicemix\components\wsif. In the init method of the WSIFBinding class, service.wsdl is read to define the binding extension.

]]></ac:plain-text-body></ac:structured-macro>

MDB

This message driven bean is the actual implementation of the service. It acts like a message listener on the queue specified on the config files. When a message is delivered, it extracts the body which is presumably a valid zip code, so the bean makes it an integer in an unsafe and intrepid manner. It then applies some logic to determine whether DSL service is available at this zip code or not. For simplicity, it just returns true for all zip codes < 50000, and false otherwise. The return message is sent to the queue specified in the replyTo field of the request message. Note that the bean must encode the correct JMSCorrelationID in the return message in order for it to be picked up by WSIF.

...