This chapter will only explain the use of Camel Triggers in the Stardust Browser Modeler. For use of Camel Triggers in the Eclipse Modeler please refer to chapter Working with Triggers in the Developer Handbook.
A Camel Trigger allows to start a process by receiving messages from an arbitrary Camel Endpoint and passing these into the Process the Trigger is defined for.
It can be created by creating a Start Event in the Browser Modeler via the Toolbar Button
and placing the Event Symbol in the Process Diagram.
Selecting the Event Symbol will open the corresponding Properties Page.
By selecting Camel the Properties Page for Camel Triggers will be opened.
The following values for Endpoint Type are supported
If the Endpoint Type is set to Generic, you may add an Additional Route Specification and Additional Beans Specification.
If you intend to start Stardust processing at another place than at the end of the additional route (e.g. in a Split or Aggregate Directive), you need to specify the Endpoint for Stardust via
<aggregate strategyRef="aggregatorStrategy"> <correlationExpression> <simple>header.cheese</simple> </correlationExpression> <to uri="ipp:this"/> </aggregate>
If you have a process with a generic Camel trigger and one activity, then when the trigger is fired, it will not automatically start next activity as the case with other triggers (JMS, File, etc. ). Instead you need to add <to uri="ipp:direct" /> to continue with process.
For example :
Note: You have to add <to uri="ipp:direct" /> only if you use generic endpoint. When another type of endpoint is used, it's not necessary to add it because it's already implemented.
In later release we are planning to support other than generic Triggers (e.g. File, JMS, REST, Timer, FIX, Mail, etc.).