This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 2bcf86d083efd3a257b6ee867d25d0f22d975641
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Aug 24 16:56:39 2021 +0200
CAMEL-13590 First version json-patch component - added docs
---
.../src/main/docs/json-patch-component.adoc | 198 ++++++++++++++++++++
.../modules/ROOT/pages/json-patch-component.adoc | 200 +++++++++++++++++++++
2 files changed, 398 insertions(+)
diff --git
a/components/camel-json-patch/src/main/docs/json-patch-component.adoc
b/components/camel-json-patch/src/main/docs/json-patch-component.adoc
new file mode 100644
index 0000000..9727f55
--- /dev/null
+++ b/components/camel-json-patch/src/main/docs/json-patch-component.adoc
@@ -0,0 +1,198 @@
+[[json-patch-component]]
+= JsonPatch Component
+:docTitle: JsonPatch
+:artifactId: camel-json-patch
+:description: JsonPatch component which transform JSON using JSON patch (RFC
6902).
+:since: 3.12.0-SNAPSHOT
+:supportLevel: Preview
+:component-header: Only producer is supported
+include::{cq-version}@camel-quarkus:ROOT:partial$reference/components/json-patch.adoc[opts=optional]
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The Jslt component allows you to process a JSON messages using an
+https://github.com/schibsted/jslt[JSLT] expression. This can be
+ideal when doing JSON to JSON transformation or querying data.
+
+Maven users will need to add the following dependency to
+their `pom.xml` for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-json-patch</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+
+== URI format
+
+-----------------------
+json-patch:resourceUri[?options]
+-----------------------
+
+Where *specName* is the classpath-local URI of the specification to
+invoke; or the complete URL of the remote specification
+(eg: \file://folder/myfile.vm).
+
+
+// component-configure options: START
+== Configuring Options
+
+Camel components are configured on two separate levels:
+
+- component level
+- endpoint level
+
+=== Configuring Component Options
+
+The component level is the highest level which holds general and common
configurations that are inherited by the endpoints.
+For example a component may have security settings, credentials for
authentication, urls for network connection and so forth.
+
+Some components only have a few options, and others may have many. Because
components typically have pre configured defaults
+that are commonly used, then you may often only need to configure a few
options on a component; or none at all.
+
+Configuring components can be done with the
xref:latest@manual::component-dsl.adoc[Component DSL],
+in a configuration file (application.properties|yaml), or directly with Java
code.
+
+=== Configuring Endpoint Options
+
+Where you find yourself configuring the most is on endpoints, as endpoints
often have many options, which allows you to
+configure what you need the endpoint to do. The options are also categorized
into whether the endpoint is used as consumer (from)
+or as a producer (to), or used for both.
+
+Configuring endpoints is most often done directly in the endpoint URI as path
and query parameters. You can also use
+the xref:latest@manual::Endpoint-dsl.adoc[Endpoint DSL] as a _type safe_ way
of configuring endpoints.
+
+A good practice when configuring options is to use
xref:latest@manual::using-propertyplaceholder.adoc[Property Placeholders],
+which allows to not hardcode urls, port numbers, sensitive information, and
other settings.
+In other words placeholders allows to externalize the configuration from your
code, and gives more flexibility and reuse.
+
+The following two sections lists all the options, firstly for the component
followed by the endpoint.
+// component-configure options: END
+
+// component options: START
+== Component Options
+
+
+The JsonPatch component supports 2 options, which are listed below.
+
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
+| *autowiredEnabled* (advanced) | Whether autowiring is enabled. This is used
for automatic autowiring options (the option must be marked as autowired) by
looking up in the registry to find if there is a single instance of matching
type, which then gets configured on the component. This can be used for
automatic configuring JDBC data sources, JMS connection factories, AWS Clients,
etc. | true | boolean
+|===
+// component options: END
+
+// endpoint options: START
+== Endpoint Options
+
+The JsonPatch endpoint is configured using URI syntax:
+
+----
+json-patch:resourceUri
+----
+
+with the following path and query parameters:
+
+=== Path Parameters (1 parameters):
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *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
+|===
+
+
+=== Query Parameters (3 parameters):
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *allowContextMapAll* (producer) | Sets whether the context map should allow
access to all details. By default only the message body and headers can be
accessed. This option can be enabled for full access to the current Exchange
and CamelContext. Doing so impose a potential security risk as this opens
access to the full power of CamelContext API. | false | boolean
+| *contentCache* (producer) | Sets whether to use resource content cache or
not | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
+|===
+// endpoint options: END
+
+
+== Passing values to JSLT
+
+Camel can supply exchange information as variables when applying a JSLT
expression on the body. The available variables from the *Exchange* are:
+
+[width="100%",cols="2,5",options="header"]
+|===
+| name | value
+| headers | The headers of the In message as a json object
+| exchange.properties | The *Exchange* properties as a json object. _exchange_
is the name of the variable and _properties_ is the path to the exchange
properties. Available if _allowContextMapAll_ option is true.
+|===
+
+All the values that cannot be converted to json with Jackson are denied and
will not be available in the jslt expression.
+
+For example, the header named "type" and the exchange property "instance" can
be accessed like
+
+[source,json]
+--------------------------------------
+{
+ "type": $headers.type,
+ "instance": $exchange.properties.instance
+}
+--------------------------------------
+
+== Samples
+
+For example you could use something like
+
+[source,java]
+--------------------------------------
+from("activemq:My.Queue").
+ to("jslt:com/acme/MyResponse.json");
+--------------------------------------
+
+And a file based resource:
+
+[source,java]
+---------------------------------------------------------------
+from("activemq:My.Queue").
+ to("jslt:file://myfolder/MyResponse.json?contentCache=true").
+ to("activemq:Another.Queue");
+---------------------------------------------------------------
+
+You can also specify which JSLT expression the component should use
+dynamically via a header, so for example:
+
+[source,java]
+---------------------------------------------------------------------
+from("direct:in").
+ setHeader("CamelJsltResourceUri").constant("path/to/my/spec.json").
+ to("jslt:dummy?allowTemplateFromHeader=true");
+---------------------------------------------------------------------
+
+Or send whole jslt expression via header: (suitable for querying)
+
+[source,java]
+---------------------------------------------------------------------
+from("direct:in").
+ setHeader("CamelJsltString").constant(".published").
+ to("jslt:dummy?allowTemplateFromHeader=true");
+---------------------------------------------------------------------
+
+Passing exchange properties to the jslt expression can be done like this
+
+[source,java]
+---------------------------------------------------------------------
+from("direct:in").
+ to("jslt:com/acme/MyResponse.json?allowContextMapAll=true");
+---------------------------------------------------------------------
+
+include::{page-component-version}@camel-spring-boot::page$jslt-starter.adoc[]
diff --git a/docs/components/modules/ROOT/pages/json-patch-component.adoc
b/docs/components/modules/ROOT/pages/json-patch-component.adoc
new file mode 100644
index 0000000..ee6afa4
--- /dev/null
+++ b/docs/components/modules/ROOT/pages/json-patch-component.adoc
@@ -0,0 +1,200 @@
+[[json-patch-component]]
+= JsonPatch Component
+//THIS FILE IS COPIED: EDIT THE SOURCE FILE:
+:page-source:
components/camel-json-patch/src/main/docs/json-patch-component.adoc
+:docTitle: JsonPatch
+:artifactId: camel-json-patch
+:description: JsonPatch component which transform JSON using JSON patch (RFC
6902).
+:since: 3.12.0-SNAPSHOT
+:supportLevel: Preview
+:component-header: Only producer is supported
+include::{cq-version}@camel-quarkus:ROOT:partial$reference/components/json-patch.adoc[opts=optional]
+
+*Since Camel {since}*
+
+*{component-header}*
+
+The Jslt component allows you to process a JSON messages using an
+https://github.com/schibsted/jslt[JSLT] expression. This can be
+ideal when doing JSON to JSON transformation or querying data.
+
+Maven users will need to add the following dependency to
+their `pom.xml` for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-json-patch</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+
+== URI format
+
+-----------------------
+json-patch:resourceUri[?options]
+-----------------------
+
+Where *specName* is the classpath-local URI of the specification to
+invoke; or the complete URL of the remote specification
+(eg: \file://folder/myfile.vm).
+
+
+// component-configure options: START
+== Configuring Options
+
+Camel components are configured on two separate levels:
+
+- component level
+- endpoint level
+
+=== Configuring Component Options
+
+The component level is the highest level which holds general and common
configurations that are inherited by the endpoints.
+For example a component may have security settings, credentials for
authentication, urls for network connection and so forth.
+
+Some components only have a few options, and others may have many. Because
components typically have pre configured defaults
+that are commonly used, then you may often only need to configure a few
options on a component; or none at all.
+
+Configuring components can be done with the
xref:latest@manual::component-dsl.adoc[Component DSL],
+in a configuration file (application.properties|yaml), or directly with Java
code.
+
+=== Configuring Endpoint Options
+
+Where you find yourself configuring the most is on endpoints, as endpoints
often have many options, which allows you to
+configure what you need the endpoint to do. The options are also categorized
into whether the endpoint is used as consumer (from)
+or as a producer (to), or used for both.
+
+Configuring endpoints is most often done directly in the endpoint URI as path
and query parameters. You can also use
+the xref:latest@manual::Endpoint-dsl.adoc[Endpoint DSL] as a _type safe_ way
of configuring endpoints.
+
+A good practice when configuring options is to use
xref:latest@manual::using-propertyplaceholder.adoc[Property Placeholders],
+which allows to not hardcode urls, port numbers, sensitive information, and
other settings.
+In other words placeholders allows to externalize the configuration from your
code, and gives more flexibility and reuse.
+
+The following two sections lists all the options, firstly for the component
followed by the endpoint.
+// component-configure options: END
+
+// component options: START
+== Component Options
+
+
+The JsonPatch component supports 2 options, which are listed below.
+
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
+| *autowiredEnabled* (advanced) | Whether autowiring is enabled. This is used
for automatic autowiring options (the option must be marked as autowired) by
looking up in the registry to find if there is a single instance of matching
type, which then gets configured on the component. This can be used for
automatic configuring JDBC data sources, JMS connection factories, AWS Clients,
etc. | true | boolean
+|===
+// component options: END
+
+// endpoint options: START
+== Endpoint Options
+
+The JsonPatch endpoint is configured using URI syntax:
+
+----
+json-patch:resourceUri
+----
+
+with the following path and query parameters:
+
+=== Path Parameters (1 parameters):
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *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
+|===
+
+
+=== Query Parameters (3 parameters):
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *allowContextMapAll* (producer) | Sets whether the context map should allow
access to all details. By default only the message body and headers can be
accessed. This option can be enabled for full access to the current Exchange
and CamelContext. Doing so impose a potential security risk as this opens
access to the full power of CamelContext API. | false | boolean
+| *contentCache* (producer) | Sets whether to use resource content cache or
not | false | boolean
+| *lazyStartProducer* (producer) | Whether the producer should be started lazy
(on the first message). By starting lazy you can use this to allow CamelContext
and routes to startup in situations where a producer may otherwise fail during
starting and cause the route to fail being started. By deferring this startup
to be lazy then the startup failure can be handled during routing messages via
Camel's routing error handlers. Beware that when the first message is processed
then creating and [...]
+|===
+// endpoint options: END
+
+
+== Passing values to JSLT
+
+Camel can supply exchange information as variables when applying a JSLT
expression on the body. The available variables from the *Exchange* are:
+
+[width="100%",cols="2,5",options="header"]
+|===
+| name | value
+| headers | The headers of the In message as a json object
+| exchange.properties | The *Exchange* properties as a json object. _exchange_
is the name of the variable and _properties_ is the path to the exchange
properties. Available if _allowContextMapAll_ option is true.
+|===
+
+All the values that cannot be converted to json with Jackson are denied and
will not be available in the jslt expression.
+
+For example, the header named "type" and the exchange property "instance" can
be accessed like
+
+[source,json]
+--------------------------------------
+{
+ "type": $headers.type,
+ "instance": $exchange.properties.instance
+}
+--------------------------------------
+
+== Samples
+
+For example you could use something like
+
+[source,java]
+--------------------------------------
+from("activemq:My.Queue").
+ to("jslt:com/acme/MyResponse.json");
+--------------------------------------
+
+And a file based resource:
+
+[source,java]
+---------------------------------------------------------------
+from("activemq:My.Queue").
+ to("jslt:file://myfolder/MyResponse.json?contentCache=true").
+ to("activemq:Another.Queue");
+---------------------------------------------------------------
+
+You can also specify which JSLT expression the component should use
+dynamically via a header, so for example:
+
+[source,java]
+---------------------------------------------------------------------
+from("direct:in").
+ setHeader("CamelJsltResourceUri").constant("path/to/my/spec.json").
+ to("jslt:dummy?allowTemplateFromHeader=true");
+---------------------------------------------------------------------
+
+Or send whole jslt expression via header: (suitable for querying)
+
+[source,java]
+---------------------------------------------------------------------
+from("direct:in").
+ setHeader("CamelJsltString").constant(".published").
+ to("jslt:dummy?allowTemplateFromHeader=true");
+---------------------------------------------------------------------
+
+Passing exchange properties to the jslt expression can be done like this
+
+[source,java]
+---------------------------------------------------------------------
+from("direct:in").
+ to("jslt:com/acme/MyResponse.json?allowContextMapAll=true");
+---------------------------------------------------------------------
+
+include::{page-component-version}@camel-spring-boot::page$jslt-starter.adoc[]
