...
Component or Bean ID | Description | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0fc2f38581a5f081-6f0427fd-45d146e2-b24284ab-e706547d72735f790b47b364"><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. |
...
The JBI standard requires encoding WSDL 1.1 parts using an XML encoding mechanism. ServiceMix supports this model. However, in addition we also allow the message properties, of an NMR message, to use the named parts of the service.wsdl
file to avoid unnecessary XML marshalling.
...