Versions Compared

Old Version 4

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

Saved on

compared with

New Version 5

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

Saved on

Key

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

Overview of the ServiceMix 1.x WSIF Example

This document describes the components that integrate with the Apache Web Service Invocation Framework (WSIF) to perform web service invocations using a number of different implementation protocols such as Axis, local Java, EJB, JMS, JCA and CCI.

...

Component or Bean ID

Description

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b9390d05a0df0d93-d3ac7f24-49d247ef-b80ca8a7-cad832dd2f1a27ae75f3b708"><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.

Some Coding Details

The following Following are descriptions of the properties found in the service.wsdl file:.

  • <jms:address> describes a target port that is accessible via JMS.
  • destinationStyle must either be queue or topic, although only queue is supported at this time.
  • jndiDestinationName is the JNDI name of the JMS queue that WSIF will send requests to.
  • jndiConnectionFactoryName is the JNDI name of the connection factory that WSIF will be used.
  • jndiProviderURL and initialContextFactory specify which JNDI database to use. If they are not present, WSIF uses the default JNDI.
  • jms:binding specifies that this binding is for Native Jms. The type is the type of the JMS message that will be sent. In this case it will be a text message.

...