THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The example also shows an important feature of the ServiceMix Client API – how to bind a WSDL file for a web service, which is adorned with WSIF additional metadata to configure the service implementation.
The following example shows how to bind a WSDL which is adorned with WSIF additional metadata to configure the service implementation.
| 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/example.xml} |
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} |
Working with XML versus properties.
The JBI standard says you must encode WSDL 1.1 parts using an XML encoding mechanism. We support 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.
| Wiki Markup |
|---|
{snippet:id=wsif|lang=java|url=http://svn.servicemix.codehaus.org/*checkout*/branches/servicemix-1.1/base/src/test/java/org/servicemix/components/wsif/WsifTest.java} |
This Java code works against the given WSLD 1.1 service using its named parts
| Wiki Markup |
|---|
{snippet:id=wsdl|lang=xml|url=http://svn.servicemix.codehaus.org/*checkout*/branches/servicemix-1.1/base/src/test/resources/org/servicemix/components/wsif/service.wsdl} |
| Code Block |
|---|
<component id="checkAvailability" service="foo:checkAvailability" class="org.servicemix.components.wsif.WSIFBinding"> <property name="definitionResource" value="classpath:org/servicemix/components/wsif/service.wsdl"/> </component> |
...
Component or Bean ID | Description | ||
|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ce256848ab3cf3ed-6976062c-40444bf8-96acbd05-4c09b730abc4443ebc604b17"><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. |
...