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

<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

Beyond standard usages described above, a trick is needed when using jolt specs from classpath resources in native mode. In such a situation, one needs to explicitly embed the resources in the native executable by specifying the include-patterns option.

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

from("direct:start").to("jolt:defaultr.json");

In order to work in native mode the include-patterns configuration should be set. For instance, in the application.properties file as below :

quarkus.camel.native.resources.include-patterns = *.json

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

Back to top