Versions Compared

Old Version 42

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

Saved on

compared with

New Version 43

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

Saved on

Key

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

...

In the ServiceMix example, the WSIF API is used by the client to make the zip code request to the web service. The WSIF API takes care of the details of JMS for the client. Other Instead of JMS, other transport mechanisms could have been used by the client as well, such as SOAP, JCA, etc. The ServiceMix WSIF API provides a single API to the client and handles the details of the web service invocation for the client, simplifying the client code.

The example also shows an important feature of the ServiceMix Client API - how to bind a WSDL file for a web service, which is adorned with WSIF additional metadata to configure the service implementation. In other words, the service.wsdl file contains WSIF extensions to WSDL that bind the web service to the transport protocol. Some code of the coding details will be shown later in this document.

...

The diagram below illustrates the logical flow of the example program:



Panel
borderColor#ccc
titleWSIF Logical Flow Diagram
borderStylesolid

...

Component or Bean ID

Description

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1800e83e19488e84-ccf3f58c-4cf84296-9580903b-94821792adbdae905dad9363"><ac:plain-text-body><![CDATA[

checkAvailability

This component uses the WSIFBinding class to integrate WSIF to ServiceMix as specified in the class property. Its definitionResource property is set to read the file classpath:org/servicemix/components/wsif/service.wsdl, which is 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 in the config files. When a message is delivered, it extracts the body which is a zip code. 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.

...