| { |
| "connector": { |
| "class": "org.apache.camel.kafkaconnector.sjmsbatch.CamelSjmsbatchSourceConnector", |
| "artifactId": "camel-sjms-batch-kafka-connector", |
| "groupId": "org.apache.camel.kafkaconnector", |
| "id": "camel-sjms-batch-source", |
| "type": "source", |
| "version": "0.7.3", |
| "description": "Highly performant and transactional batch consumption of messages from a JMS queue." |
| }, |
| "properties": { |
| "camel.source.path.destinationName": { |
| "name": "camel.source.path.destinationName", |
| "description": "The destination name. Only queues are supported, names may be prefixed by 'queue:'.", |
| "priority": "HIGH", |
| "required": "true" |
| }, |
| "camel.source.endpoint.aggregationStrategy": { |
| "name": "camel.source.endpoint.aggregationStrategy", |
| "description": "The aggregation strategy to use, which merges all the batched messages into a single message", |
| "priority": "HIGH", |
| "required": "true" |
| }, |
| "camel.source.endpoint.allowNullBody": { |
| "name": "camel.source.endpoint.allowNullBody", |
| "description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.", |
| "defaultValue": "true", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.bridgeErrorHandler": { |
| "name": "camel.source.endpoint.bridgeErrorHandler", |
| "description": "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.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.completionInterval": { |
| "name": "camel.source.endpoint.completionInterval", |
| "description": "The completion interval in millis, which causes batches to be completed in a scheduled fixed rate every interval. The batch may be empty if the timeout triggered and there was no messages in the batch. Notice you cannot use both completion timeout and completion interval at the same time, only one can be configured.", |
| "defaultValue": "1000", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.completionPredicate": { |
| "name": "camel.source.endpoint.completionPredicate", |
| "description": "The completion predicate, which causes batches to be completed when the predicate evaluates as true. The predicate can also be configured using the simple language using the string syntax. You may want to set the option eagerCheckCompletion to true to let the predicate match the incoming message, as otherwise it matches the aggregated message.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.completionSize": { |
| "name": "camel.source.endpoint.completionSize", |
| "description": "The number of messages consumed at which the batch will be completed", |
| "defaultValue": "200", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.completionTimeout": { |
| "name": "camel.source.endpoint.completionTimeout", |
| "description": "The timeout in millis from receipt of the first first message when the batch will be completed. The batch may be empty if the timeout triggered and there was no messages in the batch. Notice you cannot use both completion timeout and completion interval at the same time, only one can be configured.", |
| "defaultValue": "500", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.consumerCount": { |
| "name": "camel.source.endpoint.consumerCount", |
| "description": "The number of JMS sessions to consume from", |
| "defaultValue": "1", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.eagerCheckCompletion": { |
| "name": "camel.source.endpoint.eagerCheckCompletion", |
| "description": "Use eager completion checking which means that the completionPredicate will use the incoming Exchange. As opposed to without eager completion checking the completionPredicate will use the aggregated Exchange.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.includeAllJMSXProperties": { |
| "name": "camel.source.endpoint.includeAllJMSXProperties", |
| "description": "Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.mapJmsMessage": { |
| "name": "camel.source.endpoint.mapJmsMessage", |
| "description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. See section about how mapping works below for more details.", |
| "defaultValue": "true", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.pollDuration": { |
| "name": "camel.source.endpoint.pollDuration", |
| "description": "The duration in milliseconds of each poll for messages. completionTimeOut will be used if it is shorter and a batch has started.", |
| "defaultValue": "1000", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.sendEmptyMessageWhenIdle": { |
| "name": "camel.source.endpoint.sendEmptyMessageWhenIdle", |
| "description": "If using completion timeout or interval, then the batch may be empty if the timeout triggered and there was no messages in the batch. If this option is true and the batch is empty then an empty message is added to the batch so an empty message is routed.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.exceptionHandler": { |
| "name": "camel.source.endpoint.exceptionHandler", |
| "description": "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.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.exchangePattern": { |
| "name": "camel.source.endpoint.exchangePattern", |
| "description": "Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]", |
| "priority": "MEDIUM", |
| "required": "false", |
| "enum": [ |
| "InOnly", |
| "InOut", |
| "InOptionalOut" |
| ] |
| }, |
| "camel.source.endpoint.asyncStartListener": { |
| "name": "camel.source.endpoint.asyncStartListener", |
| "description": "Whether to startup the consumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and\/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.headerFilterStrategy": { |
| "name": "camel.source.endpoint.headerFilterStrategy", |
| "description": "To use a custom HeaderFilterStrategy to filter header to and from Camel message.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.jmsKeyFormatStrategy": { |
| "name": "camel.source.endpoint.jmsKeyFormatStrategy", |
| "description": "Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.keepAliveDelay": { |
| "name": "camel.source.endpoint.keepAliveDelay", |
| "description": "The delay in millis between attempts to re-establish a valid session. If this is a positive value the SjmsBatchConsumer will attempt to create a new session if it sees an Exception during message consumption. This delay value allows you to pause between attempts to prevent spamming the logs. If this is a negative value then the SjmsBatchConsumer will bail out and the consumer will not stop consuming new messages. The default is 5000 ms, that is, 5 seconds.", |
| "defaultValue": "5000", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.messageCreatedStrategy": { |
| "name": "camel.source.endpoint.messageCreatedStrategy", |
| "description": "To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.recoveryInterval": { |
| "name": "camel.source.endpoint.recoveryInterval", |
| "description": "Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.", |
| "defaultValue": "5000", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.synchronous": { |
| "name": "camel.source.endpoint.synchronous", |
| "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.source.endpoint.timeoutCheckerExecutorService": { |
| "name": "camel.source.endpoint.timeoutCheckerExecutorService", |
| "description": "If using the completionInterval option a background thread is created to trigger the completion interval. Set this option to provide a custom thread pool to be used rather than creating a new thread for every consumer.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.component.sjms-batch.bridgeErrorHandler": { |
| "name": "camel.component.sjms-batch.bridgeErrorHandler", |
| "description": "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.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.component.sjms-batch.asyncStartListener": { |
| "name": "camel.component.sjms-batch.asyncStartListener", |
| "description": "Whether to startup the consumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and\/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.", |
| "defaultValue": "false", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.component.sjms-batch.autowiredEnabled": { |
| "name": "camel.component.sjms-batch.autowiredEnabled", |
| "description": "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.", |
| "defaultValue": "true", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.component.sjms-batch.connectionFactory": { |
| "name": "camel.component.sjms-batch.connectionFactory", |
| "description": "A ConnectionFactory is required to enable the SjmsBatchComponent.", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.component.sjms-batch.recoveryInterval": { |
| "name": "camel.component.sjms-batch.recoveryInterval", |
| "description": "Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.", |
| "defaultValue": "5000", |
| "priority": "MEDIUM", |
| "required": "false" |
| }, |
| "camel.component.sjms-batch.headerFilterStrategy": { |
| "name": "camel.component.sjms-batch.headerFilterStrategy", |
| "description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.", |
| "priority": "MEDIUM", |
| "required": "false" |
| } |
| } |
| } |
