...
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.
The WSIF example shown illustrates the following:
...
Component or Bean ID | Description | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="78f802184bbf7987-98bb3f6d-40d14628-82a1af93-493ed3b14289c32c01e8ee12"><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 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. |
...