docs/modules/ROOT/pages/reference/extensions/jolt.adoc

// Do not edit directly!
// This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page
= JOLT
:page-aliases: extensions/jolt.adoc
:linkattrs:
:cq-artifact-id: camel-quarkus-jolt
:cq-native-supported: true
:cq-status: Stable
:cq-status-deprecation: Stable
:cq-description: JSON to JSON transformation using JOLT.
:cq-deprecated: false
:cq-jvm-since: 1.0.0
:cq-native-since: 1.0.0

[.badges]
[.badge-key]##JVM since##[.badge-supported]##1.0.0## [.badge-key]##Native since##[.badge-supported]##1.0.0##

JSON to JSON transformation using JOLT.

== What's inside

* xref:{cq-camel-components}::jolt-component.adoc[JOLT component], URI syntax: `jolt:resourceUri`

Please refer to the above link for usage and configuration details.

== Maven coordinates

https://code.quarkus.io/?extension-search=camel-quarkus-jolt[Create a new project with this extension on code.quarkus.io, window="_blank"]

Or add the coordinates to your existing project:

[source,xml]
----
<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-jolt</artifactId>
</dependency>
----

Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.

== allowContextMapAll option in native mode

The `allowContextMapAll` option is not supported in native mode as it requires reflective access to security sensitive camel core classes such as
`CamelContext` & `Exchange`. This is considered a security risk and thus access to the feature is not provided by default.

== Additional Camel Quarkus configuration

This component typically loads its specs from classpath resources.
To make it work also in native mode, you need to explicitly embed the spec files in the native executable
by using the `quarkus.native.resources.includes` property.

For instance, the route below would load the Jolt spec from a classpath resource named `defaultr.json`:

[source,java]
----
from("direct:start").to("jolt:defaultr.json");
----

To include this (an possibly other specs stored in `.json` files) in the native image, you would have to add something like the following to your `application.properties` file:

[source,properties]
----
quarkus.native.resources.includes = *.json
----

More information about selecting resources for inclusion in the native executable can be found at xref:user-guide/native-mode.adoc#embedding-resource-in-native-executable[Embedding resource in native executable].