<dependency> <groupId>org.switchyard.components</groupId> <artifactId>switchyard-component-camel-core</artifactId> <version>SWITCHYARD-VERSION</version> </dependency>
The SEDA binding in SwitchYard provides asynchronous service binding between camel route and SwitchYard service.
SEDA queue is not persistent.
This binding have it's own namespace. To use it you must declare namespace with uri urn:switchyard-component-camel-core:config:1.0. Your Maven project should also have following dependency:
<dependency> <groupId>org.switchyard.components</groupId> <artifactId>switchyard-component-camel-core</artifactId> <version>SWITCHYARD-VERSION</version> </dependency>
This binding do not depend on switchyard-component-camel and it might be used separately.
This binding is built on top of camel-seda. Please refer camel documentation for detailed description of options.
Following options can be apiled to <binding.seda> definition:
name : queue name
size : the maximum capacity of the SEDA queue (the number of messages it can hold)
concurrentConsumers
waitForTaskToComplete
timeout
multipleConsumers
limitConcurrentConsumers
Here's an example of what a SEDA service binding looks like:
<sca:composite name="camel-binding" targetNamespace="urn:switchyard-quickstart:camel-binding:0.1.0"> <sca:service name="GreetingService" promote="GreetingService"> <camel:binding.seda> <camel:name>GreetingQueue</camel:name> <camel:size>6</camel:size> <camel:concurrentConsumers>2</camel:concurrentConsumers> </camel:binding.seda> </sca:service> </sca:composite>