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. 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. This decouples the transport layer from the client code. 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 for the client, simplifying the client code.
...
Here is an example of how in WSIF you can enable a service to be exposed over a JMS topic or queue:
| 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 JBI standard says you must encode WSDL 1.1 parts using an XML encoding mechanism. We support ServiceMix supports this model. However, in addition we also allow the message properties to be used with WSIF as the named parts to avoid unnecessary XML marshalling. For example here is a Java example using the ServiceMix Client API in a WSIF style of working, passing in and fetching out named parameters.
...
Component or Bean ID | Description | ||
|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4765fa04c287bb47-8190e83b-4ae24e8f-961b86be-9388deec2ab72512fc5b5d81"><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. |
...