org.apache.camel

Annotation Type RoutingSlip

@Retention(value=RUNTIME)
 @Documented
 @Target(value={FIELD,METHOD,CONSTRUCTOR})
public @interface RoutingSlip

Indicates that this method is to be used as a Routing Slip routing the incoming message through a series of processing steps. When a message Exchange is received from an Endpoint then the Bean Integration mechanism is used to map the incoming Message to the method parameters. The return value of the method is then converted to either a Collection or array of objects where each element is converted to an Endpoint or a String, or if it is not a collection/array then it is converted to an Endpoint or String. Then for each endpoint or URI the message is routed in a pipes and filter fashion.

See Also:

DynamicRouter

Optional Element Summary

Optional Elements

Modifier and Type	Optional Element and Description
int	cacheSize Sets the maximum size used by the ProducerCache which is used to cache and reuse producers when using this routing slip, when uris are reused.
String	delimiter Sets the uri delimiter to use
boolean	ignoreInvalidEndpoints Whether to ignore the invalidate endpoint exception when try to create a producer with that endpoint

Element Detail

delimiter

public abstract String delimiter

Sets the uri delimiter to use

Default:

","

ignoreInvalidEndpoints

public abstract boolean ignoreInvalidEndpoints

Whether to ignore the invalidate endpoint exception when try to create a producer with that endpoint

Default:

false

cacheSize

public abstract int cacheSize

Sets the maximum size used by the ProducerCache which is used to cache and reuse producers when using this routing slip, when uris are reused. Beware that when using dynamic endpoints then it affects how well the cache can be utilized. If each dynamic endpoint is unique then its best to turn of caching by setting this to -1, which allows Camel to not cache both the producers and endpoints; they are regarded as prototype scoped and will be stopped and discarded after use. This reduces memory usage as otherwise producers/endpoints are stored in memory in the caches. However if there are a high degree of dynamic endpoints that have been used before, then it can benefit to use the cache to reuse both producers and endpoints and therefore the cache size can be set accordingly or rely on the default size (1000). If there is a mix of unique and used before dynamic endpoints, then setting a reasonable cache size can help reduce memory usage to avoid storing too many non frequent used producers.

Default:

0