Versions Compared

Old Version 54

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

Saved on

compared with

New Version 55

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

Saved on

Key

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

...

Note: This is not a complete and working example. Rather, it illustrates how WSIF can be used in a servicemix ServiceMix component and used through a typical and realistic web application.The following components in the diagram have not been completely implemented:

...

Component or Bean ID

Description

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7f18079a458c2882-9e7f6ee9-4c6f4474-bec9aea6-a04ad47013842f22e3c6452d"><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. The servicemix.wsdl file can be found at [servicemix-2.x_src_install_dir]\components\base\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.

...