THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
This example shows critical code snippets from a larger example, which can be found at: url_here. The original example has a client application submitting a zip code to a Web Services application. The web service checks if DSL service is available in the zip code area and responds to the client. In the original example, the client uses a JMS queue to send the message and the web service receives the message from queue and responds. In the ServiceMix example, the WSIF API is used by the client to make the request. This decouples the transport layer from the client code. The WSIF 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. WSIF provides a single API to the client and handles the details of the transmission for the client. More to follow...
The following example shows how to bind a WSDL file for a web service, which is adorned with WSIF additional metadata to configure the service implementation.
...
Component or Bean ID | Description | ||
|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4683c7e25d9c224c-9bea60c0-41374882-bd038853-bc951cb6b24e5bceb6f827f5"><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. |
...