THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Web Services Invocation Framework (WSIF) provides a Java API for calling Web services, hiding the details of how the service is provided, e.g., via SOAP or JMS, etc. This document describes the ServiceMix 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.
...
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 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 transmission web service invocation for the client, simplifying the client code.
...
- A user opens a web browser and accesses a web form with a "zip code" input field and a submit button. The submit button sends the form and the zip code typed in by the user to a Servicemix HTTP binding component.
- The HTTP binding component creates an InOut exchange message through the client API. The message is sent through the NMR to the checkAvailability component.
- The checkAvailability component sends the request to the JMS queue.
- The web service is implemented with as a message driven EJB (MDB), who's "onMessage" method is listening for messages on the queue.
- 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).
- The checkAvailability component receives the response from the queue.
- The checkAvailability component responds to the HTTP client.
- The HTTP client sends the result back to the web form. The value of the result property is displayed and lets the user know whether or not DSL is available in the specified zip code area.
...
The following table provides more details about the function of the checkAvailability component and the Web Service MDB:
Component or Bean ID | Description | ||
|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b9f8e4c4907f31d0-1d2091e3-41814461-96bea91b-9dde69482e97de540c4ac502"><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 | ]]></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 presumably a valid 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. |
...
Here is an example of how to enable a service to be exposed over a JMS topic or queue. This is a snippet of code from the service.wsdl file. It shows how to configure the JMS binding:
| Wiki Markup |
|---|
{snippet:id=wsif|lang=xml|url=http://svn.servicemix.codehaus.org/*checkout*/branches/servicemix-1.1/base/src/test/resources/org/servicemix/components/wsif/service.wsdl} |
The following Here are descriptions of the properties found in the service.wsdl file. These The descriptions are quoted from the WSDL Bindings for JMS web page:
...