JOLT

JVM since1.0.0 Native since1.0.0

JSON to JSON transformation using JOLT.

What’s inside

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

Maven coordinates

Create a new project with this extension on code.quarkus.io

Or add the coordinates to your existing project:

<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-jolt</artifactId>
</dependency>

Check the 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:

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:

quarkus.native.resources.includes = *.json

More information about selecting resources for inclusion in the native executable can be found at Embedding resource in native executable.

Back to top