Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

Chapter 171. JOLT Component

Available as of Camel version 2.16

The jolt: component allows you to process a JSON messages using an JOLT specification. This can be ideal when doing JSON to JSON transformation.

Maven users will need to add the following dependency to their pom.xml for this component: 

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-jolt</artifactId>
    <version>x.x.x</version>
    <!-- use the same version as your Camel core version -->
</dependency>
Copy to Clipboard Toggle word wrap

 

171.1. URI format
Copia collegamento

jolt:specName[?options]
Copy to Clipboard Toggle word wrap

Where specName is the classpath-local URI of the specification to invoke; or the complete URL of the remote specification (eg: file://folder/myfile.json).

You can append query options to the URI in the following format, ?option=value&option=value&…​

171.2. Options
Copia collegamento

The JOLT component supports 2 options which are listed below.

Expand
NameDescriptionDefaultType

transform (advanced)

Explicitly sets the Transform to use. If not set a Transform specified by the transformDsl will be created

 

Transform

resolveProperty Placeholders (advanced)

Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.

true

boolean

The JOLT endpoint is configured using URI syntax: 

jolt:resourceUri
Copy to Clipboard Toggle word wrap

with the following path and query parameters:

171.2.1. Path Parameters (1 parameters):
Copia collegamento

Expand
NameDescriptionDefaultType

resourceUri

Required Path to the resource. You can prefix with: classpath, file, http, ref, or bean. classpath, file and http loads the resource using these protocols (classpath is default). ref will lookup the resource in the registry. bean will call a method on a bean to be used as the resource. For bean you can specify the method name after dot, eg bean:myBean.myMethod.

 

String

171.2.2. Query Parameters (5 parameters):
Copia collegamento

Expand
NameDescriptionDefaultType

contentCache (producer)

Sets whether to use resource content cache or not

false

boolean

inputType (producer)

Specifies if the input is hydrated JSON or a JSON String.

Hydrated

JoltInputOutputType

outputType (producer)

Specifies if the output should be hydrated JSON or a JSON String.

Hydrated

JoltInputOutputType

transformDsl (producer)

Specifies the Transform DSL of the endpoint resource. If none is specified Chainr will be used.

Chainr

JoltTransformType

synchronous (advanced)

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

false

boolean

171.3. Samples
Copia collegamento

For example you could use something like 

from("activemq:My.Queue").
  to("jolt:com/acme/MyResponse.json");
Copy to Clipboard Toggle word wrap

And a file based resource: 

from("activemq:My.Queue").
  to("jolt:file://myfolder/MyResponse.json?contentCache=true").
  to("activemq:Another.Queue");
Copy to Clipboard Toggle word wrap

You can also specify what specification the component should use dynamically via a header, so for example: 

from("direct:in").
  setHeader("CamelJoltResourceUri").constant("path/to/my/spec.json").
  to("jolt:dummy");
Copy to Clipboard Toggle word wrap

 

171.4. See Also
Copia collegamento

  • Configuring Camel
  • Component
  • Endpoint
  • Getting Started
Torna in cima
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2025 Red Hat