This is an automated email from the ASF dual-hosted git repository. lburgazzoli pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel-k-runtime.git
The following commit(s) were added to refs/heads/master by this push: new 61d9256 chore: Minor docs & code sample fixes 61d9256 is described below commit 61d9256188242e08b2d7fae13eed873c71c0c618 Author: James Netherton <jamesnether...@gmail.com> AuthorDate: Fri Aug 21 08:16:45 2020 +0100 chore: Minor docs & code sample fixes --- docs/modules/languages/pages/groovy.adoc | 2 +- docs/modules/languages/pages/javascript.adoc | 2 +- docs/modules/languages/pages/kotlin.adoc | 4 ++-- docs/modules/languages/pages/yaml.adoc | 14 +++++++------- examples/camel-k-runtime-example-rest/README.adoc | 2 +- 5 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/modules/languages/pages/groovy.adoc b/docs/modules/languages/pages/groovy.adoc index 0e9b75d..669e62b 100644 --- a/docs/modules/languages/pages/groovy.adoc +++ b/docs/modules/languages/pages/groovy.adoc @@ -158,7 +158,7 @@ beans { == Rest Support -Integrations's REST endpoints can be configured using the top level _rest_ block: +Integrations REST endpoints can be configured using the top level _rest_ block: [source,groovy] ---- diff --git a/docs/modules/languages/pages/javascript.adoc b/docs/modules/languages/pages/javascript.adoc index 7f93f29..597825f 100644 --- a/docs/modules/languages/pages/javascript.adoc +++ b/docs/modules/languages/pages/javascript.adoc @@ -27,7 +27,7 @@ To run it, you need just to execute: kamel run hello.js ``` -For JavaScript integrations, Camel K does not yet provide an enhanced DSL but you can access to some global bounded objects such as a writable registry and the camel context so to set the property _exchangeFormatter_ of the _LogComponent_ as done in previous example, you can do something like: +For JavaScript integrations, Camel K does not yet provide an enhanced DSL, but you can access to some global bounded objects such as a writable registry and the camel context so to set the property _exchangeFormatter_ of the _LogComponent_ as done in previous example, you can do something like: [source,js] ---- diff --git a/docs/modules/languages/pages/kotlin.adoc b/docs/modules/languages/pages/kotlin.adoc index fe9aefe..478b850 100644 --- a/docs/modules/languages/pages/kotlin.adoc +++ b/docs/modules/languages/pages/kotlin.adoc @@ -24,7 +24,7 @@ context { } ---- -At the moment the enhanced DSL provides a way to bind items to the registry, to configure the components the context creates and some improvements over the REST DSL. +At the moment, the enhanced DSL provides a way to bind items to the registry, to configure the components the context creates and some improvements over the REST DSL. == Beans DSL @@ -96,7 +96,7 @@ As for Groovy, you can provide your custom extension to the DSL == Rest Endpoints -Integrations's REST endpoints can be configured using the top level _rest_ block: +Integrations REST endpoints can be configured using the top level _rest_ block: [source,kotlin] ---- diff --git a/docs/modules/languages/pages/yaml.adoc b/docs/modules/languages/pages/yaml.adoc index 276fa61..33700a6 100644 --- a/docs/modules/languages/pages/yaml.adoc +++ b/docs/modules/languages/pages/yaml.adoc @@ -7,7 +7,7 @@ The YAML DSL is current in preview support level. == Defining a route -A route is a sequence of elements, or `steps`, defined as follow: +A route is a sequence of elements, or `steps`, defined as follows: [source,yaml] ---- @@ -28,7 +28,7 @@ from: #<1> [NOTE] ==== -Each step is represented by YAML map that has a single entry where the field name is the EIP name +Each step is represented by a YAML map that has a single entry where the field name is the EIP name ==== As general rule each step provide all the parameters the related definition declares but there are some minor differences/enhancements: @@ -114,7 +114,7 @@ In case you want to use the data-format's default settings, you need to place an == Extending the DSL -The DSL is designed to be easily extended so you can provide your own step handler which is discovered at runtime using Camel's factory finder. +The DSL is designed to be easily extended, so you can provide your own step handler which is discovered at runtime using Camel's factory finder. Assuming you want to create a step to simplify the creation of a certain type of endpoints then you need: @@ -130,14 +130,14 @@ class=com.acme.converter.MyConverter [source,java] ---- -package com.acme.converter.AcmeConverter +package com.acme.converter.AcmeConverter; import org.apache.camel.k.loader.yaml.parser.ProcessorStepParser; public class AcmeConverter implements ProcessorStepParser { /** - * @param context contains a references to the camel context and the current node as raw JsonNode + * @param context contains references to the camel context and the current node as raw JsonNode */ @Override public ProcessorDefinition<?> toProcessor(Context context) { @@ -145,8 +145,8 @@ public class AcmeConverter Definition definition = context.node(Definition.class); // create the definition - ToDefinition to = new ToDefinition() - to.setUri(String.format("http://%s:%d/fixed/path"), definition.host, definition.port) + ToDefinition to = new ToDefinition(); + to.setUri(String.format("http://%s:%d/fixed/path", definition.host, definition.port)); return to; } diff --git a/examples/camel-k-runtime-example-rest/README.adoc b/examples/camel-k-runtime-example-rest/README.adoc index bc2024f..d424e4b 100644 --- a/examples/camel-k-runtime-example-rest/README.adoc +++ b/examples/camel-k-runtime-example-rest/README.adoc @@ -1,7 +1,7 @@ Rest Apache Camel K Runtime example ====================================== -This repository contains an Apache Camel-K Runtime application that expose a `rest` endpoint and and `/health` endpoint to gather Camel context status. +This repository contains an Apache Camel-K Runtime application that expose a `rest` endpoint and `/health` endpoint to gather Camel context status. In order to run it: [code,shell]