Constant Field Values
Contents
org.apache.*
-
org.apache.camel.kafkaconnector.optaplanner.CamelOptaplannerSinkConnectorConfig Modifier and Type Constant Field Value public static final StringCAMEL_SINK_OPTAPLANNER_COMPONENT_AUTOWIRED_ENABLED_CONF"camel.component.optaplanner.autowiredEnabled"public static final StringCAMEL_SINK_OPTAPLANNER_COMPONENT_AUTOWIRED_ENABLED_DOC"Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc."public static final StringCAMEL_SINK_OPTAPLANNER_COMPONENT_LAZY_START_PRODUCER_CONF"camel.component.optaplanner.lazyStartProducer"public static final StringCAMEL_SINK_OPTAPLANNER_COMPONENT_LAZY_START_PRODUCER_DOC"Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel\'s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing."public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_ASYNC_CONF"camel.sink.endpoint.async"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_ASYNC_DOC"Specifies to perform operations in async mode"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_LAZY_START_PRODUCER_CONF"camel.sink.endpoint.lazyStartProducer"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_LAZY_START_PRODUCER_DOC"Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel\'s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing."public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_PROBLEM_ID_CONF"camel.sink.endpoint.problemId"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_PROBLEM_ID_DEFAULT"1L"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_PROBLEM_ID_DOC"In case of using SolverManager : the problem id"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_SOLVER_ID_CONF"camel.sink.endpoint.solverId"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_SOLVER_ID_DEFAULT"DEFAULT_SOLVER"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_SOLVER_ID_DOC"Specifies the solverId to user for the solver instance key"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_THREAD_POOL_SIZE_CONF"camel.sink.endpoint.threadPoolSize"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_THREAD_POOL_SIZE_DOC"Specifies the thread pool size to use when async is true"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_USE_SOLVER_MANAGER_CONF"camel.sink.endpoint.useSolverManager"public static final StringCAMEL_SINK_OPTAPLANNER_ENDPOINT_USE_SOLVER_MANAGER_DOC"use SolverManager instead of XML file config. Use this mode on Quarkus app."public static final StringCAMEL_SINK_OPTAPLANNER_PATH_CONFIG_FILE_CONF"camel.sink.path.configFile"public static final StringCAMEL_SINK_OPTAPLANNER_PATH_CONFIG_FILE_DOC"Specifies the location to the solver file. If useSolverManager=FALSE, Camel uses this file and create the Solver. If useSolverManager=TRUE and SolverManager is set in the header {OptaPlannerConstants.SOLVER_MANAGER} : this file is ignored by Camel usage of SolverManager. SolverManager can be injected by DI in Quarkus or Spring." -
org.apache.camel.kafkaconnector.optaplanner.CamelOptaplannerSourceConnectorConfig Modifier and Type Constant Field Value public static final StringCAMEL_SOURCE_OPTAPLANNER_COMPONENT_AUTOWIRED_ENABLED_CONF"camel.component.optaplanner.autowiredEnabled"public static final StringCAMEL_SOURCE_OPTAPLANNER_COMPONENT_AUTOWIRED_ENABLED_DOC"Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc."public static final StringCAMEL_SOURCE_OPTAPLANNER_COMPONENT_BRIDGE_ERROR_HANDLER_CONF"camel.component.optaplanner.bridgeErrorHandler"public static final StringCAMEL_SOURCE_OPTAPLANNER_COMPONENT_BRIDGE_ERROR_HANDLER_DOC"Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored."public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_BRIDGE_ERROR_HANDLER_CONF"camel.source.endpoint.bridgeErrorHandler"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_BRIDGE_ERROR_HANDLER_DOC"Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored."public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_EXCEPTION_HANDLER_CONF"camel.source.endpoint.exceptionHandler"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_EXCEPTION_HANDLER_DOC"To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored."public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_EXCHANGE_PATTERN_CONF"camel.source.endpoint.exchangePattern"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_EXCHANGE_PATTERN_DOC"Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_PROBLEM_ID_CONF"camel.source.endpoint.problemId"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_PROBLEM_ID_DEFAULT"1L"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_PROBLEM_ID_DOC"In case of using SolverManager : the problem id"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_SOLVER_ID_CONF"camel.source.endpoint.solverId"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_SOLVER_ID_DEFAULT"DEFAULT_SOLVER"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_SOLVER_ID_DOC"Specifies the solverId to user for the solver instance key"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_USE_SOLVER_MANAGER_CONF"camel.source.endpoint.useSolverManager"public static final StringCAMEL_SOURCE_OPTAPLANNER_ENDPOINT_USE_SOLVER_MANAGER_DOC"use SolverManager instead of XML file config. Use this mode on Quarkus app."public static final StringCAMEL_SOURCE_OPTAPLANNER_PATH_CONFIG_FILE_CONF"camel.source.path.configFile"public static final StringCAMEL_SOURCE_OPTAPLANNER_PATH_CONFIG_FILE_DOC"Specifies the location to the solver file. If useSolverManager=FALSE, Camel uses this file and create the Solver. If useSolverManager=TRUE and SolverManager is set in the header {OptaPlannerConstants.SOLVER_MANAGER} : this file is ignored by Camel usage of SolverManager. SolverManager can be injected by DI in Quarkus or Spring."