This is an automated email from the ASF dual-hosted git repository. apupier pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
commit d0c07819c4befeb9d0392380b1ab0863ff4cfbae Author: Sanjana <[email protected]> AuthorDate: Fri Feb 6 14:44:06 2026 +0530 Restore accidentally truncated core.adoc --- .../ROOT/pages/reference/extensions/core.adoc | 406 +++++++++++++++++++++ 1 file changed, 406 insertions(+) diff --git a/docs/modules/ROOT/pages/reference/extensions/core.adoc b/docs/modules/ROOT/pages/reference/extensions/core.adoc index db73e5ab49..9a9aa274f9 100644 --- a/docs/modules/ROOT/pages/reference/extensions/core.adoc +++ b/docs/modules/ROOT/pages/reference/extensions/core.adoc @@ -124,3 +124,409 @@ camel.beans.customBeanWithSetterInjection.counter = 123 As such, the class `PropertiesCustomBeanWithSetterInjection` needs to be link:https://quarkus.io/guides/writing-native-applications-tips#registering-for-reflection[registered for reflection], note that field access could be omitted in this case. + +[width="100%",cols="80,5,15",options="header"] +|=== +| Configuration property | Type | Default + + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-service-discovery-exclude-patterns]]`link:#quarkus-camel-service-discovery-exclude-patterns[quarkus.camel.service.discovery.exclude-patterns]` + +A comma-separated list of Ant-path style patterns to match Camel service definition files in the classpath. The +services defined in the matching files will *not* be discoverable via the **`org.apache.camel.spi.FactoryFinder` +mechanism. + +The excludes have higher precedence than includes. The excludes defined here can also be used to veto the +discoverability of services included by Camel Quarkus extensions. + +Example values: `META-INF/services/org/apache/camel/foo/++*++,META-INF/services/org/apache/camel/foo/++**++/bar` +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-service-discovery-include-patterns]]`link:#quarkus-camel-service-discovery-include-patterns[quarkus.camel.service.discovery.include-patterns]` + +A comma-separated list of Ant-path style patterns to match Camel service definition files in the classpath. The +services defined in the matching files will be discoverable via the `org.apache.camel.spi.FactoryFinder` mechanism +unless the given file is excluded via `exclude-patterns`. + +Note that Camel Quarkus extensions may include some services by default. The services selected here added to those +services and the exclusions defined in `exclude-patterns` are applied to the union set. + +Example values: `META-INF/services/org/apache/camel/foo/++*++,META-INF/services/org/apache/camel/foo/++**++/bar` +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-service-registry-exclude-patterns]]`link:#quarkus-camel-service-registry-exclude-patterns[quarkus.camel.service.registry.exclude-patterns]` + +A comma-separated list of Ant-path style patterns to match Camel service definition files in the classpath. The +services defined in the matching files will *not* be added to Camel registry during application's static +initialization. + +The excludes have higher precedence than includes. The excludes defined here can also be used to veto the +registration of services included by Camel Quarkus extensions. + +Example values: `META-INF/services/org/apache/camel/foo/++*++,META-INF/services/org/apache/camel/foo/++**++/bar`** +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-service-registry-include-patterns]]`link:#quarkus-camel-service-registry-include-patterns[quarkus.camel.service.registry.include-patterns]` + +A comma-separated list of Ant-path style patterns to match Camel service definition files in the classpath. The +services defined in the matching files will be added to Camel registry during application's static initialization +unless the given file is excluded via `exclude-patterns`. + +Note that Camel Quarkus extensions may include some services by default. The services selected here added to those +services and the exclusions defined in `exclude-patterns` are applied to the union set. + +Example values: `META-INF/services/org/apache/camel/foo/++*++,META-INF/services/org/apache/camel/foo/++**++/bar` +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-runtime-catalog-components]]`link:#quarkus-camel-runtime-catalog-components[quarkus.camel.runtime-catalog.components]` + +If `true` the Runtime Camel Catalog embedded in the application will contain JSON schemas of Camel components +available in the application; otherwise component JSON schemas will not be available in the Runtime Camel Catalog and +any attempt to access those will result in a RuntimeException. + +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `false` except for making the behavior consistent with native mode. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-runtime-catalog-languages]]`link:#quarkus-camel-runtime-catalog-languages[quarkus.camel.runtime-catalog.languages]` + +If `true` the Runtime Camel Catalog embedded in the application will contain JSON schemas of Camel languages +available in the application; otherwise language JSON schemas will not be available in the Runtime Camel Catalog and +any attempt to access those will result in a RuntimeException. + +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `false` except for making the behavior consistent with native mode. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-runtime-catalog-dataformats]]`link:#quarkus-camel-runtime-catalog-dataformats[quarkus.camel.runtime-catalog.dataformats]` + +If `true` the Runtime Camel Catalog embedded in the application will contain JSON schemas of Camel data formats +available in the application; otherwise data format JSON schemas will not be available in the Runtime Camel Catalog +and any attempt to access those will result in a RuntimeException. + +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `false` except for making the behavior consistent with native mode. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-runtime-catalog-devconsoles]]`link:#quarkus-camel-runtime-catalog-devconsoles[quarkus.camel.runtime-catalog.devconsoles]` + +If `true` the Runtime Camel Catalog embedded in the application will contain JSON schemas of Camel dev consoles +available in the application; otherwise dev console JSON schemas will not be available in the Runtime Camel Catalog +and any attempt to access those will result in a RuntimeException. + +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `false` except for making the behavior consistent with native mode. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-runtime-catalog-models]]`link:#quarkus-camel-runtime-catalog-models[quarkus.camel.runtime-catalog.models]` + +If `true` the Runtime Camel Catalog embedded in the application will contain JSON schemas of Camel EIP models +available in the application; otherwise EIP model JSON schemas will not be available in the Runtime Camel Catalog and +any attempt to access those will result in a RuntimeException. + +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `false` except for making the behavior consistent with native mode. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-runtime-catalog-transformers]]`link:#quarkus-camel-runtime-catalog-transformers[quarkus.camel.runtime-catalog.transformers]` + +If `true` the Runtime Camel Catalog embedded in the application will contain JSON schemas of Camel transformers +available in the application; otherwise transformer JSON schemas will not be available in the Runtime Camel Catalog +and any attempt to access those will result in a RuntimeException. + +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `false` except for making the behavior consistent with native mode. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-routes-discovery-exclude-patterns]]`link:#quarkus-camel-routes-discovery-exclude-patterns[quarkus.camel.routes-discovery.exclude-patterns]` + +Used for exclusive filtering scanning of RouteBuilder classes. The exclusive filtering takes precedence over +inclusive filtering. The pattern is using Ant-path style pattern. Multiple patterns can be specified separated by +comma. For example to exclude all classes starting with Bar use: ++**++/Bar++*++ To exclude all routes from a +specific package use: com/mycompany/bar/++*++ To exclude all routes from a specific package and its sub-packages use +double wildcards: com/mycompany/bar/++**++ And to exclude all routes from two specific packages use: +com/mycompany/bar/++*++,com/mycompany/stuff/++*++ +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-routes-discovery-include-patterns]]`link:#quarkus-camel-routes-discovery-include-patterns[quarkus.camel.routes-discovery.include-patterns]` + +Used for inclusive filtering scanning of RouteBuilder classes. The exclusive filtering takes precedence over +inclusive filtering. The pattern is using Ant-path style pattern. Multiple patterns can be specified separated by +comma. For example to include all classes starting with Foo use: ++**++/Foo++*++ To include all routes from a +specific package use: com/mycompany/foo/++*++ To include all routes from a specific package and its sub-packages use +double wildcards: com/mycompany/foo/++**++ And to include all routes from two specific packages use: +com/mycompany/foo/++*++,com/mycompany/stuff/++*++ +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-native-reflection-exclude-patterns]]`link:#quarkus-camel-native-reflection-exclude-patterns[quarkus.camel.native.reflection.exclude-patterns]` + +A comma separated list of Ant-path style patterns to match class names that should be *excluded* from registering for +reflection. Use the class name format as returned by the `java.lang.Class.getName()` method: package segments +delimited by period `.` and inner classes by dollar sign `$`. + +This option narrows down the set selected by `include-patterns`. By default, no classes are excluded. + +This option cannot be used to unregister classes which have been registered internally by Quarkus extensions. +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-native-reflection-include-patterns]]`link:#quarkus-camel-native-reflection-include-patterns[quarkus.camel.native.reflection.include-patterns]` + +A comma separated list of Ant-path style patterns to match class names that should be registered for reflection. Use +the class name format as returned by the `java.lang.Class.getName()` method: package segments delimited by period `.` +and inner classes by dollar sign `$`. + +By default, no classes are included. The set selected by this option can be narrowed down by `exclude-patterns`. + +Note that Quarkus extensions typically register the required classes for reflection by themselves. This option is +useful in situations when the built in functionality is not sufficient. + +Note that this option enables the full reflective access for constructors, fields and methods. If you need a finer +grained control, consider using `io.quarkus.runtime.annotations.RegisterForReflection` annotation in your Java code. + +For this option to work properly, at least one of the following conditions must be satisfied: + +- There are no wildcards (`++*++` or `/`) in the patterns +- The artifacts containing the selected classes contain a Jandex index (`META-INF/jandex.idx`) +- The artifacts containing the selected classes are registered for indexing using the +`quarkus.index-dependency.++*++` family of options in `application.properties` - e.g. + +[source,properties] +---- +quarkus.index-dependency.my-dep.group-id = org.my-group +quarkus.index-dependency.my-dep.artifact-id = my-artifact +---- + +where `my-dep` is a label of your choice to tell Quarkus that `org.my-group` and with `my-artifact` belong together. +| List of `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-native-reflection-serialization-enabled]]`link:#quarkus-camel-native-reflection-serialization-enabled[quarkus.camel.native.reflection.serialization-enabled]` + +If `true`, basic classes are registered for serialization; otherwise basic classes won't be registered automatically +for serialization in native mode. The list of classes automatically registered for serialization can be found in +link:https://github.com/apache/camel-quarkus/blob/main/extensions-core/core/deployment/src/main/java/org/apache/camel/quarkus/core/deployment/CamelSerializationProcessor.java[CamelSerializationProcessor.BASE_SERIALIZATION_CLASSES]. +Setting this to `false` helps to reduce the size of the native image. In JVM mode, there is no real benefit of +setting this flag to `true` except for making the behavior consistent with native mode. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-expression-on-build-time-analysis-failure]]`link:#quarkus-camel-expression-on-build-time-analysis-failure[quarkus.camel.expression.on-build-time-analysis-failure]` + +What to do if it is not possible to extract expressions from a route definition at build time. +| `fail`, `warn`, `ignore` +| `warn` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-expression-extraction-enabled]]`link:#quarkus-camel-expression-extraction-enabled[quarkus.camel.expression.extraction-enabled]` + +Indicates whether the expression extraction from the route definitions at build time must be done. If disabled, the +expressions are compiled at runtime. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-event-bridge-enabled]]`link:#quarkus-camel-event-bridge-enabled[quarkus.camel.event-bridge.enabled]` + +Whether to enable the bridging of Camel events to CDI events. + +This allows CDI observers to be configured for Camel events. E.g. those belonging to the +`org.apache.camel.quarkus.core.events`, `org.apache.camel.quarkus.main.events` & `org.apache.camel.impl.event` +packages. + +Note that this configuration item only has any effect when observers configured for Camel events are present in the +application. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-source-location-enabled]]`link:#quarkus-camel-source-location-enabled[quarkus.camel.source-location-enabled]` + +Build time configuration options for enable/disable camel source location. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-enabled]]`link:#quarkus-camel-trace-enabled[quarkus.camel.trace.enabled]` + +Enables tracer in your Camel application. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-standby]]`link:#quarkus-camel-trace-standby[quarkus.camel.trace.standby]` + +To set the tracer in standby mode, where the tracer will be installed, but not automatically enabled. The tracer can +then be enabled explicitly later from Java, JMX or tooling. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-backlog-size]]`link:#quarkus-camel-trace-backlog-size[quarkus.camel.trace.backlog-size]` + +Defines how many of the last messages to keep in the tracer. +| `int` +| `1000` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-remove-on-dump]]`link:#quarkus-camel-trace-remove-on-dump[quarkus.camel.trace.remove-on-dump]` + +Whether all traced messages should be removed when the tracer is dumping. By default, the messages are removed, which +means that dumping will not contain previous dumped messages. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-body-max-chars]]`link:#quarkus-camel-trace-body-max-chars[quarkus.camel.trace.body-max-chars]` + +To limit the message body to a maximum size in the traced message. Use 0 or negative value to use unlimited size. +| `int` +| `131072` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-body-include-streams]]`link:#quarkus-camel-trace-body-include-streams[quarkus.camel.trace.body-include-streams]` + +Whether to include the message body of stream based messages. If enabled then beware the stream may not be +re-readable later. See more about Stream Caching. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-body-include-files]]`link:#quarkus-camel-trace-body-include-files[quarkus.camel.trace.body-include-files]` + +Whether to include the message body of file based messages. The overhead is that the file content has to be read from +the file. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-include-exchange-properties]]`link:#quarkus-camel-trace-include-exchange-properties[quarkus.camel.trace.include-exchange-properties]` + +Whether to include the exchange properties in the traced message. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-include-exchange-variables]]`link:#quarkus-camel-trace-include-exchange-variables[quarkus.camel.trace.include-exchange-variables]` + +Whether to include the exchange variables in the traced message. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-include-exception]]`link:#quarkus-camel-trace-include-exception[quarkus.camel.trace.include-exception]` + +Whether to include the exception in the traced message in case of failed exchange. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-trace-rests]]`link:#quarkus-camel-trace-trace-rests[quarkus.camel.trace.trace-rests]` + +Whether to trace routes that is created from Rest DSL. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-trace-templates]]`link:#quarkus-camel-trace-trace-templates[quarkus.camel.trace.trace-templates]` + +Whether to trace routes that is created from route templates or kamelets. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-trace-pattern]]`link:#quarkus-camel-trace-trace-pattern[quarkus.camel.trace.trace-pattern]` + +Filter for tracing by route or node id. +| `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-trace-trace-filter]]`link:#quarkus-camel-trace-trace-filter[quarkus.camel.trace.trace-filter]` + +Filter for tracing messages. +| `string` +| + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-type-converter-statistics-enabled]]`link:#quarkus-camel-type-converter-statistics-enabled[quarkus.camel.type-converter.statistics-enabled]` + +Whether type converter statistics are enabled. By default, type converter utilization statistics are disabled. Note +that enabling statistics incurs a minor performance impact under very heavy load. +| `boolean` +| `false` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-dev-ui-update-interval]]`link:#quarkus-camel-dev-ui-update-interval[quarkus.camel.dev-ui.update-interval]` + +The interval at which data is updated in Camel Quarkus Dev UI pages. +| link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[`Duration`] link:#duration-note-anchor-core[icon:question-circle[title=More information about the Duration format]] +| `5S` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-main-shutdown-timeout]]`link:#quarkus-camel-main-shutdown-timeout[quarkus.camel.main.shutdown.timeout]` + +A timeout (with millisecond precision) to wait for `CamelMain++#++stop()` to finish +| link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[`Duration`] link:#duration-note-anchor-core[icon:question-circle[title=More information about the Duration format]] +| `PT3S` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-main-arguments-on-unknown]]`link:#quarkus-camel-main-arguments-on-unknown[quarkus.camel.main.arguments.on-unknown]` + +The action to take when `CamelMain` encounters an unknown argument. fail - Prints the `CamelMain` usage statement and +throws a `RuntimeException` ignore - Suppresses any warnings and the application startup proceeds as normal warn - +Prints the `CamelMain` usage statement but allows the application startup to proceed as normal +| `fail`, `warn`, `ignore` +| `warn` + +a| [[camel-dataformat-data-format-configs]]`link:#camel-dataformat-data-format-configs[camel.dataformat."data-format-configs"]` + +Camel data format configuration. + +The format of the configuration is as follows. + +[source,properties] +---- +camel.dataformat.<name>.<property> = value +---- + +For example. +[source,properties] +---- +camel.dataformat.beanio.stream-name = test-stream +camel.dataformat.beanio.mapping = test-mapping.xml +---- +| `Map<String,Map<String,String>>` +| + +a| [[quarkus-camel-bootstrap-enabled]]`link:#quarkus-camel-bootstrap-enabled[quarkus.camel.bootstrap.enabled]` + +When set to true, the {@link CamelRuntime} will be started automatically. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-routes-discovery-enabled]]`link:#quarkus-camel-routes-discovery-enabled[quarkus.camel.routes-discovery.enabled]` + +Enable automatic discovery of routes during static initialization. +| `boolean` +| `true` + +a|icon:lock[title=Fixed at build time] [[quarkus-camel-csimple-on-build-time-analysis-failure]]`link:#quarkus-camel-csimple-on-build-time-analysis-failure[quarkus.camel.csimple.on-build-time-analysis-failure]` + +What to do if it is not possible to extract CSimple expressions from a route definition at build time. +| `fail`, `warn`, `ignore` +| `warn` +|=== + +[.configuration-legend] +{doc-link-icon-lock}[title=Fixed at build time] Configuration property fixed at build time. All other configuration properties are overridable at runtime. + +[NOTE] +[id=duration-note-anchor-core] +.About the Duration format +==== +To write duration values, use the standard `java.time.Duration` format. +See the link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html#parse(java.lang.CharSequence)[Duration#parse() Java API documentation] for more information. + +You can also use a simplified format, starting with a number: + +* If the value is only a number, it represents time in seconds. +* If the value is a number followed by `ms`, it represents time in milliseconds. + +In other cases, the simplified format is translated to the `java.time.Duration` format for parsing: + +* If the value is a number followed by `h`, `m`, or `s`, it is prefixed with `PT`. +* If the value is a number followed by `d`, it is prefixed with `P`. +==== +
