THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
SEDA Component
The seda: component provides asynchronous SEDA behaviour so that messages are exchanged on a BlockingQueue and consumers are invoked in a seperate thread pool to the producer.
Note that queues are only visible within a single CamelContext. If you want to communicate across CamelContext instances such as to communicate across web applications, see the VM component.
This component does not implement any kind of persistence or recovery if the VM termininates while messages are yet to be processed. If you need persistence, reliability or distributed SEDA then try using either JMS or ActiveMQ
URI format
seda:someName
Where someName can be any string to uniquely identify the endpoint within the current CamelContext