schema stringclasses 471
values | key stringlengths 0 203 | description stringlengths 0 4.37k | object stringlengths 2 322k |
|---|---|---|---|
camel-yaml-dsl.json | use-application-context-class-loader | Use ApplicationContextClassLoader as custom ClassLoader | {"type": "boolean"} |
camel-yaml-dsl.json | type | Whether to filter by class type or regular expression | {"type": "string"} |
camel-yaml-dsl.json | value | Value of type such as class name or regular expression | {"type": "string"} |
camel-yaml-dsl.json | org.apache.camel.model.dataformat.ZipDeflaterDataFormat | Compress and decompress streams using java.util.zip.Deflater and java.util.zip.Inflater. | {"type": "object", "properties": {"compression-level": {"type": "string", "default": "-1", "enum": ["-1", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9"]}, "id": {"type": "string"}}} |
camel-yaml-dsl.json | compression-level | To specify a specific compression between 0-9. -1 is default compression, 0 is no compression, and 9 is the best compression. | {"type": "string", "default": "-1", "enum": ["-1", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9"]} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | org.apache.camel.model.dataformat.ZipFileDataFormat | Compression and decompress streams using java.util.zip.ZipStream. | {"type": "object", "properties": {"allow-empty-directory": {"type": "boolean"}, "id": {"type": "string"}, "max-decompressed-size": {"type": "number", "default": "1073741824"}, "preserve-path-elements": {"type": "boolean"}, "using-iterator": {"type": "boolean"}}} |
camel-yaml-dsl.json | allow-empty-directory | If the zip file has more than one entry, setting this option to true, allows to get the iterator even if the directory is empty | {"type": "boolean"} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | max-decompressed-size | Set the maximum decompressed size of a zip file (in bytes). The default value if not specified corresponds to 1 gigabyte. An IOException will be thrown if the decompressed size exceeds this amount. Set to -1 to disable setting a maximum decompressed size. | {"type": "number", "default": "1073741824"} |
camel-yaml-dsl.json | preserve-path-elements | If the file name contains path elements, setting this option to true, allows the path to be maintained in the zip file. | {"type": "boolean"} |
camel-yaml-dsl.json | using-iterator | If the zip file has more than one entry, the setting this option to true, allows working with the splitter EIP, to split the data using an iterator in a streaming mode. | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.errorhandler.DeadLetterChannelDefinition | Error handler with dead letter queue. | {"type": "object", "properties": {"dead-letter-handle-new-exception": {"type": "boolean"}, "dead-letter-uri": {"type": "string"}, "executor-service-ref": {"type": "string"}, "id": {"type": "string"}, "level": {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]}, "log-name": {"type": "string"}, "logger-ref": {"type": "string"}, "on-exception-occurred-ref": {"type": "string"}, "on-prepare-failure-ref": {"type": "string"}, "on-redelivery-ref": {"type": "string"}, "redelivery-policy": {}, "redelivery-policy-ref": {"type": "string"}, "retry-while-ref": {"type": "string"}, "use-original-body": {"type": "boolean"}, "use-original-message": {"type": "boolean"}}, "required": ["dead-letter-uri"]} |
camel-yaml-dsl.json | dead-letter-handle-new-exception | Whether the dead letter channel should handle (and ignore) any new exception that may been thrown during sending the message to the dead letter endpoint. The default value is true which means any such kind of exception is handled and ignored. Set this to false to let the exception be propagated back on the org.apache.camel.Exchange . This can be used in situations where you use transactions, and want to use Camel's dead letter channel to deal with exceptions during routing, but if the dead letter channel itself fails because of a new exception being thrown, then by setting this to false the new exceptions is propagated back and set on the org.apache.camel.Exchange , which allows the transaction to detect the exception, and rollback. | {"type": "boolean"} |
camel-yaml-dsl.json | dead-letter-uri | The dead letter endpoint uri for the Dead Letter error handler. | {"type": "string"} |
camel-yaml-dsl.json | executor-service-ref | Sets a reference to a thread pool to be used by the error handler | {"type": "string"} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | level | Logging level to use when using the logging error handler type. | {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]} |
camel-yaml-dsl.json | log-name | Name of the logger to use for the logging error handler | {"type": "string"} |
camel-yaml-dsl.json | logger-ref | References to a logger to use as logger for the error handler | {"type": "string"} |
camel-yaml-dsl.json | on-exception-occurred-ref | Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom logging about the occurred exception at the exact time it happened. Important: Any exception thrown from this processor will be ignored. | {"type": "string"} |
camel-yaml-dsl.json | on-prepare-failure-ref | Sets a reference to a processor to prepare the org.apache.camel.Exchange before handled by the failure processor / dead letter channel. This allows for example to enrich the message before sending to a dead letter queue. | {"type": "string"} |
camel-yaml-dsl.json | on-redelivery-ref | Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the org.apache.camel.Exchange before its being redelivered. | {"type": "string"} |
camel-yaml-dsl.json | redelivery-policy | Sets the redelivery settings | {} |
camel-yaml-dsl.json | redelivery-policy-ref | Sets a reference to a RedeliveryPolicy to be used for redelivery settings. | {"type": "string"} |
camel-yaml-dsl.json | retry-while-ref | Sets a retry while predicate. Will continue retrying until the predicate evaluates to false. | {"type": "string"} |
camel-yaml-dsl.json | use-original-body | Will use the original input org.apache.camel.Message body (original body only) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | use-original-message | Will use the original input org.apache.camel.Message (original body and headers) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.errorhandler.DefaultErrorHandlerDefinition | The default error handler. | {"type": "object", "properties": {"executor-service-ref": {"type": "string"}, "id": {"type": "string"}, "level": {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]}, "log-name": {"type": "string"}, "logger-ref": {"type": "string"}, "on-exception-occurred-ref": {"type": "string"}, "on-prepare-failure-ref": {"type": "string"}, "on-redelivery-ref": {"type": "string"}, "redelivery-policy": {}, "redelivery-policy-ref": {"type": "string"}, "retry-while-ref": {"type": "string"}, "use-original-body": {"type": "boolean"}, "use-original-message": {"type": "boolean"}}} |
camel-yaml-dsl.json | executor-service-ref | Sets a reference to a thread pool to be used by the error handler | {"type": "string"} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | level | Logging level to use when using the logging error handler type. | {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]} |
camel-yaml-dsl.json | log-name | Name of the logger to use for the logging error handler | {"type": "string"} |
camel-yaml-dsl.json | logger-ref | References to a logger to use as logger for the error handler | {"type": "string"} |
camel-yaml-dsl.json | on-exception-occurred-ref | Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom logging about the occurred exception at the exact time it happened. Important: Any exception thrown from this processor will be ignored. | {"type": "string"} |
camel-yaml-dsl.json | on-prepare-failure-ref | Sets a reference to a processor to prepare the org.apache.camel.Exchange before handled by the failure processor / dead letter channel. This allows for example to enrich the message before sending to a dead letter queue. | {"type": "string"} |
camel-yaml-dsl.json | on-redelivery-ref | Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the org.apache.camel.Exchange before its being redelivered. | {"type": "string"} |
camel-yaml-dsl.json | redelivery-policy | Sets the redelivery settings | {} |
camel-yaml-dsl.json | redelivery-policy-ref | Sets a reference to a RedeliveryPolicy to be used for redelivery settings. | {"type": "string"} |
camel-yaml-dsl.json | retry-while-ref | Sets a retry while predicate. Will continue retrying until the predicate evaluates to false. | {"type": "string"} |
camel-yaml-dsl.json | use-original-body | Will use the original input org.apache.camel.Message body (original body only) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | use-original-message | Will use the original input org.apache.camel.Message (original body and headers) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.errorhandler.JtaTransactionErrorHandlerDefinition | JTA based transactional error handler (requires camel-jta). | {"type": "object", "properties": {"executor-service-ref": {"type": "string"}, "id": {"type": "string"}, "level": {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]}, "log-name": {"type": "string"}, "logger-ref": {"type": "string"}, "on-exception-occurred-ref": {"type": "string"}, "on-prepare-failure-ref": {"type": "string"}, "on-redelivery-ref": {"type": "string"}, "redelivery-policy": {}, "redelivery-policy-ref": {"type": "string"}, "retry-while-ref": {"type": "string"}, "rollback-logging-level": {"type": "string", "default": "WARN", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]}, "transacted-policy-ref": {"type": "string"}, "use-original-body": {"type": "boolean"}, "use-original-message": {"type": "boolean"}}} |
camel-yaml-dsl.json | executor-service-ref | Sets a reference to a thread pool to be used by the error handler | {"type": "string"} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | level | Logging level to use when using the logging error handler type. | {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]} |
camel-yaml-dsl.json | log-name | Name of the logger to use for the logging error handler | {"type": "string"} |
camel-yaml-dsl.json | logger-ref | References to a logger to use as logger for the error handler | {"type": "string"} |
camel-yaml-dsl.json | on-exception-occurred-ref | Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom logging about the occurred exception at the exact time it happened. Important: Any exception thrown from this processor will be ignored. | {"type": "string"} |
camel-yaml-dsl.json | on-prepare-failure-ref | Sets a reference to a processor to prepare the org.apache.camel.Exchange before handled by the failure processor / dead letter channel. This allows for example to enrich the message before sending to a dead letter queue. | {"type": "string"} |
camel-yaml-dsl.json | on-redelivery-ref | Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the org.apache.camel.Exchange before its being redelivered. | {"type": "string"} |
camel-yaml-dsl.json | redelivery-policy | Sets the redelivery settings | {} |
camel-yaml-dsl.json | redelivery-policy-ref | Sets a reference to a RedeliveryPolicy to be used for redelivery settings. | {"type": "string"} |
camel-yaml-dsl.json | retry-while-ref | Sets a retry while predicate. Will continue retrying until the predicate evaluates to false. | {"type": "string"} |
camel-yaml-dsl.json | rollback-logging-level | Sets the logging level to use for logging transactional rollback. This option is default WARN. | {"type": "string", "default": "WARN", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]} |
camel-yaml-dsl.json | transacted-policy-ref | The transacted policy to use that is configured for either Spring or JTA based transactions. If no policy has been configured then Camel will attempt to auto-discover. | {"type": "string"} |
camel-yaml-dsl.json | use-original-body | Will use the original input org.apache.camel.Message body (original body only) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | use-original-message | Will use the original input org.apache.camel.Message (original body and headers) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.errorhandler.NoErrorHandlerDefinition | To not use an error handler. | {"type": "object", "properties": {"id": {"type": "string"}}} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | org.apache.camel.model.errorhandler.RefErrorHandlerDefinition | References to an existing or custom error handler. | {"oneOf": [{"type": "string"}, {"type": "object", "properties": {"id": {"type": "string"}, "ref": {"type": "string"}}}], "required": ["ref"]} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | ref | References to an existing or custom error handler. | {"type": "string"} |
camel-yaml-dsl.json | org.apache.camel.model.errorhandler.SpringTransactionErrorHandlerDefinition | Spring based transactional error handler (requires camel-spring). | {"type": "object", "properties": {"executor-service-ref": {"type": "string"}, "id": {"type": "string"}, "level": {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]}, "log-name": {"type": "string"}, "logger-ref": {"type": "string"}, "on-exception-occurred-ref": {"type": "string"}, "on-prepare-failure-ref": {"type": "string"}, "on-redelivery-ref": {"type": "string"}, "redelivery-policy": {}, "redelivery-policy-ref": {"type": "string"}, "retry-while-ref": {"type": "string"}, "rollback-logging-level": {"type": "string", "default": "WARN", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]}, "transacted-policy-ref": {"type": "string"}, "use-original-body": {"type": "boolean"}, "use-original-message": {"type": "boolean"}}} |
camel-yaml-dsl.json | executor-service-ref | Sets a reference to a thread pool to be used by the error handler | {"type": "string"} |
camel-yaml-dsl.json | id | The id of this node | {"type": "string"} |
camel-yaml-dsl.json | level | Logging level to use when using the logging error handler type. | {"type": "string", "default": "ERROR", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]} |
camel-yaml-dsl.json | log-name | Name of the logger to use for the logging error handler | {"type": "string"} |
camel-yaml-dsl.json | logger-ref | References to a logger to use as logger for the error handler | {"type": "string"} |
camel-yaml-dsl.json | on-exception-occurred-ref | Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom logging about the occurred exception at the exact time it happened. Important: Any exception thrown from this processor will be ignored. | {"type": "string"} |
camel-yaml-dsl.json | on-prepare-failure-ref | Sets a reference to a processor to prepare the org.apache.camel.Exchange before handled by the failure processor / dead letter channel. This allows for example to enrich the message before sending to a dead letter queue. | {"type": "string"} |
camel-yaml-dsl.json | on-redelivery-ref | Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the org.apache.camel.Exchange before its being redelivered. | {"type": "string"} |
camel-yaml-dsl.json | redelivery-policy | Sets the redelivery settings | {} |
camel-yaml-dsl.json | redelivery-policy-ref | Sets a reference to a RedeliveryPolicy to be used for redelivery settings. | {"type": "string"} |
camel-yaml-dsl.json | retry-while-ref | Sets a retry while predicate. Will continue retrying until the predicate evaluates to false. | {"type": "string"} |
camel-yaml-dsl.json | rollback-logging-level | Sets the logging level to use for logging transactional rollback. This option is default WARN. | {"type": "string", "default": "WARN", "enum": ["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF"]} |
camel-yaml-dsl.json | transacted-policy-ref | The transacted policy to use that is configured for either Spring or JTA based transactions. If no policy has been configured then Camel will attempt to auto-discover. | {"type": "string"} |
camel-yaml-dsl.json | use-original-body | Will use the original input org.apache.camel.Message body (original body only) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | use-original-message | Will use the original input org.apache.camel.Message (original body and headers) when an org.apache.camel.Exchange is moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN message we use the original IN message instead. This allows you to store the original input in the dead letter queue instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that the former includes both the original body and headers, where as the latter only includes the original body. You can use the latter to enrich the message with custom headers and include the original message body. The former wont let you do this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and useOriginalBody. The original input message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and therefore use the parent original message. By default this feature is off. | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.language.CSimpleExpression | Evaluate a compiled simple expression. | {"oneOf": [{"type": "string"}, {"type": "object", "properties": {"expression": {"type": "string"}, "id": {"type": "string"}, "result-type": {"type": "string"}, "trim": {"type": "boolean"}}}], "required": ["expression"]} |
camel-yaml-dsl.json | expression | The expression value in your chosen language syntax | {"type": "string"} |
camel-yaml-dsl.json | id | Sets the id of this node | {"type": "string"} |
camel-yaml-dsl.json | result-type | Sets the class of the result type (type from output) | {"type": "string"} |
camel-yaml-dsl.json | trim | Whether to trim the value to remove leading and trailing whitespaces and line breaks | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.language.ConstantExpression | A fixed value set only once during the route startup. | {"oneOf": [{"type": "string"}, {"type": "object", "properties": {"expression": {"type": "string"}, "id": {"type": "string"}, "result-type": {"type": "string"}, "trim": {"type": "boolean"}}}], "required": ["expression"]} |
camel-yaml-dsl.json | expression | The expression value in your chosen language syntax | {"type": "string"} |
camel-yaml-dsl.json | id | Sets the id of this node | {"type": "string"} |
camel-yaml-dsl.json | result-type | Sets the class of the result type (type from output) | {"type": "string"} |
camel-yaml-dsl.json | trim | Whether to trim the value to remove leading and trailing whitespaces and line breaks | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.language.DatasonnetExpression | To use DataSonnet scripts for message transformations. | {"oneOf": [{"type": "string"}, {"type": "object", "properties": {"body-media-type": {"type": "string"}, "expression": {"type": "string"}, "id": {"type": "string"}, "output-media-type": {"type": "string"}, "result-type": {"type": "string"}, "trim": {"type": "boolean"}}}], "required": ["expression"]} |
camel-yaml-dsl.json | body-media-type | The String representation of the message's body MediaType | {"type": "string"} |
camel-yaml-dsl.json | expression | The expression value in your chosen language syntax | {"type": "string"} |
camel-yaml-dsl.json | id | Sets the id of this node | {"type": "string"} |
camel-yaml-dsl.json | output-media-type | The String representation of the MediaType to output | {"type": "string"} |
camel-yaml-dsl.json | result-type | Sets the class of the result type (type from output) | {"type": "string"} |
camel-yaml-dsl.json | trim | Whether to trim the value to remove leading and trailing whitespaces and line breaks | {"type": "boolean"} |
camel-yaml-dsl.json | org.apache.camel.model.language.ExchangePropertyExpression | Gets a property from the Exchange. | {"oneOf": [{"type": "string"}, {"type": "object", "properties": {"expression": {"type": "string"}, "id": {"type": "string"}, "trim": {"type": "boolean"}}}], "required": ["expression"]} |
camel-yaml-dsl.json | expression | The expression value in your chosen language syntax | {"type": "string"} |
camel-yaml-dsl.json | id | Sets the id of this node | {"type": "string"} |
camel-yaml-dsl.json | trim | Whether to trim the value to remove leading and trailing whitespaces and line breaks | {"type": "boolean"} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.