Class RoutingSlipDefinition<Type extends ProcessorDefinition<Type>>

  • All Implemented Interfaces:
    org.apache.camel.CamelContextAware, org.apache.camel.LineNumberAware, Block, HasExpressionType, org.apache.camel.NamedNode, org.apache.camel.spi.HasId, org.apache.camel.spi.IdAware

    @Metadata(label="eip,routing")
    public class RoutingSlipDefinition<Type extends ProcessorDefinition<Type>>
    extends ExpressionNode
    Routes a message through a series of steps that are pre-determined (the slip)
    • Constructor Detail

      • RoutingSlipDefinition

        public RoutingSlipDefinition()
      • RoutingSlipDefinition

        public RoutingSlipDefinition​(String headerName)
      • RoutingSlipDefinition

        public RoutingSlipDefinition​(String headerName,
                                     String uriDelimiter)
      • RoutingSlipDefinition

        public RoutingSlipDefinition​(org.apache.camel.Expression expression,
                                     String uriDelimiter)
      • RoutingSlipDefinition

        public RoutingSlipDefinition​(org.apache.camel.Expression expression)
    • Method Detail

      • getShortName

        public String getShortName()
      • getLabel

        public String getLabel()
        Description copied from class: ProcessorDefinition
        Returns a label to describe this node such as the expression if some kind of expression node
        Specified by:
        getLabel in interface org.apache.camel.NamedNode
        Overrides:
        getLabel in class ExpressionNode
      • setExpression

        public void setExpression​(ExpressionDefinition expression)
        Expression to define the routing slip, which defines which endpoints to route the message in a pipeline style. Notice the expression is evaluated once, if you want a more dynamic style, then the dynamic router eip is a better choice.
        Overrides:
        setExpression in class ExpressionNode
      • setUriDelimiter

        public void setUriDelimiter​(String uriDelimiter)
      • getUriDelimiter

        public String getUriDelimiter()
      • setIgnoreInvalidEndpoints

        public void setIgnoreInvalidEndpoints​(String ignoreInvalidEndpoints)
      • getIgnoreInvalidEndpoints

        public String getIgnoreInvalidEndpoints()
      • getCacheSize

        public String getCacheSize()
      • setCacheSize

        public void setCacheSize​(String cacheSize)
      • ignoreInvalidEndpoints

        public RoutingSlipDefinition<Type> ignoreInvalidEndpoints()
        Ignore the invalidate endpoint exception when try to create a producer with that endpoint
        Returns:
        the builder
      • ignoreInvalidEndpoints

        public RoutingSlipDefinition<Type> ignoreInvalidEndpoints​(boolean ignoreInvalidEndpoints)
        Ignore the invalidate endpoint exception when try to create a producer with that endpoint
        Returns:
        the builder
      • ignoreInvalidEndpoints

        public RoutingSlipDefinition<Type> ignoreInvalidEndpoints​(String ignoreInvalidEndpoints)
        Ignore the invalidate endpoint exception when try to create a producer with that endpoint
        Returns:
        the builder
      • uriDelimiter

        public RoutingSlipDefinition<Type> uriDelimiter​(String uriDelimiter)
        Sets the uri delimiter to use
        Parameters:
        uriDelimiter - the delimiter
        Returns:
        the builder
      • cacheSize

        public RoutingSlipDefinition<Type> cacheSize​(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.
        Parameters:
        cacheSize - the cache size, use 0 for default cache size, or -1 to turn cache off.
        Returns:
        the builder
      • cacheSize

        public RoutingSlipDefinition<Type> cacheSize​(String 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.
        Parameters:
        cacheSize - the cache size, use 0 for default cache size, or -1 to turn cache off.
        Returns:
        the builder