Interface DataSetEndpointBuilderFactory.DataSetEndpointProducerBuilder

All Superinterfaces:
org.apache.camel.builder.EndpointProducerBuilder, org.apache.camel.EndpointProducerResolver
All Known Subinterfaces:
DataSetEndpointBuilderFactory.DataSetEndpointBuilder
Enclosing interface:
DataSetEndpointBuilderFactory

public static interface DataSetEndpointBuilderFactory.DataSetEndpointProducerBuilder extends org.apache.camel.builder.EndpointProducerBuilder
Builder for endpoint producers for the Dataset component.
  • Method Details

    • advanced

    • dataSetIndex

      Controls the behaviour of the CamelDataSetIndex header. off (consumer) the header will not be set. strict (consumer) the header will be set. lenient (consumer) the header will be set. off (producer) the header value will not be verified, and will not be set if it is not present. strict (producer) the header value must be present and will be verified. lenient (producer) the header value will be verified if it is present, and will be set if it is not present. The option is a: java.lang.String type. Default: lenient Group: common
      Parameters:
      dataSetIndex - the value to set
      Returns:
      the dsl builder
    • assertPeriod

      default DataSetEndpointBuilderFactory.DataSetEndpointProducerBuilder assertPeriod(long assertPeriod)
      Sets a grace period after which the mock will re-assert to ensure the preliminary assertion is still valid. This is used, for example, to assert that exactly a number of messages arrive. For example, if the expected count was set to 5, then the assertion is satisfied when five or more messages arrive. To ensure that exactly 5 messages arrive, then you would need to wait a little period to ensure no further message arrives. This is what you can use this method for. By default, this period is disabled. The option is a: long type. Group: producer
      Parameters:
      assertPeriod - the value to set
      Returns:
      the dsl builder
    • assertPeriod

      Sets a grace period after which the mock will re-assert to ensure the preliminary assertion is still valid. This is used, for example, to assert that exactly a number of messages arrive. For example, if the expected count was set to 5, then the assertion is satisfied when five or more messages arrive. To ensure that exactly 5 messages arrive, then you would need to wait a little period to ensure no further message arrives. This is what you can use this method for. By default, this period is disabled. The option will be converted to a long type. Group: producer
      Parameters:
      assertPeriod - the value to set
      Returns:
      the dsl builder
    • consumeDelay

      default DataSetEndpointBuilderFactory.DataSetEndpointProducerBuilder consumeDelay(long consumeDelay)
      Allows a delay to be specified which causes a delay when a message is consumed by the producer (to simulate slow processing). The option is a: long type. Default: 0 Group: producer
      Parameters:
      consumeDelay - the value to set
      Returns:
      the dsl builder
    • consumeDelay

      Allows a delay to be specified which causes a delay when a message is consumed by the producer (to simulate slow processing). The option will be converted to a long type. Default: 0 Group: producer
      Parameters:
      consumeDelay - the value to set
      Returns:
      the dsl builder
    • expectedCount

      default DataSetEndpointBuilderFactory.DataSetEndpointProducerBuilder expectedCount(int expectedCount)
      Specifies the expected number of message exchanges that should be received by this mock. Beware: If you want to expect that 0 messages, then take extra care, as 0 matches when the tests starts, so you need to set a assert period time to let the test run for a while to make sure there are still no messages arrived; for that use the assertPeriod option. If you want to assert that exactly nth message arrives to this mock, then see also the assertPeriod option for further details. The option is a: int type. Default: -1 Group: producer
      Parameters:
      expectedCount - the value to set
      Returns:
      the dsl builder
    • expectedCount

      Specifies the expected number of message exchanges that should be received by this mock. Beware: If you want to expect that 0 messages, then take extra care, as 0 matches when the tests starts, so you need to set a assert period time to let the test run for a while to make sure there are still no messages arrived; for that use the assertPeriod option. If you want to assert that exactly nth message arrives to this mock, then see also the assertPeriod option for further details. The option will be converted to a int type. Default: -1 Group: producer
      Parameters:
      expectedCount - the value to set
      Returns:
      the dsl builder