You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/10/10 03:31:19 UTC
[camel] branch master updated: Example readme from md to adoc and
new help note (#3235)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new e7faf8a Example readme from md to adoc and new help note (#3235)
e7faf8a is described below
commit e7faf8a6afd3967ff6c5f2a340cbac81f8d01283
Author: Federico Valeri <fv...@users.noreply.github.com>
AuthorDate: Thu Oct 10 05:30:58 2019 +0200
Example readme from md to adoc and new help note (#3235)
---
examples/README.adoc | 10 +-
examples/camel-example-activemq-tomcat/README.adoc | 53 ++++++
examples/camel-example-activemq-tomcat/README.md | 48 -----
examples/camel-example-aggregate/README.adoc | 64 +++++++
examples/camel-example-aggregate/README.md | 57 ------
examples/camel-example-any23/README.adoc | 12 +-
.../README.adoc | 119 ++++++++++++
.../camel-example-artemis-amqp-blueprint/README.md | 90 ---------
.../README.adoc | 89 +++++++++
.../camel-example-artemis-large-messages/README.md | 74 --------
examples/camel-example-artemis/README.adoc | 101 +++++++++++
examples/camel-example-artemis/README.md | 81 ---------
examples/camel-example-as2/README.adoc | 35 ++++
examples/camel-example-as2/README.md | 32 ----
examples/camel-example-bigxml-split/README.adoc | 78 ++++++++
examples/camel-example-bigxml-split/README.md | 60 ------
examples/camel-example-billboard-aggr/README.adoc | 56 ++++++
examples/camel-example-billboard-aggr/README.md | 46 -----
.../camel-example-cafe-endpointdsl/README.adoc | 44 +++++
examples/camel-example-cafe-endpointdsl/README.md | 40 ----
examples/camel-example-cafe/README.adoc | 42 +++++
examples/camel-example-cafe/README.md | 37 ----
.../camel-example-cassandra-kubernetes/LICENSE.md | 202 ---------------------
.../{ReadMe.md => README.adoc} | 84 +++++----
examples/camel-example-cdi-aws-s3/README.adoc | 47 +++++
examples/camel-example-cdi-aws-s3/README.md | 38 ----
.../{README.md => README.adoc} | 91 ++++++----
.../{README.md => README.adoc} | 92 ++++++----
.../{README.md => README.adoc} | 74 ++++----
.../{README.md => README.adoc} | 61 ++++---
.../{README.md => README.adoc} | 71 ++++----
examples/camel-example-cdi-test/README.adoc | 75 ++++++++
examples/camel-example-cdi-test/README.md | 67 -------
.../{README.md => README.adoc} | 79 ++++----
examples/camel-example-cdi/README.adoc | 45 +++++
examples/camel-example-cdi/README.md | 43 -----
examples/camel-example-console/README.adoc | 48 +++++
examples/camel-example-console/README.md | 43 -----
examples/camel-example-cxf-blueprint/README.adoc | 112 ++++++++++++
examples/camel-example-cxf-blueprint/README.md | 88 ---------
examples/camel-example-cxf-proxy/README.adoc | 88 +++++++++
examples/camel-example-cxf-proxy/README.md | 74 --------
examples/camel-example-cxf-tomcat/README.adoc | 75 ++++++++
examples/camel-example-cxf-tomcat/README.md | 67 -------
.../README.adoc | 110 +++++++++++
.../README.md | 117 ------------
examples/camel-example-cxf/README.adoc | 55 ++++++
examples/camel-example-cxf/README.md | 45 -----
examples/camel-example-debezium/README.adoc | 15 +-
.../camel-example-ehcache-blueprint/README.adoc | 84 +++++++++
examples/camel-example-ehcache-blueprint/README.md | 60 ------
.../readme.adoc | 25 ++-
examples/camel-example-fhir-osgi/README.adoc | 166 +++++++++++++++++
examples/camel-example-fhir-osgi/README.md | 148 ---------------
.../camel-example-fhir-spring-boot/readme.adoc | 14 +-
.../camel-example-fhir/{README.md => README.adoc} | 61 ++++---
examples/camel-example-ftp/README.md | 11 +-
examples/camel-example-google-pubsub/README.adoc | 14 +-
examples/camel-example-grpc-kubernetes/README.adoc | 8 +-
.../camel-example-hazelcast-kubernetes/LICENSE.md | 202 ---------------------
.../{ReadMe.md => README.adoc} | 146 ++++++++-------
examples/camel-example-hystrix/README.adoc | 93 ++++++++++
examples/camel-example-hystrix/README.md | 78 --------
examples/camel-example-java8/readme.adoc | 14 +-
examples/camel-example-jdbc/README.adoc | 49 +++++
examples/camel-example-jdbc/README.md | 47 -----
examples/camel-example-jira/README.adoc | 18 +-
examples/camel-example-jms-file/README.adoc | 37 ++++
examples/camel-example-jms-file/README.md | 33 ----
examples/camel-example-jmx/README.adoc | 41 +++++
examples/camel-example-jmx/README.md | 36 ----
examples/camel-example-jooq/README.adoc | 24 ++-
examples/camel-example-kafka-avro/README.adoc | 19 +-
.../README.adoc | 21 +--
examples/camel-example-kafka/README.adoc | 18 +-
examples/camel-example-kotlin/README.adoc | 34 ++++
examples/camel-example-kotlin/ReadMe.md | 29 ---
examples/camel-example-loadbalancing/README.adoc | 65 +++++++
examples/camel-example-loadbalancing/README.md | 12 +-
examples/camel-example-loan-broker-cxf/README.adoc | 37 ++++
examples/camel-example-loan-broker-cxf/README.md | 30 ---
examples/camel-example-loan-broker-jms/README.adoc | 37 ++++
examples/camel-example-loan-broker-jms/README.md | 30 ---
examples/camel-example-main-artemis/readme.adoc | 16 +-
examples/camel-example-main-tiny/readme.adoc | 16 +-
examples/camel-example-main/readme.adoc | 18 +-
examples/camel-example-management/README.adoc | 91 ++++++++++
examples/camel-example-management/README.md | 73 --------
examples/camel-example-micrometer/README.adoc | 80 ++++++++
examples/camel-example-micrometer/README.md | 71 --------
examples/camel-example-mybatis/README.adoc | 59 ++++++
examples/camel-example-mybatis/README.md | 50 -----
.../readme.adoc | 14 +-
.../{README.md => README.adoc} | 103 ++++++-----
.../{README.md => README.adoc} | 85 +++++----
examples/camel-example-opentracing/README.adoc | 71 ++++++++
examples/camel-example-opentracing/README.md | 63 -------
examples/camel-example-pojo-messaging/README.adoc | 35 ++++
examples/camel-example-pojo-messaging/README.md | 30 ---
examples/camel-example-rabbitmq/readme.adoc | 14 +-
.../readme.adoc | 16 +-
.../camel-example-reactive-streams/readme.adoc | 14 +-
examples/camel-example-rest-producer/readme.adoc | 18 +-
examples/camel-example-rest-swagger/README.adoc | 41 +++++
examples/camel-example-rest-swagger/README.md | 30 ---
examples/camel-example-restlet-jdbc/README.adoc | 102 +++++++++++
examples/camel-example-restlet-jdbc/README.md | 70 -------
.../camel-example-route-throttling/README.adoc | 73 ++++++++
examples/camel-example-route-throttling/README.md | 11 +-
.../README.adoc | 72 ++++++++
.../README.md | 55 ------
.../README.adoc | 87 +++++++++
.../camel-example-servlet-rest-blueprint/README.md | 65 -------
examples/camel-example-servlet-tomcat/README.adoc | 44 +++++
examples/camel-example-servlet-tomcat/README.md | 34 ----
examples/camel-example-spark-rest/README.adoc | 78 ++++++++
examples/camel-example-spark-rest/README.md | 62 -------
examples/camel-example-splunk/README.adoc | 65 +++++++
examples/camel-example-splunk/README.md | 64 -------
.../camel-example-spring-boot-activemq/readme.adoc | 20 +-
.../camel-example-spring-boot-amqp/readme.adoc | 20 +-
.../readme.adoc | 21 ++-
.../camel-example-spring-boot-geocoder/README.adoc | 16 +-
.../camel-example-spring-boot-grpc/README.adoc | 18 +-
.../readme.adoc | 18 +-
.../README.adoc | 16 +-
.../camel-example-spring-boot-master/readme.adoc | 20 +-
.../camel-example-spring-boot-metrics/README.adoc | 59 ++++++
.../camel-example-spring-boot-metrics/README.md | 46 -----
.../camel-example-spring-boot-pojo/README.adoc | 16 +-
.../{README.md => README.adoc} | 70 +++----
.../README.adoc | 16 +-
.../README.adoc | 21 ++-
.../readme.adoc | 23 ++-
examples/camel-example-spring-boot-xml/readme.adoc | 19 +-
examples/camel-example-spring-boot/readme.adoc | 21 ++-
.../README.adoc | 20 +-
.../README.adoc | 23 ++-
.../camel-example-spring-javaconfig/README.adoc | 42 +++++
examples/camel-example-spring-javaconfig/README.md | 38 ----
examples/camel-example-spring-jms/README.adoc | 53 ++++++
examples/camel-example-spring-jms/README.md | 44 -----
examples/camel-example-spring-pulsar/README.adoc | 66 +++++++
examples/camel-example-spring-pulsar/README.md | 46 -----
examples/camel-example-spring-security/README.adoc | 42 +++++
examples/camel-example-spring-security/README.md | 36 ----
examples/camel-example-spring-ws/README.adoc | 42 +++++
examples/camel-example-spring-ws/README.md | 39 ----
examples/camel-example-spring-xquery/README.adoc | 43 +++++
examples/camel-example-spring-xquery/README.md | 39 ----
examples/camel-example-spring/README.adoc | 41 +++++
examples/camel-example-spring/README.md | 37 ----
examples/camel-example-sql-blueprint/README.adoc | 65 +++++++
examples/camel-example-sql-blueprint/README.md | 56 ------
examples/camel-example-ssh-security/README.adoc | 121 ++++++++++++
examples/camel-example-ssh-security/README.md | 99 ----------
examples/camel-example-ssh/README.adoc | 48 +++++
examples/camel-example-ssh/README.md | 40 ----
examples/camel-example-swagger-cdi/README.adoc | 64 +++++++
examples/camel-example-swagger-cdi/README.md | 53 ------
examples/camel-example-swagger-osgi/README.adoc | 67 +++++++
examples/camel-example-swagger-osgi/README.md | 60 ------
examples/camel-example-telegram/README.adoc | 16 +-
.../README.adoc | 58 ++++++
.../camel-example-transformer-blueprint/README.md | 51 ------
examples/camel-example-transformer-cdi/README.adoc | 40 ++++
examples/camel-example-transformer-cdi/README.md | 37 ----
.../camel-example-transformer-demo/README.adoc | 39 ++++
examples/camel-example-transformer-demo/README.md | 37 ----
.../camel-example-twitter-salesforce/README.adoc | 126 +++++++++++++
.../camel-example-twitter-salesforce/README.md | 108 -----------
.../README.adoc | 68 +++++++
.../README.md | 57 ------
.../camel-example-twitter-websocket/README.adoc | 47 +++++
examples/camel-example-twitter-websocket/README.md | 41 -----
.../readme.adoc | 18 +-
examples/camel-example-webhook/readme.adoc | 18 +-
.../camel-example-widget-gadget-cdi/README.adoc | 97 ++++++++++
examples/camel-example-widget-gadget-cdi/README.md | 78 --------
.../camel-example-widget-gadget-java/README.adoc | 95 ++++++++++
.../camel-example-widget-gadget-java/README.md | 76 --------
.../camel-example-widget-gadget-xml/README.adoc | 96 ++++++++++
examples/camel-example-widget-gadget-xml/README.md | 77 --------
examples/camel-example-zipkin/README.adoc | 127 +++++++++++++
examples/camel-example-zipkin/README.md | 105 -----------
185 files changed, 5432 insertions(+), 4749 deletions(-)
diff --git a/examples/README.adoc b/examples/README.adoc
index fe20c5e..160f20f 100644
--- a/examples/README.adoc
+++ b/examples/README.adoc
@@ -268,12 +268,12 @@ Number of Examples: 115 (0 deprecated)
|===
// examples: END
+== Help and contributions
-== Forum, Help, etc
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
-If you hit an problems please let us know on the Camel Forums <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-activemq-tomcat/README.adoc b/examples/camel-example-activemq-tomcat/README.adoc
new file mode 100644
index 0000000..2f48637
--- /dev/null
+++ b/examples/camel-example-activemq-tomcat/README.adoc
@@ -0,0 +1,53 @@
+== Embedded ActiveMQ Broker with Camel running in Apache Tomcat
+
+=== Introduction
+
+This example shows how you can embed Apache ActiveMQ Broker and Camel in
+a web application, which can run on Apache Tomcat or other web
+containers.
+
+This example embeds ActiveMQ Broker and a Camel application which will
+continuously send a message per second to an inbox queue. Then another
+Camel route will route messages from the inbox to the outbox queue.
+
+==== Camel component used in this example
+
+* camel-core
+* camel-jms
+* camel-spring
+
+=== Build
+
+You will need to build this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+Which will create a `+.war+` file in the target directly.
+
+You can then deploy this `+.war+` file in any web container such as
+Apache Tomcat, by copying the `+.war+` file to its `+/webapp+`
+directory.
+
+This example embeds ActiveMQ Broker and a Camel application which will
+continuously send a message per second to an inbox queue. Then another
+Camel route will route messages from the inbox to the outbox queue.
+
+=== Configuration
+
+The ActiveMQ broker is configured in the
+`+src/main/resources/broker.xml+` file. And the Camel application in the
+`+src/main/resources/camel-context.xml+` file.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-activemq-tomcat/README.md b/examples/camel-example-activemq-tomcat/README.md
deleted file mode 100644
index 05e8e80..0000000
--- a/examples/camel-example-activemq-tomcat/README.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# Embedded ActiveMQ Broker with Camel running in Apache Tomcat
-
-### Introduction
-This example shows how you can embed Apache ActiveMQ Broker and Camel in a web application, which can run on Apache Tomcat or other web containers.
-
-This example embeds ActiveMQ Broker and a Camel application which will continuously send a message per second to an inbox queue.
-Then another Camel route will route messages from the inbox to the outbox queue.
-
-#### Camel component used in this example
-
-* camel-core
-* camel-jms
-* camel-spring
-
-### Build
-
-You will need to build this example first:
-
- mvn install
-
-### Run
-
-Which will create a `.war` file in the target directly.
-
-You can then deploy this `.war` file in any web container such as
-Apache Tomcat, by copying the `.war` file to its `/webapp` directory.
-
-This example embeds ActiveMQ Broker and a Camel application
-which will continuously send a message per second to an inbox queue.
-Then another Camel route will route messages from the inbox
-to the outbox queue.
-
-### Configuration
-
-The ActiveMQ broker is configured in the `src/main/resources/broker.xml` file.
-And the Camel application in the `src/main/resources/camel-context.xml` file.
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-aggregate/README.adoc b/examples/camel-example-aggregate/README.adoc
new file mode 100644
index 0000000..2d3a579
--- /dev/null
+++ b/examples/camel-example-aggregate/README.adoc
@@ -0,0 +1,64 @@
+== Camel Persistent Aggregate
+
+=== Introduction
+
+This example shows how to use Camel Aggregator EIP which offers (since
+Camel 2.3) database persistence.
+
+It's an interactive example where you can type in some numbers which
+then are aggregated (summed, per this sample's aggregation strategy)
+whenever the user types `+STOP+`. +
+The user can then enter more numbers to do another aggregation.
+
+==== How it works
+
+The example is an interactive example where it prompt on the console for
+you to enter a number and press `+ENTER+`. The numbers you enter will
+then be aggregated and persisted. That means you can at any time hit
+`+ctrl + c+` to shutdown Camel.
+
+Then you should be able to start the example again and resume where you
+left. When you want to complete the aggregation you can enter `+STOP+`
+as input and Camel will show you the result, which is the sum of all the
+numbers entered.
+
+The persistent datastore is located in the `+data/hawtdb.dat+` file. Its
+automatic created the first time.
+
+==== Camel component used in this example
+
+* camel-core
+* camel-spring
+* camel-stream
+
+=== Build
+
+The example is run using Maven.
+
+First compile the example by entering:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type:
+
+....
+mvn camel:run
+....
+
+To stop the example hit ctrl+c. If you restart it and resume entering
+numbers you should see that it remembered previously entered values, as
+it uses a persistent store.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-aggregate/README.md b/examples/camel-example-aggregate/README.md
deleted file mode 100644
index f00f4d9..0000000
--- a/examples/camel-example-aggregate/README.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# Camel Persistent Aggregate
-
-### Introduction
-
-This example shows how to use Camel Aggregator EIP which offers (since Camel 2.3)
-database persistence.
-
-It's an interactive example where you can type in some numbers which then are aggregated
-(summed, per this sample's aggregation strategy) whenever the user types `STOP`.
-The user can then enter more numbers to do another aggregation.
-
-#### How it works
-
-The example is an interactive example where it prompt on the console for you to enter a number and press `ENTER`.
-The numbers you enter will then be aggregated and persisted. That means you can at any time hit `ctrl + c` to shutdown Camel.
-
-Then you should be able to start the example again and resume where you left.
-When you want to complete the aggregation you can enter `STOP` as input and Camel will show you the result,
-which is the sum of all the numbers entered.
-
-The persistent datastore is located in the `data/hawtdb.dat` file. Its automatic created the first time.
-
-#### Camel component used in this example
-
-* camel-core
-* camel-spring
-* camel-stream
-
-### Build
-
-The example is run using Maven.
-
-First compile the example by entering:
-
- mvn compile
-
-### Run
-
-To run the example type:
-
- mvn camel:run
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>. If you restart it and resume
-entering numbers you should see that it remembered previously entered values, as it
-uses a persistent store.
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-any23/README.adoc b/examples/camel-example-any23/README.adoc
index 2945073..a0bc955 100644
--- a/examples/camel-example-any23/README.adoc
+++ b/examples/camel-example-any23/README.adoc
@@ -1,4 +1,4 @@
-= Apache Any23 Example
+== Apache Any23 Example
This example shows how to extract data from a page with RDF content using Apache Any23. In this example the Dbpedia webpage of a country (Ecuador) is processed with the camel-any23 dataformat as a RDF4J Model.
The extracted information is filtered in order to select the URIS of the country's leaders through the Dbpedia property http://dbpedia.org/ontology/leader .
@@ -21,3 +21,13 @@ You can find more information about Apache Any23 at the website: https://any23.a
== More information about Apache Camel
You can find more information about Apache Camel at the website: http://camel.apache.org/
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-artemis-amqp-blueprint/README.adoc b/examples/camel-example-artemis-amqp-blueprint/README.adoc
new file mode 100644
index 0000000..3432708
--- /dev/null
+++ b/examples/camel-example-artemis-amqp-blueprint/README.adoc
@@ -0,0 +1,119 @@
+== Camel Artemis AMQP Messaging
+
+This example shows how to produce/consume messages between Apache Camel
+and ActiveMQ Artemis using the AMQP component based on the JMS 2.0
+Apache Qpid Proton client library.
+
+One benefit of using Camel's AMQP component is to allow connectivity to
+Qpid's Dispatch Router enabling flexible and scalable interconnect
+between any AMQP endpoints.
+
+The example includes a JUnit to showcase how to embed an AMQP enabled
+Artemis Broker. This permits building and testing the code in complete
+isolation.
+
+When deployed in a running environment, Camel will attempt to connect to
+an already existing Artemis broker using the default AMQP port (5672).
+
+=== Test with embedded Artemis
+
+The JUnit with an included embedded Artemis Broker can be triggered
+using Maven.
+
+....
+mvn test -P itest
+....
+
+=== Install ActiveMQ Artemis
+
+To automate downloading, unpacking and configuration of Apache ActiveMQ
+Artemis with latest defined version a special profile is added. It's
+necessary to run following Maven command for do this during example
+install:
+
+....
+mvn install -P artemis
+....
+
+=== Run ActiveMQ Artemis
+
+To start configured ActiveMQ Artemis instance in a shell use:
+
+....
+$ target/artemis-instance/bin/artemis run
+....
+
+Which startup ActiveMQ Artemis in the foreground and keeps it running
+until you hit ctrl+c to shutdown ActiveMQ Artemis.
+
+=== Run Camel
+
+Start the Camel application:
+
+....
+mvn camel:run -DskipTests=true
+....
+
+Once started, Camel will be listening for HTTP requests (port 9090) as a
+trigger mechanism to fire AMQP messages to Artemis.
+
+From your prefered browser hit the following URL:
+
+....
+http://localhost:9090/message
+....
+
+Or alternatively, using cURL:
+
+....
+curl http://localhost:9090/message
+....
+
+The above actions should render on screen:
+
+....
+Hello from Camel's AMQP example
+....
+
+To stop the example hit ctrl+c.
+
+=== ActiveMQ Artemis web console
+
+You can browse the Artemis web console: http://localhost:8161/console to
+see activity such as number of consumers and producers or acknoledged
+messages.
+
+=== Run with Karaf
+
+You will need to install this example first to your local maven
+repository with:
+
+....
+mvn install
+....
+
+Then you can install this example from the shell using this example's
+`+features.xml+` for easy provisioning:
+
+....
+feature:repo-add mvn:org.apache.camel.example/camel-example-artemis-amqp-blueprint/${version}/xml/features
+feature:install camel-example-artemis-amqp-blueprint
+....
+
+And you can see the application running by tailing the logs:
+
+....
+log:tail
+....
+
+And you can use ctrl+c to stop tailing the log.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-artemis-amqp-blueprint/README.md b/examples/camel-example-artemis-amqp-blueprint/README.md
deleted file mode 100644
index e97d788..0000000
--- a/examples/camel-example-artemis-amqp-blueprint/README.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# Camel Artemis AMQP Messaging
-
-This example shows how to produce/consume messages between Apache Camel and ActiveMQ Artemis using the AMQP component based on the JMS 2.0 Apache Qpid Proton client library.
-
-One benefit of using Camel's AMQP component is to allow connectivity to Qpid's Dispatch Router enabling flexible and scalable interconnect between any AMQP endpoints.
-
-The example includes a JUnit to showcase how to embed an AMQP enabled Artemis Broker. This permits building and testing the code in complete isolation.
-
-When deployed in a running environment, Camel will attempt to connect to an already existing Artemis broker using the default AMQP port (5672).
-
-### Test with embedded Artemis
-
-The JUnit with an included embedded Artemis Broker can be triggered using Maven.
-
- mvn test -P itest
-
-### Install ActiveMQ Artemis
-
-To automate downloading, unpacking and configuration of Apache ActiveMQ Artemis with latest defined version a special profile is added.
-It's necessary to run following Maven command for do this during example install:
-
- mvn install -P artemis
-
-### Run ActiveMQ Artemis
-
-To start configured ActiveMQ Artemis instance in a shell use:
-
- $ target/artemis-instance/bin/artemis run
-
-Which startup ActiveMQ Artemis in the foreground and keeps it running until you hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-to shutdown ActiveMQ Artemis.
-
-### Run Camel
-
-Start the Camel application:
-
- mvn camel:run -DskipTests=true
-
-Once started, Camel will be listening for HTTP requests (port 9090) as a trigger mechanism to fire AMQP messages to Artemis.
-
-From your prefered browser hit the following URL:
-
- http://localhost:9090/message
-
-Or alternatively, using cURL:
-
- curl http://localhost:9090/message
-
-The above actions should render on screen:
-
- Hello from Camel's AMQP example
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>.
-
-### ActiveMQ Artemis web console
-
-You can browse the Artemis web console: <http://localhost:8161/console>
-to see activity such as number of consumers and producers or acknoledged messages.
-
-### Run with Karaf
-
-You will need to install this example first to your local maven repository with:
-
- mvn install
-
-Then you can install this example from the shell using this example's `features.xml`
-for easy provisioning:
-
- feature:repo-add mvn:org.apache.camel.example/camel-example-artemis-amqp-blueprint/${version}/xml/features
- feature:install camel-example-artemis-amqp-blueprint
-
-And you can see the application running by tailing the logs:
-
- log:tail
-
-And you can use <kbd>ctrl</kbd>+<kbd>c</kbd> to stop tailing the log.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-
-The Camel riders!
-
-
diff --git a/examples/camel-example-artemis-large-messages/README.adoc b/examples/camel-example-artemis-large-messages/README.adoc
new file mode 100644
index 0000000..7e41de3
--- /dev/null
+++ b/examples/camel-example-artemis-large-messages/README.adoc
@@ -0,0 +1,89 @@
+== Camel Artemis Large Messages
+
+=== Introduction
+
+This example shows how to send large messages between Apache Camel and
+ActiveMQ Artemis. When we say large messages we refer to messages with
+sizes of GB.
+
+You should be able to run Camel and Artemis in JVMs with lower memory
+such as 256/512mb etc, and still be able to send messages in GB of sizes
+between them.
+
+This works by spool big messages to disk. Artemis spool large messages
+to its `+data/large-messages+` directory, and Camel uses stream caching
+to spool to a temporary directory during routing.
+
+=== Build
+
+The example is run using Maven.
+
+First compile the example by entering:
+
+....
+mvn compile
+....
+
+=== Install ActiveMQ Artemis
+
+To automate downloading, unpacking and configuration of Apache ActiveMQ
+Artemis with latest defined version a special profile is added. It's
+necessary to run following Maven command for do this during example
+install:
+
+....
+mvn install -P artemis
+....
+
+=== Run ActiveMQ Artemis
+
+To start configured ActiveMQ Artemis instance in a shell use:
+
+....
+$ target/artemis-instance/bin/artemis run
+....
+
+Which startup ActiveMQ Artemis in the foreground and keeps it running
+until you hit ctrl+c to shutdown ActiveMQ Artemis.
+
+=== Run Camel
+
+Before running this example, then ensure the JVM has limited memory by
+executing
+
+....
+export MAVEN_OPTS="-Xmx256m"
+....
+
+And then start the Camel application:
+
+....
+mvn camel:run
+....
+
+You can then copy files to `+target/inbox+` folder which is send to
+Artemis, and then back again to Camel and written to the
+`+target/outbox+` folder.
+
+This should work for small and big files such as files with sizes of GB.
+The JVM should not run out of memory.
+
+To stop the example hit ctrl+c. If you restart it and resume entering
+numbers you should see that it remembered previously entered values, as
+it uses a persistent store.
+
+=== ActiveMQ Artemis web console
+
+You can browse the Artemis web console: http://localhost:8161/console to
+see activity such as number of consumers and producers. You can also
+delete all messages from queues which is a handy operation.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-artemis-large-messages/README.md b/examples/camel-example-artemis-large-messages/README.md
deleted file mode 100644
index 2b27b94..0000000
--- a/examples/camel-example-artemis-large-messages/README.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Camel Artemis Large Messages
-
-### Introduction
-
-This example shows how to send large messages between Apache Camel and ActiveMQ Artemis.
-When we say large messages we refer to messages with sizes of GB.
-
-You should be able to run Camel and Artemis in JVMs with lower memory such as 256/512mb etc, and
-still be able to send messages in GB of sizes between them.
-
-This works by spool big messages to disk. Artemis spool large messages to its `data/large-messages`
-directory, and Camel uses stream caching to spool to a temporary directory during routing.
-
-### Build
-
-The example is run using Maven.
-
-First compile the example by entering:
-
- mvn compile
-
-### Install ActiveMQ Artemis
-
-To automate downloading, unpacking and configuration of Apache ActiveMQ Artemis with latest defined version a special profile is added.
-It's necessary to run following Maven command for do this during example install:
-
- mvn install -P artemis
-
-### Run ActiveMQ Artemis
-
-To start configured ActiveMQ Artemis instance in a shell use:
-
- $ target/artemis-instance/bin/artemis run
-
-Which startup ActiveMQ Artemis in the foreground and keeps it running until you hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-to shutdown ActiveMQ Artemis.
-
-### Run Camel
-
-Before running this example, then ensure the JVM has limited memory by executing
-
- export MAVEN_OPTS="-Xmx256m"
-
-And then start the Camel application:
-
- mvn camel:run
-
-You can then copy files to `target/inbox` folder which is send to Artemis, and then
-back again to Camel and written to the `target/outbox` folder.
-
-This should work for small and big files such as files with sizes of GB.
-The JVM should not run out of memory.
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>. If you restart it and resume
-entering numbers you should see that it remembered previously entered values, as it
-uses a persistent store.
-
-### ActiveMQ Artemis web console
-
-You can browse the Artemis web console: <http://localhost:8161/console>
-to see activity such as number of consumers and producers.
-You can also delete all messages from queues which is a handy operation.
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-artemis/README.adoc b/examples/camel-example-artemis/README.adoc
new file mode 100644
index 0000000..356ac96
--- /dev/null
+++ b/examples/camel-example-artemis/README.adoc
@@ -0,0 +1,101 @@
+== Widget and Gadget Example - Apache ActiveMQ Artemis
+
+=== Introduction
+
+This example shows the Widget and Gadget use-case from the Enterprise
+Integration Patterns book. It is similar to the other Widget and Gadget
+example, but uses Apache ActiveMQ Artemis, the next generation message
+broker from ActiveMQ.
+
+The example provides a simple order system, where incoming orders, is
+routed to either a widget or gadget inventory system, for further
+processing. The example uses the most famous pattern from the EIP book,
+which is the Content Based Router.
+
+The example is implemented in plain Java without using any kind of
+_application server_ but just a plain old _Java Main_.
+
+==== Camel component used in this example
+
+* camel-core
+* camel-jms
+
+=== Build
+
+You will need to build this example first:
+
+....
+mvn install
+....
+
+=== Install ActiveMQ Artemis
+
+To automate downloading, unpacking and configuration of Apache ActiveMQ
+Artemis with latest defined version a special profile is added. It's
+necessary to run following Maven command for do this during example
+install:
+
+....
+mvn install -P artemis
+....
+
+=== Run ActiveMQ Artemis
+
+To start configured ActiveMQ Artemis instance in a shell use:
+
+....
+$ target/artemis-instance/bin/artemis run
+....
+
+Which startup ActiveMQ Artemis in the foreground and keeps it running
+until you hit ctrl+c to shutdown ActiveMQ Artemis.
+
+=== Run Camel
+
+The Camel application connects to the message broker on url:
+`+tcp://localhost:61616+`. The url can be changed in the
+`+ArtemisMain.java+` source code.
+
+When the ActiveMQ Artemis broker is running, then you can run this
+example using:
+
+....
+mvn compile exec:java
+....
+
+When the Camel application runs, you should see 2 orders being processed
+and logged to the console, with an output similar to:
+
+....
+2019-04-26 11:04:27,154 [sumer[newOrder]] INFO gadget - Exchange[ExchangePattern: InOnly, BodyType: String, Body: ...<order> <customerId>456</customerId> <product>gadget</product> <amount>3</amount></order>]
+2019-04-26 11:04:27,162 [sumer[newOrder]] INFO widget - Exchange[ExchangePattern: InOnly, BodyType: String, Body: ...<order> <customerId>123</customerId> <product>widget</product> <amount>2</amount></order>]
+....
+
+You can access the ActiveMQ Artemis web console using
+http://localhost:8161/console and then browse the queues. The user name
+and password for accessing the console are setup when creating the
+broker instance and are, in this example, set to `+admin+` and `+admin+`
+respectively.
+
+You should see the three queues:
+
+* newOrder
+* widget
+* gadget
+
+The Camel application can be stopped pressing ctrl+c in the shell.
+
+=== Configuration
+
+The Camel application is configured in the
+`+src/main/java/org/apache/camel/example/ArtemisMain.java+` file.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-artemis/README.md b/examples/camel-example-artemis/README.md
deleted file mode 100644
index 831abea..0000000
--- a/examples/camel-example-artemis/README.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Widget and Gadget Example - Apache ActiveMQ Artemis
-
-### Introduction
-
-This example shows the Widget and Gadget use-case from the Enterprise Integration Patterns book. It is similar
-to the other Widget and Gadget example, but uses Apache ActiveMQ Artemis, the next generation message broker
-from ActiveMQ.
-
-The example provides a simple order system, where incoming orders, is routed to either a widget or gadget inventory system,
-for further processing. The example uses the most famous pattern from the EIP book, which is the Content Based Router.
-
-The example is implemented in plain Java without using any kind of _application server_ but just a plain old _Java Main_.
-
-#### Camel component used in this example
-
-* camel-core
-* camel-jms
-
-### Build
-
-You will need to build this example first:
-
- mvn install
-
-### Install ActiveMQ Artemis
-
-To automate downloading, unpacking and configuration of Apache ActiveMQ Artemis with latest defined version a special profile is added.
-It's necessary to run following Maven command for do this during example install:
-
- mvn install -P artemis
-
-### Run ActiveMQ Artemis
-
-To start configured ActiveMQ Artemis instance in a shell use:
-
- $ target/artemis-instance/bin/artemis run
-
-Which startup ActiveMQ Artemis in the foreground and keeps it running until you hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-to shutdown ActiveMQ Artemis.
-
-### Run Camel
-
-The Camel application connects to the message broker on url: `tcp://localhost:61616`.
-The url can be changed in the `ArtemisMain.java` source code.
-
-When the ActiveMQ Artemis broker is running, then you can run this example using:
-
- mvn compile exec:java
-
-When the Camel application runs, you should see 2 orders being processed and logged to the console, with an
-output similar to:
-```
-2019-04-26 11:04:27,154 [sumer[newOrder]] INFO gadget - Exchange[ExchangePattern: InOnly, BodyType: String, Body: ...<order> <customerId>456</customerId> <product>gadget</product> <amount>3</amount></order>]
-2019-04-26 11:04:27,162 [sumer[newOrder]] INFO widget - Exchange[ExchangePattern: InOnly, BodyType: String, Body: ...<order> <customerId>123</customerId> <product>widget</product> <amount>2</amount></order>]
-```
-
-You can access the ActiveMQ Artemis web console using [http://localhost:8161/console](http://localhost:8161/console)
-and then browse the queues. The user name and password for accessing the console are setup when creating
-the broker instance and are, in this example, set to `admin` and `admin` respectively.
-
-You should see the three queues:
-
- - newOrder
- - widget
- - gadget
-
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
-
-### Configuration
-
-The Camel application is configured in the `src/main/java/org/apache/camel/example/ArtemisMain.java` file.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-as2/README.adoc b/examples/camel-example-as2/README.adoc
new file mode 100644
index 0000000..6bddd76
--- /dev/null
+++ b/examples/camel-example-as2/README.adoc
@@ -0,0 +1,35 @@
+== Camel AS2 Example
+
+=== Introduction
+
+This example shows how to work with AS2 and Camel.
+
+The Camel AS2 example is a demo of the camel-as2 component to show how
+to route messages between AS2 endpoints, with endpoints consuming and
+producing AS2 messages over HTTP request.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-as2/README.md b/examples/camel-example-as2/README.md
deleted file mode 100644
index 62dcfea..0000000
--- a/examples/camel-example-as2/README.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Camel AS2 Example
-
-### Introduction
-
-This example shows how to work with AS2 and Camel.
-
-The Camel AS2 example is a demo of the camel-as2 component to show how to route messages between AS2 endpoints,
-with endpoints consuming and producing AS2 messages over HTTP request.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example type
-
- mvn camel:run
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-bigxml-split/README.adoc b/examples/camel-example-bigxml-split/README.adoc
new file mode 100644
index 0000000..cfa5c06
--- /dev/null
+++ b/examples/camel-example-bigxml-split/README.adoc
@@ -0,0 +1,78 @@
+== Splitting big XML payloads
+
+=== Introduction
+
+This example shows how to deal with big XML files in Camel.
+
+The XPath tokenizer will load the entire XML content into memory, so
+it's not well suited for very big XML payloads. +
+Instead you can use the StAX or XML tokenizers to efficiently iterate
+the XML payload in a streamed fashion. +
+For more information please read the
+http://camel.apache.org/splitter.html[official documentation].
+
+There are 2 tests:
+
+[arabic]
+. `+StaxTokenizerTest+` : requires using JAXB and process messages using
+a SAX ContentHandler
+. `+XmlTokenizerTest+` : easier to use but can't handle complex XML
+structures (i.e. nested naming clash)
+
+The test XML contains a simple collection of records.
+
+[source,xml]
+----
+<?xml version="1.0" encoding="UTF-8"?>
+<records xmlns="http://fvaleri.it/records">
+ <record>
+ <key>0</key>
+ <value>The quick brown fox jumps over the lazy dog</value>
+ </record>
+</records>
+----
+
+You can customize numOfRecords and maxWaitTime to do performance tests
+with different payloads. +
+Max JVM heap is restricted to 20 MB to show that it works with a very
+limited amount of memory (see `+pom.xml+`).
+
+There are also a number of optional runtime settings: - no cache enabled
+- no parallel processing - no mock endpoints with in-memory exchange
+store - enabled Throughput Logging for DEBUG level - disabled JMX
+instrumentation
+
+=== Build and run
+
+The test XML file is built once beforehand using `+@BeforeClass+`.
+
+[source,sh]
+----
+mvn clean test -DskipTests=false
+----
+
+=== Test results
+
+Tested on MacBook Pro 2,8 GHz Intel Core i7; 16 GB 2133 MHz LPDDR3; Java
+1.8.0_181.
+
+[cols=",,,,",options="header",]
+|===
+|tokenizer |numOfRecords |maxWaitTime (ms) |XML size (kB) |time (ms)
+|StAX |40000 |5000 |3543 |3052
+|XML |40000 |5000 |3543 |2756
+|StAX |1000000 |20000 |89735 |11740
+|XML |1000000 |20000 |89735 |11137
+|StAX |15000000 |200000 |1366102 |132176
+|XML |15000000 |200000 |1366102 |132549
+|===
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-bigxml-split/README.md b/examples/camel-example-bigxml-split/README.md
deleted file mode 100644
index 45d0453..0000000
--- a/examples/camel-example-bigxml-split/README.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Splitting big XML payloads
-
-### Introduction
-This example shows how to deal with big XML files in Camel.
-
-The XPath tokenizer will load the entire XML content into memory, so it's not well suited for very big XML payloads.
-Instead you can use the StAX or XML tokenizers to efficiently iterate the XML payload in a streamed fashion.
-For more information please read the [official documentation](http://camel.apache.org/splitter.html).
-
-There are 2 tests:
-
-1. `StaxTokenizerTest` : requires using JAXB and process messages using a SAX ContentHandler
-2. `XmlTokenizerTest` : easier to use but can't handle complex XML structures (i.e. nested naming clash)
-
-The test XML contains a simple collection of records.
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<records xmlns="http://fvaleri.it/records">
- <record>
- <key>0</key>
- <value>The quick brown fox jumps over the lazy dog</value>
- </record>
-</records>
-```
-
-You can customize numOfRecords and maxWaitTime to do performance tests with different payloads.
-Max JVM heap is restricted to 20 MB to show that it works with a very limited amount of memory (see `pom.xml`).
-
-There are also a number of optional runtime settings:
-- no cache enabled
-- no parallel processing
-- no mock endpoints with in-memory exchange store
-- enabled Throughput Logging for DEBUG level
-- disabled JMX instrumentation
-
-### Build and run
-The test XML file is built once beforehand using `@BeforeClass`.
-```sh
-mvn clean test -DskipTests=false
-```
-
-### Test results
-Tested on MacBook Pro 2,8 GHz Intel Core i7; 16 GB 2133 MHz LPDDR3; Java 1.8.0_181.
-
-tokenizer | numOfRecords | maxWaitTime (ms) | XML size (kB) | time (ms)
---- | --- | --- | --- | ---
-StAX | 40000 | 5000 | 3543 | 3052
-XML | 40000 | 5000 | 3543 | 2756
-StAX | 1000000 | 20000 | 89735 | 11740
-XML | 1000000 | 20000 | 89735 | 11137
-StAX | 15000000 | 200000 | 1366102 | 132176
-XML | 15000000 | 200000 | 1366102 | 132549
-
-### Forum, Help, etc
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-billboard-aggr/README.adoc b/examples/camel-example-billboard-aggr/README.adoc
new file mode 100644
index 0000000..51a4b4c
--- /dev/null
+++ b/examples/camel-example-billboard-aggr/README.adoc
@@ -0,0 +1,56 @@
+== Billboard TOP100 aggregation example
+
+=== Introduction
+
+The `+billboard_lyrics_1964-2015+` CSV dataset contains the TOP100 songs
+with lyrics for each year. +
+We can compute the TOP20 artists with most songs on Billboard using
+Split and Aggregate EIPs. +
+Build statistics is not the Camel core business but, as shown, you can
+easily do it!
+
+This is the final result:
+
+[cols=",",options="header",]
+|===
+|Artist |Presences
+|madonna |35
+|elton john |26
+|mariah carey |25
+|stevie wonder |22
+|janet jackson |22
+|michael jackson |22
+|whitney houston |19
+|rihanna |19
+|taylor swift |19
+|pink |17
+|the beatles |17
+|kelly clarkson |17
+|britney spears |16
+|the black eyed peas |16
+|chicago |15
+|usher |14
+|rod stewart |14
+|aretha franklin |14
+|katy perry |14
+|phil collins |13
+|===
+
+=== Build and run
+
+Build and run the test with this single command.
+
+[source,sh]
+----
+mvn clean test
+----
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-billboard-aggr/README.md b/examples/camel-example-billboard-aggr/README.md
deleted file mode 100644
index 8c732aa..0000000
--- a/examples/camel-example-billboard-aggr/README.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# Billboard TOP100 aggregation example
-
-### Introduction
-The `billboard_lyrics_1964-2015` CSV dataset contains the TOP100 songs with lyrics for each year.
-We can compute the TOP20 artists with most songs on Billboard using Split and Aggregate EIPs.
-Build statistics is not the Camel core business but, as shown, you can easily do it!
-
-This is the final result:
-
-Artist | Presences
---- | ---
-madonna | 35
-elton john | 26
-mariah carey | 25
-stevie wonder | 22
-janet jackson | 22
-michael jackson | 22
-whitney houston | 19
-rihanna | 19
-taylor swift | 19
-pink | 17
-the beatles | 17
-kelly clarkson | 17
-britney spears | 16
-the black eyed peas | 16
-chicago | 15
-usher | 14
-rod stewart | 14
-aretha franklin | 14
-katy perry | 14
-phil collins | 13
-
-### Build and run
-Build and run the test with this single command.
-```sh
-mvn clean test
-```
-
-### Forum, Help, etc
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may have.
-Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-cafe-endpointdsl/README.adoc b/examples/camel-example-cafe-endpointdsl/README.adoc
new file mode 100644
index 0000000..e36c463
--- /dev/null
+++ b/examples/camel-example-cafe-endpointdsl/README.adoc
@@ -0,0 +1,44 @@
+== Cafe Example with Endpoint DSL
+
+=== Introduction
+
+This example uses the Camel Endpoint DSL to configure Camel endpoints
+using a type-safe Java endpoint DSL (eg fluent builder style).
+
+This example shows how to work with splitter and aggregator to implement
+a Cafe demo.
+
+First it uses the splitter to dispatch the order, then sends the orders
+to barista by checking if the coffee is hot or cold. When the coffee is
+ready, we use a aggregate to gather the drinks for waiter to deliver.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java+` directory.
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cafe-endpointdsl/README.md b/examples/camel-example-cafe-endpointdsl/README.md
deleted file mode 100644
index 59f1f06..0000000
--- a/examples/camel-example-cafe-endpointdsl/README.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Cafe Example with Endpoint DSL
-
-### Introduction
-
-This example uses the Camel Endpoint DSL to configure Camel endpoints using a type-safe Java endpoint DSL
-(eg fluent builder style).
-
-This example shows how to work with splitter and aggregator to implement a Cafe demo.
-
-First it uses the splitter to dispatch the order, then sends the orders to barista by checking
-if the coffee is hot or cold. When the coffee is ready, we use a aggregate to gather the drinks for waiter to deliver.
-
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example type
-
- mvn camel:run
-
-You can see the routing rules by looking at the java code in the
-`src/main/java` directory.
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cafe/README.adoc b/examples/camel-example-cafe/README.adoc
new file mode 100644
index 0000000..1cebf75
--- /dev/null
+++ b/examples/camel-example-cafe/README.adoc
@@ -0,0 +1,42 @@
+== Cafe Example
+
+=== Introduction
+
+This example shows how to work with splitter and aggregator to implement
+a Cafe demo.
+
+First It uses the splitter to dispatch the order, then sends the orders
+to barista by checking if the coffee is hot or cold. When the coffee is
+ready, we use a aggregate to gather the drinks for waiter to deliver.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java directory+` and the Spring XML configuration lives in
+`+src/main/resources/META-INF/spring+`
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cafe/README.md b/examples/camel-example-cafe/README.md
deleted file mode 100644
index 543fac7..0000000
--- a/examples/camel-example-cafe/README.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Cafe Example
-
-### Introduction
-
-This example shows how to work with splitter and aggregator to implement a Cafe demo.
-
-First It uses the splitter to dispatch the order, then sends the orders to barista by checking
-if the coffee is hot or cold. When the coffee is ready, we use a aggregate to gather the drinks for waiter to deliver.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example type
-
- mvn camel:run
-
-You can see the routing rules by looking at the java code in the
-`src/main/java directory` and the Spring XML configuration lives in
-`src/main/resources/META-INF/spring`
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cassandra-kubernetes/LICENSE.md b/examples/camel-example-cassandra-kubernetes/LICENSE.md
deleted file mode 100644
index 8f71f43..0000000
--- a/examples/camel-example-cassandra-kubernetes/LICENSE.md
+++ /dev/null
@@ -1,202 +0,0 @@
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "{}"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright {yyyy} {name of copyright owner}
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
diff --git a/examples/camel-example-cassandra-kubernetes/ReadMe.md b/examples/camel-example-cassandra-kubernetes/README.adoc
similarity index 86%
rename from examples/camel-example-cassandra-kubernetes/ReadMe.md
rename to examples/camel-example-cassandra-kubernetes/README.adoc
index d5002bc..33a5240 100644
--- a/examples/camel-example-cassandra-kubernetes/ReadMe.md
+++ b/examples/camel-example-cassandra-kubernetes/README.adoc
@@ -1,48 +1,51 @@
-# Camel Cassandraql route on Kubernetes cluster
+== Camel Cassandraql route on Kubernetes cluster
-This quickstart run in a Java standalone container, using Spring with Apache Camel (Cassandraql component).
+This quickstart run in a Java standalone container, using Spring with
+Apache Camel (Cassandraql component).
This example is based on:
-- Minikube 0.21.0 (Kubernetes version >= 1.7)
-- Fabric8 Maven Plugin (version >= 3.5)
+* Minikube 0.21.0 (Kubernetes version >= 1.7)
+* Fabric8 Maven Plugin (version >= 3.5)
First thing you'll need to do is preparing the environment.
-Don't forget to use a bit more memory for your Minikube for running this example:
+Don't forget to use a bit more memory for your Minikube for running this
+example:
-```
+....
$ minikube start --memory 5120 --cpus=4
-```
+....
-Once your Minikube node is up and running you'll need to run the following command.
-In your src/main/resource/fabric8/ folder you'll find two yaml file. Run the following command using them:
+Once your Minikube node is up and running you'll need to run the
+following command. In your src/main/resource/fabric8/ folder you'll find
+two yaml file. Run the following command using them:
-```
+....
$ kubectl create -f src/main/resources/fabric8/cassandra-service.yaml
$ kubectl create -f src/main/resources/fabric8/cassandra-statefulset.yaml
-```
+....
To check the correct startup of the cluster run the following command:
-```
+....
$ kubectl get statefulsets
NAME DESIRED CURRENT AGE
cassandra 2 2 2h
-```
+....
and check the status of the pods
-```
+....
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
cassandra-0 1/1 Running 0 2h
cassandra-1 1/1 Running 0 2h
-```
+....
You can also verify the health of your cluster by running
-```
+....
$ kubectl exec <pod_name> -it nodetool status
Datacenter: DC1-K8Demo
======================
@@ -51,28 +54,35 @@ Status=Up/Down
-- Address Load Tokens Owns (effective) Host ID Rack
UN 172.17.0.4 212.14 KiB 32 53.1% 9bf81ccd-4aa1-451b-b56e-c16c5ee04836 Rack1-K8Demo
UN 172.17.0.6 170.08 KiB 32 46.9% 69cc6f60-9ccf-439d-a298-b79b643c1586 Rack1-K8Demo
-```
+....
-### Building and running
+=== Building and running
Navigate to the project folder and the example can be built with
- mvn clean -Pkubernetes-install fabric8:deploy
+....
+mvn clean -Pkubernetes-install fabric8:deploy
+....
-When the example runs in fabric8, you can use the Kubectl command tool to inspect the status
+When the example runs in fabric8, you can use the Kubectl command tool
+to inspect the status
To list all the running pods:
- kubectl get pods
+....
+kubectl get pods
+....
-Then find the name of the pod that runs this quickstart, and output the logs from the running pods with:
+Then find the name of the pod that runs this quickstart, and output the
+logs from the running pods with:
- kubectl logs <name of pod>
+....
+kubectl logs <name of pod>
+....
and you should see something like this:
-
-```
+....
2017-08-06 10:43:52,209 [main ] INFO ClassPathXmlApplicationContext - Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@1068e947: startup date [Sun Aug 06 10:43:52 UTC 2017]; root of context hierarchy
2017-08-06 10:43:52,244 [main ] INFO XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [META-INF/spring/camel-context.xml]
2017-08-06 10:43:53,425 [main ] INFO GuavaCompatibility - Detected Guava >= 19 in the classpath, using modern compatibility layer
@@ -96,19 +106,31 @@ and you should see something like this:
2017-08-06 10:43:59,586 [2 - timer://foo] INFO cassandra-route - Query result set [Row[1, oscerd]]
2017-08-06 10:44:04,575 [2 - timer://foo] INFO cassandra-route - Query result set [Row[1, oscerd]]
2017-08-06 10:44:09,577 [2 - timer://foo] INFO cassandra-route - Query result set [Row[1, oscerd]]
-```
+....
-### Cleanup
+=== Cleanup
Run following to undeploy the application and cassandra nodes
-```
+
+....
$ mvn -Pkubernetes-install fabric8:undeploy
$ kubectl create -f src/main/resources/fabric8/cassandra-service.yaml
$ kubectl create -f src/main/resources/fabric8/cassandra-statefulset.yaml
-```
+....
Make sure no pod is running
-```
+
+....
$ kubectl get pods
No resources found.
-```
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cdi-aws-s3/README.adoc b/examples/camel-example-cdi-aws-s3/README.adoc
new file mode 100644
index 0000000..87cf20f
--- /dev/null
+++ b/examples/camel-example-cdi-aws-s3/README.adoc
@@ -0,0 +1,47 @@
+== AWS S3 Example - CDI
+
+=== Introduction
+
+This example illustrates the integration between Camel, CDI and AWS S3.
+
+The `+camel-cdi+` and `+camel-aws-s3+` components are used in this
+example..
+
+Don't forget to add your bucket name and your credentials in the
+Application.java file before compiling. Actually AccessKey and SecretKey
+are equals to `XXXXXX', while the bucketName in the route is named
+`bucketName'
+
+=== Build
+
+You can build this example using:
+
+[source,sh]
+----
+$ mvn package
+----
+
+=== Run
+
+You can run this example using:
+
+[source,sh]
+----
+$ mvn camel:run
+----
+
+When the Camel application runs, you should the files from your bucket
+been downloaded and saved into target/s3out directory with their
+filename.
+
+The Camel application can be stopped pressing ctrl+c in the shell.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cdi-aws-s3/README.md b/examples/camel-example-cdi-aws-s3/README.md
deleted file mode 100644
index 232e176..0000000
--- a/examples/camel-example-cdi-aws-s3/README.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# AWS S3 Example - CDI
-
-### Introduction
-
-This example illustrates the integration between Camel, CDI and AWS S3.
-
-The `camel-cdi` and `camel-aws-s3` components are used in this example..
-
-Don't forget to add your bucket name and your credentials in the Application.java file before compiling. Actually AccessKey and SecretKey are equals to 'XXXXXX', while the bucketName in the route is named 'bucketName'
-
-### Build
-
-You can build this example using:
-
-```sh
-$ mvn package
-```
-
-### Run
-
-You can run this example using:
-
-```sh
-$ mvn camel:run
-```
-
-When the Camel application runs, you should the files from your bucket been downloaded and saved into target/s3out directory with their filename.
-
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-cdi-cassandraql/README.md b/examples/camel-example-cdi-cassandraql/README.adoc
similarity index 87%
rename from examples/camel-example-cdi-cassandraql/README.md
rename to examples/camel-example-cdi-cassandraql/README.adoc
index 88515ba..2fb1634 100644
--- a/examples/camel-example-cdi-cassandraql/README.md
+++ b/examples/camel-example-cdi-cassandraql/README.adoc
@@ -1,27 +1,33 @@
-# Cassandraql Example - CDI
+== Cassandraql Example - CDI
-### Introduction
+=== Introduction
-This example illustrates the integration between Camel, CDI and Cassandra.
+This example illustrates the integration between Camel, CDI and
+Cassandra.
-The example get the list of pods from a Kubernetes cluster and print name and status of each one of the pods returned.
+The example get the list of pods from a Kubernetes cluster and print
+name and status of each one of the pods returned.
-The `camel-cdi`, `camel-core` and `camel-cassandraql` components are used in this example.
-The example assumes you have a running Cassandra Cluster in your environment. We will use Docker to spin up this cluster.
+The `+camel-cdi+`, `+camel-core+` and `+camel-cassandraql+` components
+are used in this example. The example assumes you have a running
+Cassandra Cluster in your environment. We will use Docker to spin up
+this cluster.
-By default cluster requires significant amount of RAM memory (approx. 12GB).
-You can limit memory of docker container specifying parameter: `--env MAX_HEAP_SIZE`
+By default cluster requires significant amount of RAM memory (approx.
+12GB). You can limit memory of docker container specifying parameter:
+`+--env MAX_HEAP_SIZE+`
As first step we will need to run a single node cluster:
-```
+
+....
$ docker run --name master_node --env MAX_HEAP_SIZE='800M' -dt oscerd/cassandra
$ docker run --name node1 --env MAX_HEAP_SIZE='800M' -d -e SEED="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' master_node)" oscerd/cassandra
$ docker run --name node2 --env MAX_HEAP_SIZE='800M' -d -e SEED="$(docker inspect --format='{{ .NetworkSettings.IPAddress }}' master_node)" oscerd/cassandra
-```
+....
We now have three nodes in our cluster.
-```
+....
$ docker exec -ti master_node /opt/cassandra/bin/nodetool status
Datacenter: datacenter1
=======================
@@ -31,36 +37,37 @@ Status=Up/Down
UN 172.17.0.3 102.67 KiB 256 65.9% 1a985c48-33a1-44aa-b7e9-f1a3620a6482 rack1
UN 172.17.0.2 107.64 KiB 256 68.2% da54ce5e-6433-4ea0-b2c3-fbc6c63ea955 rack1
UN 172.17.0.4 15.42 KiB 256 65.8% 0f2ba25a-37b0-4f27-a10a-d9a44655396a rack1
-```
+....
-From your local [Apache Cassandra](http://cassandra.apache.org/) directory run the `cqlsh` command:
+From your local http://cassandra.apache.org/[Apache Cassandra] directory
+run the `+cqlsh+` command:
-```
+....
<LOCAL_CASSANDRA_HOME>/bin/cqlsh $(docker inspect --format='{{ .NetworkSettings.IPAddress }}' master_node)
-```
+....
You should see the Cqlsh prompt
-```
+....
Connected to Test Cluster at 172.17.0.2:9042.
[cqlsh 5.0.1 | Cassandra 3.6 | CQL spec 3.4.2 | Native protocol v4]
Use HELP for help.
cqlsh>
-```
+....
-Let's create a namespace `test` with a table `users`
+Let's create a namespace `+test+` with a table `+users+`
-```
+....
create keyspace test with replication = {'class':'SimpleStrategy', 'replication_factor':3};
use test;
create table users ( id int primary key, name text );
insert into users (id,name) values (1, 'oscerd');
quit;
-```
+....
run a simple query to check everything works:
-```
+....
cqlsh> use test;
cqlsh:test> select * from users;
@@ -70,28 +77,32 @@ cqlsh:test> select * from users;
(1 rows)
cqlsh:test>
-```
+....
-Remember to edit the apache-deltaspike.properties file to add the correct addresses of the different nodes running in Docker.
+Remember to edit the apache-deltaspike.properties file to add the
+correct addresses of the different nodes running in Docker.
-### Build
+=== Build
You will need to build this example first:
-```sh
+[source,sh]
+----
$ mvn install
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ mvn compile camel:run
-```
+----
When the Camel application runs, you should see the following result:
-```
+
+....
2016-07-24 15:33:50,812 [cdi.Main.main()] INFO Version - WELD-000900: 2.3.5 (Final)
Jul 24, 2016 3:33:50 PM org.apache.deltaspike.core.impl.config.EnvironmentPropertyConfigSourceProvider <init>
INFO: Custom config found by DeltaSpike. Name: 'META-INF/apache-deltaspike.properties', URL: 'file:/home/oscerd/workspace/apache-camel/camel/examples/camel-example-cdi-cassandraql/target/classes/META-INF/apache-deltaspike.properties'
@@ -125,14 +136,13 @@ INFO: Computed the following DeltaSpike ProjectStage: Production
2016-07-24 15:33:52,987 [cdi.Main.main()] INFO DefaultCamelContext - Apache Camel 2.18.0 (CamelContext: camel-example-cassandraql-cdi) started in 0.742 seconds
2016-07-24 15:33:53,018 [cdi.Main.main()] INFO Bootstrap - WELD-ENV-002003: Weld SE container STATIC_INSTANCE initialized
2016-07-24 15:33:54,041 [ timer://stream] INFO route1 - Result from query [Row[1, oscerd]]
+....
-```
-
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-If you run the query again you should see a `davsclaus` entry too:
+If you run the query again you should see a `+davsclaus+` entry too:
-```
+....
cqlsh> use test;
cqlsh:test> select * from users;
@@ -143,13 +153,14 @@ cqlsh:test> select * from users;
(2 rows)
cqlsh:test>
-```
+....
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-cdi-kubernetes/README.md b/examples/camel-example-cdi-kubernetes/README.adoc
similarity index 50%
rename from examples/camel-example-cdi-kubernetes/README.md
rename to examples/camel-example-cdi-kubernetes/README.adoc
index 1fba7f9..41f87db 100644
--- a/examples/camel-example-cdi-kubernetes/README.md
+++ b/examples/camel-example-cdi-kubernetes/README.adoc
@@ -1,53 +1,65 @@
-# Kubernetes Example - CDI
+== Kubernetes Example - CDI
-### Introduction
+=== Introduction
-This example illustrates the integration between Camel, CDI and Kubernetes.
+This example illustrates the integration between Camel, CDI and
+Kubernetes.
The example gets the list of pods from a Kubernetes cluster and emulates
-the output of the `kubectl get pods` command.
-
-The `camel-cdi` and `camel-kubernetes` components are used in this example.
-The example assumes you have a running Kubernetes cluster in your environment.
-For example you can use [minikube](https://github.com/kubernetes/minikube)
-or the [vagrant openshift image](https://github.com/fabric8io/fabric8-installer/tree/master/vagrant/openshift) from
-[Fabric8 team](http://fabric8.io/).
-
-By default, the example use the `KUBERNETES_MASTER` environment variable
-to retrieve the Kubernetes master URL. Besides, it tries to find the current
-login token and namespace by parsing the users `~/.kube/config` file.
-However, you can edit the `application.properties` file to override the default
-and provide the Kubernetes master URL and OAuth token for your environment.
-
-To retrieve the tokens in your kubeconfig file, you can execute the following command:
-```sh
+the output of the `+kubectl get pods+` command.
+
+The `+camel-cdi+` and `+camel-kubernetes+` components are used in this
+example. The example assumes you have a running Kubernetes cluster in
+your environment. For example you can use
+https://github.com/kubernetes/minikube[minikube] or the
+https://github.com/fabric8io/fabric8-installer/tree/master/vagrant/openshift[vagrant
+openshift image] from http://fabric8.io/[Fabric8 team].
+
+By default, the example use the `+KUBERNETES_MASTER+` environment
+variable to retrieve the Kubernetes master URL. Besides, it tries to
+find the current login token and namespace by parsing the users
+`+~/.kube/config+` file. However, you can edit the
+`+application.properties+` file to override the default and provide the
+Kubernetes master URL and OAuth token for your environment.
+
+To retrieve the tokens in your kubeconfig file, you can execute the
+following command:
+
+[source,sh]
+----
$ kubectl config view -o jsonpath='{range .users[?(@.user.token != "")]}{.name}{":\t"}{.user.token}{"\n"}{end}'
-```
+----
-Alternatively, if you're using OpenShift, you can retrieve the token for the current user with:
-```sh
+Alternatively, if you're using OpenShift, you can retrieve the token for
+the current user with:
+
+[source,sh]
+----
$ oc whoami -t
-```
+----
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ KUBERNETES_MASTER="https://$(minikube ip):8443/" mvn camel:run
-```
+----
+
+When the Camel application runs, you should see the pods list being
+logged periodically, e.g.:
-When the Camel application runs, you should see the pods list being logged
-periodically, e.g.:
-```
+....
2016-08-22 18:29:46,449 [ timer://client] INFO kubernetes-client - We currently have 11 pods:
NAME READY STATUS RESTARTS AGE
content-repository-yhg9u 1/1 Running 34 49d
@@ -61,18 +73,18 @@ mysql-5-f8trz 1/1 Running 8 13d
nexus-5j60s 1/1 Running 71 49d
router-1-7eiu5 2/2 Running 26 49d
spring-boot-camel-rest-s-13-559vm 1/1 Running 0 6h
+....
-```
-
-The timer has a `period` option equals to `10s`.
+The timer has a `+period+` option equals to `+10s+`.
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-cdi-metrics/README.md b/examples/camel-example-cdi-metrics/README.adoc
similarity index 67%
rename from examples/camel-example-cdi-metrics/README.md
rename to examples/camel-example-cdi-metrics/README.adoc
index 94574d3..9886f56 100644
--- a/examples/camel-example-cdi-metrics/README.md
+++ b/examples/camel-example-cdi-metrics/README.adoc
@@ -1,44 +1,50 @@
-# Metrics Example - CDI
+== Metrics Example - CDI
-### Introduction
+=== Introduction
-This example illustrates the integration between Camel, Dropwizard Metrics and CDI.
+This example illustrates the integration between Camel, Dropwizard
+Metrics and CDI.
-The example emulates an unreliable service that processes a continuous stream of events.
-The unreliable service fails randomly and metrics get collected to report
-the number of generated events as well as the total number of attempted, redelivered,
-failed and successful calls to the service. A SLF4J reporter is configured so that
-these metrics details get logged every 10 seconds in the console.
+The example emulates an unreliable service that processes a continuous
+stream of events. The unreliable service fails randomly and metrics get
+collected to report the number of generated events as well as the total
+number of attempted, redelivered, failed and successful calls to the
+service. A SLF4J reporter is configured so that these metrics details
+get logged every 10 seconds in the console.
-The example is implemented in Java with CDI dependency injection. It uses JBoss Weld
-as the minimal CDI container to run the application, though you can run the application
-in any CDI compliant container.
+The example is implemented in Java with CDI dependency injection. It
+uses JBoss Weld as the minimal CDI container to run the application,
+though you can run the application in any CDI compliant container.
-The `camel-cdi` and `camel-metrics` components are used in this example.
-The `camel-test-cdi` module is used for the JUnit test runner.
-Besides, the Metrics CDI extension is used so that metrics can be injected
-and custom metrics registered via CDI. For instance, a ratio gauge is registered
-to monitor the success rate, that is the ratio of success calls on the number
-of generated events.
+The `+camel-cdi+` and `+camel-metrics+` components are used in this
+example. The `+camel-test-cdi+` module is used for the JUnit test
+runner. Besides, the Metrics CDI extension is used so that metrics can
+be injected and custom metrics registered via CDI. For instance, a ratio
+gauge is registered to monitor the success rate, that is the ratio of
+success calls on the number of generated events.
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ mvn camel:run
-```
+----
-When the Camel application runs, you should see the calls to the 'unreliable-service' being logged to the console, e.g.:
-```
+When the Camel application runs, you should see the calls to the
+`unreliable-service' being logged to the console, e.g.:
+
+....
2016-01-18 15:19:04,390 [ timer://stream] INFO unreliable-service - Processing event #8...
2016-01-18 15:19:06,399 [ timer://stream] ERROR unreliable-service - Failed processing event #8
2016-01-18 15:19:06,400 [ timer://stream] INFO unreliable-service - Processing event #9...
@@ -52,25 +58,27 @@ When the Camel application runs, you should see the calls to the 'unreliable-ser
2016-01-18 15:19:11,424 [ timer://stream] INFO unreliable-service - Processing event #13...
2016-01-18 15:19:12,428 [ timer://stream] WARN unreliable-service - Processed event #13 after 1 retries
2016-01-18 15:19:12,430 [ timer://stream] INFO unreliable-service - Successfully processed event #13
-```
+....
And every 10 seconds, the metrics report, e.g.:
-```
+
+....
2016-01-18 15:19:14,360 [rter-1-thread-1] INFO metrics - type=GAUGE, name=success-ratio, value=0.9314661799835947
2016-01-18 15:19:14,361 [rter-1-thread-1] INFO metrics - type=METER, name=attempt, count=26, mean_rate=1.3682531895692165, m1=1.245416192969619, m5=1.209807850571521, m15=1.2033118138834105, rate_unit=events/second
2016-01-18 15:19:14,361 [rter-1-thread-1] INFO metrics - type=METER, name=error, count=2, mean_rate=0.25121358141009453, m1=0.4, m5=0.4, m15=0.4, rate_unit=events/second
2016-01-18 15:19:14,361 [rter-1-thread-1] INFO metrics - type=METER, name=generated, count=15, mean_rate=0.7210025396112787, m1=0.6455184225121126, m5=0.6098087536676114, m15=0.6033118478925024, rate_unit=events/second
2016-01-18 15:19:14,361 [rter-1-thread-1] INFO metrics - type=METER, name=redelivery, count=11, mean_rate=0.6872842357052532, m1=0.9385926899562456, m5=0.9868864401928024, m15=0.995580155717569, rate_unit=events/second
2016-01-18 15:19:14,361 [rter-1-thread-1] INFO metrics - type=METER, name=success, count=12, mean_rate=0.5768131773739456, m1=0.6012785791263936, m5=0.6000546385677541, m15=0.6000061386568257, rate_unit=events/second
-```
+....
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-cdi-properties/README.md b/examples/camel-example-cdi-properties/README.adoc
similarity index 53%
rename from examples/camel-example-cdi-properties/README.md
rename to examples/camel-example-cdi-properties/README.adoc
index ac0eb4b..56e4b47 100644
--- a/examples/camel-example-cdi-properties/README.md
+++ b/examples/camel-example-cdi-properties/README.adoc
@@ -1,44 +1,48 @@
-# Properties Example - CDI
+== Properties Example - CDI
-### Introduction
+=== Introduction
-This example illustrates the integration between Camel, DeltaSpike and CDI
-for configuration properties.
+This example illustrates the integration between Camel, DeltaSpike and
+CDI for configuration properties.
-The example uses DeltaSpike to source configuration properties and creates
-a `PropertiesComponent` bean that Camel uses to resolve property placeholders
-in endpoint URIs. Besides, the application uses DeltaSpike's `@ConfigProperty`
-qualifier to directly inject configuration property values. More information
-can be found in [DeltaSpike configuration mechanism][] documentation.
+The example uses DeltaSpike to source configuration properties and
+creates a `+PropertiesComponent+` bean that Camel uses to resolve
+property placeholders in endpoint URIs. Besides, the application uses
+DeltaSpike's `+@ConfigProperty+` qualifier to directly inject
+configuration property values. More information can be found in
+http://deltaspike.apache.org/documentation/configuration.html[DeltaSpike
+configuration mechanism] documentation.
-The example is implemented in Java with CDI dependency injection.
-It uses JBoss Weld as the minimal CDI container to run the application,
+The example is implemented in Java with CDI dependency injection. It
+uses JBoss Weld as the minimal CDI container to run the application,
though you can run the application in any CDI compliant container.
-The `camel-cdi` and `camel-core` components are used in this example.
-The `camel-test-cdi` module is used for the JUnit test runner.
+The `+camel-cdi+` and `+camel-core+` components are used in this
+example. The `+camel-test-cdi+` module is used for the JUnit test
+runner.
-[DeltaSpike configuration mechanism]: http://deltaspike.apache.org/documentation/configuration.html
-
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ mvn camel:run
-```
+----
When the Camel application runs, you should see the following messages
being logged to the console, e.g.:
-```
+
+....
2016-01-28 15:02:46,223 [cdi.Main.main()] INFO CdiCamelExtension - Camel CDI is starting Camel context [hello]
2016-01-28 15:02:46,223 [cdi.Main.main()] INFO DefaultCamelContext - Apache Camel 2.17.0 (CamelContext: hello) is starting
...
@@ -46,15 +50,16 @@ being logged to the console, e.g.:
2016-01-28 15:02:46,461 [cdi.Main.main()] INFO DefaultCamelContext - Total 1 routes, of which 1 is started.
2016-01-28 15:02:46,461 [cdi.Main.main()] INFO DefaultCamelContext - Apache Camel 2.17.0 (CamelContext: hello) started in 0.238 seconds
2016-01-28 15:02:46,661 [cdi.Main.main()] INFO route1 - Hello from CamelContext (hello)
-```
+....
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-cdi-rest-servlet/README.md b/examples/camel-example-cdi-rest-servlet/README.adoc
similarity index 72%
rename from examples/camel-example-cdi-rest-servlet/README.md
rename to examples/camel-example-cdi-rest-servlet/README.adoc
index ca228b7..edc68bc 100644
--- a/examples/camel-example-cdi-rest-servlet/README.md
+++ b/examples/camel-example-cdi-rest-servlet/README.adoc
@@ -1,39 +1,42 @@
-# REST DSL / Servlet Example - CDI
+== REST DSL / Servlet Example - CDI
-### Introduction
+=== Introduction
-This example illustrates the Camel REST DSL being used in a Java application
-that uses CDI as dependency injection framework.
+This example illustrates the Camel REST DSL being used in a Java
+application that uses CDI as dependency injection framework.
-The example uses the [`camel-servlet`][Servlet component] component
-as the underlying HTTP engine to service REST APIs defined with the Camel
-REST DSL.
+The example uses the
+http://camel.apache.org/servlet.html[`+camel-servlet+`] component as the
+underlying HTTP engine to service REST APIs defined with the Camel REST
+DSL.
-This example uses JBoss Weld as the minimal CDI container to run the application,
-and is deployed in Jetty as Servlet engine, though you can run the application
-in any CDI compliant container and Servlet container.
+This example uses JBoss Weld as the minimal CDI container to run the
+application, and is deployed in Jetty as Servlet engine, though you can
+run the application in any CDI compliant container and Servlet
+container.
-[Servlet component]: http://camel.apache.org/servlet.html
-
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ mvn jetty:run
-```
+----
When the Camel application runs, you should see the following messages
being logged to the console, e.g.:
-```
+
+....
2016-01-29 18:52:57,591 [main ] INFO servletWeldServlet - WELD-ENV-001008: Initialize Weld using ServletContainerInitializer
2016-01-29 18:52:58,313 [main ] INFO servletJetty - WELD-ENV-001200: Jetty 7.2+ detected, CDI injection will be available in Servlets and Filters. Injection into Listeners should work on Jetty 9.1.1 and newer.
2016-01-29 18:52:58,885 [main ] INFO CdiCamelExtension - Camel CDI is starting Camel context [hello]
@@ -48,36 +51,38 @@ being logged to the console, e.g.:
[INFO] Started ServerConnector@63f7f62{HTTP/1.1}{0.0.0.0:8080}
[INFO] Started @12857ms
[INFO] Started Jetty Server
-```
+....
-Then you can open the following URL into your Web browser, <http://localhost:8080/camel/say/hello/>, and
-being responded with `Hello World!`.
+Then you can open the following URL into your Web browser,
+http://localhost:8080/camel/say/hello/, and being responded with
+`+Hello World!+`.
Otherwise, in a separate prompt, by running:
-```
+....
curl http://localhost:8080/camel/say/hello/Antonin
-```
+....
You should being responded with the following message:
-```
+....
Hello Antonin, I'm CamelContext(hello)!
-```
+....
And see the following message being logged by the Camel application:
-```
+....
016-01-29 19:03:20,293 [tp1211352799-18] INFO route2 - Hello Antonin, I'm CamelContext(hello)!
-```
+....
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-cdi-test/README.adoc b/examples/camel-example-cdi-test/README.adoc
new file mode 100644
index 0000000..73f0a85
--- /dev/null
+++ b/examples/camel-example-cdi-test/README.adoc
@@ -0,0 +1,75 @@
+== Testing Example - CDI
+
+=== Introduction
+
+This example demonstrates the testing features that are provided as part
+of the integration between Camel and CDI.
+
+The example is implemented in Java with CDI dependency injection. It
+uses JBoss Weld as the minimal CDI container to run the application,
+though you can run the application in any CDI compliant container.
+
+This example comes with a series of test classes that each demonstrates
+particular features provided by the `+camel-test-cdi+` module:
+
+[width="100%",cols="33%,67%",options="header",]
+|===
+|Test class |Description
+|link:src/test/java/org/apache/camel/example/cdi/test/AdviceTest.java[`+AdviceTest+`]
+|Adds a test route using Camel advice API
+
+|link:src/test/java/org/apache/camel/example/cdi/test/AlternativeTest.java[`+AlternativeTest+`]
+|Mocks a bean used in a Camel route with a CDI alternative
+
+|link:src/test/java/org/apache/camel/example/cdi/test/ApplicationScopedTest.java[`+ApplicationScopedTest+`]
+|A stateful `+@ApplicationScoped+` test class
+
+|link:src/test/java/org/apache/camel/example/cdi/test/CustomContextTest.java[`+CustomContextTest+`]
+|Declares a custom Camel context bean for test purpose
+
+|link:src/test/java/org/apache/camel/example/cdi/test/OrderTest.java[`+OrderTest+`]
+|Orders the test methods execution with `+@Order+`
+|===
+
+=== Build
+
+You can build this example using:
+
+[source,sh]
+----
+$ mvn package
+----
+
+=== Run
+
+You can run this example using:
+
+[source,sh]
+----
+$ mvn camel:run
+----
+
+When the Camel application runs, you should see the following message
+being logged to the console, e.g.:
+
+....
+2016-03-04 17:54:04,147 [cdi.Main.main()] INFO route - Hello from camel-test-cdi
+....
+
+The Camel application can be stopped pressing ctrl+c in the shell.
+
+You should see the following message being logged to the console:
+
+....
+2016-03-04 17:54:18,725 [Thread-1 ] INFO route - Bye from camel-test-cdi
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cdi-test/README.md b/examples/camel-example-cdi-test/README.md
deleted file mode 100644
index 03fd646..0000000
--- a/examples/camel-example-cdi-test/README.md
+++ /dev/null
@@ -1,67 +0,0 @@
-# Testing Example - CDI
-
-### Introduction
-
-This example demonstrates the testing features that are provided as part of
-the integration between Camel and CDI.
-
-The example is implemented in Java with CDI dependency injection. It uses JBoss Weld
-as the minimal CDI container to run the application, though you can run the application
-in any CDI compliant container.
-
-This example comes with a series of test classes that each demonstrates particular
-features provided by the `camel-test-cdi` module:
-
-| Test class | Description |
-| --------------------------- | --------------------------------------------------------- |
-| [`AdviceTest`][] | Adds a test route using Camel advice API |
-| [`AlternativeTest`][] | Mocks a bean used in a Camel route with a CDI alternative |
-| [`ApplicationScopedTest`][] | A stateful `@ApplicationScoped` test class |
-| [`CustomContextTest`][] | Declares a custom Camel context bean for test purpose |
-| [`OrderTest`][] | Orders the test methods execution with `@Order` |
-
-[`AdviceTest`]: src/test/java/org/apache/camel/example/cdi/test/AdviceTest.java
-[`AlternativeTest`]: src/test/java/org/apache/camel/example/cdi/test/AlternativeTest.java
-[`ApplicationScopedTest`]: src/test/java/org/apache/camel/example/cdi/test/ApplicationScopedTest.java
-[`CustomContextTest`]: src/test/java/org/apache/camel/example/cdi/test/CustomContextTest.java
-[`OrderTest`]: src/test/java/org/apache/camel/example/cdi/test/OrderTest.java
-
-### Build
-
-You can build this example using:
-
-```sh
-$ mvn package
-```
-
-### Run
-
-You can run this example using:
-
-```sh
-$ mvn camel:run
-```
-
-When the Camel application runs, you should see the following message being logged
-to the console, e.g.:
-
-```
-2016-03-04 17:54:04,147 [cdi.Main.main()] INFO route - Hello from camel-test-cdi
-```
-
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
-
-You should see the following message being logged to the console:
-
-```
-2016-03-04 17:54:18,725 [Thread-1 ] INFO route - Bye from camel-test-cdi
-```
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-cdi-xml/README.md b/examples/camel-example-cdi-xml/README.adoc
similarity index 82%
rename from examples/camel-example-cdi-xml/README.md
rename to examples/camel-example-cdi-xml/README.adoc
index 4c0e470..fa401d3 100644
--- a/examples/camel-example-cdi-xml/README.md
+++ b/examples/camel-example-cdi-xml/README.adoc
@@ -1,47 +1,52 @@
-# Camel XML Example - CDI
+== Camel XML Example - CDI
-### Introduction
+=== Introduction
This example illustrates the use of Camel XML configuration files into
Camel CDI applications.
-While CDI favors a typesafe dependency injection mechanism, it may be useful
-to reuse existing Camel XML configuration files into a Camel CDI application.
-In other use cases, it might be handy to rely on the Camel XML DSL to configure
-its Camel context(s).
+While CDI favors a typesafe dependency injection mechanism, it may be
+useful to reuse existing Camel XML configuration files into a Camel CDI
+application. In other use cases, it might be handy to rely on the Camel
+XML DSL to configure its Camel context(s).
-So that example demonstrates how to import a Camel XML configuration file
-and the level of interoperability between the Camel XML DSL and CDI.
+So that example demonstrates how to import a Camel XML configuration
+file and the level of interoperability between the Camel XML DSL and
+CDI.
-It is implemented in Java with CDI dependency injection.
-It uses JBoss Weld as the minimal CDI container to run the application,
-though you can run the application in any CDI compliant container.
+It is implemented in Java with CDI dependency injection. It uses JBoss
+Weld as the minimal CDI container to run the application, though you can
+run the application in any CDI compliant container.
-It is required to have the `camel-core-xml` dependency in the classpath
-when importing Camel XML configuration files using Camel CDI.
+It is required to have the `+camel-core-xml+` dependency in the
+classpath when importing Camel XML configuration files using Camel CDI.
-The `camel-cdi` and `camel-stream` components are used in this example.
-The `camel-test-cdi` module is used for the JUnit test runner.
+The `+camel-cdi+` and `+camel-stream+` components are used in this
+example. The `+camel-test-cdi+` module is used for the JUnit test
+runner.
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ mvn camel:run
-```
+----
When the Camel application runs, you should see the following messages
being logged to the console, e.g.:
-```
+
+....
2016-04-26 17:08:49,021 [cdi.Main.main()] INFO Version - WELD-000900: 2.3.4 (Final)
2016-04-26 17:08:51,805 [cdi.Main.main()] INFO CdiCamelExtension - Camel CDI is starting Camel context [cdi-camel-xml]
2016-04-26 17:08:51,806 [cdi.Main.main()] INFO DefaultCamelContext - Apache Camel 2.18.0 (CamelContext: cdi-camel-xml) is starting
@@ -59,14 +64,14 @@ being logged to the console, e.g.:
██║ ██║ ██║███████╗ ██║ ╚═╝ ██║██║ ██║ ██║ ██║ ██║██║██╔╝ ██╗
╚═╝ ╚═╝ ╚═╝╚══════╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝ ╚═╝ ╚═╝╚═╝╚═╝ ╚═╝
Which pill (red|blue)?:
+....
-```
+You're being prompted which pill Neo should be taking. If he chooses the
+red one, Neo gets unplugged from the Matrix and the red pill serves as a
+location device to track his position into the farm to broadcast it and
+have the rebellion rescuing him, e.g.:
-You're being prompted which pill Neo should be taking. If he chooses the red one,
-Neo gets unplugged from the Matrix and the red pill serves as a location device
-to track his position into the farm to broadcast it and have the rebellion
-rescuing him, e.g.:
-```
+....
Which pill (red|blue)?: red
2016-04-26 17:12:07,520 [#1 - ControlBus] INFO DefaultShutdownStrategy - Starting to graceful shutdown 1 routes (timeout 300 seconds)
2016-04-26 17:12:07,521 [0 - stream://in] INFO unplug - Neo has been located in matrix
@@ -81,10 +86,11 @@ Which pill (red|blue)?: red
|_| |___|___|
2016-04-26 17:12:08,532 [#1 - ControlBus] INFO DefaultCamelContext - Route: terminal is stopped, was consuming from: Endpoint[stream://in?delay=1000&promptMessage=Which+pill+%28red%7Cblue%29%3F%3A+]
2016-04-26 17:12:08,533 [#1 - ControlBus] INFO ControlBusProducer - ControlBus task done [stop route terminal] with result -> void
-```
+....
+
+The Camel application can be stopped pressing ctrl+c in the shell:
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell:
-```
+....
2016-04-26 17:16:50,172 [Thread-5 ] INFO MainSupport$HangupInterceptor - Received hang up - stopping the main instance.
2016-04-26 17:16:50,179 [Thread-5 ] INFO CamelContextProducer - Camel CDI is stopping Camel context [cdi-camel-xml]
2016-04-26 17:16:50,180 [Thread-5 ] INFO DefaultCamelContext - Apache Camel 2.18.0 (CamelContext: cdi-camel-xml) is shutting down
@@ -101,13 +107,14 @@ The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in th
|__ | | | | _| . | . | | | | |_ _ _
|_____|_|_|___|_| |___|___|_____|_|_|_|_|_|
2016-04-26 17:16:50,275 [Thread-5 ] INFO Bootstrap - WELD-ENV-002001: Weld SE container STATIC_INSTANCE shut down
-```
+....
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-cdi/README.adoc b/examples/camel-example-cdi/README.adoc
new file mode 100644
index 0000000..b5cc0ac
--- /dev/null
+++ b/examples/camel-example-cdi/README.adoc
@@ -0,0 +1,45 @@
+== CDI Example
+
+=== Introduction
+
+This example shows how to work with Camel using CDI to configure
+components, endpoints and beans.
+
+A timer triggers a Camel route to run every 5th second which creates a
+message that is logged to the console.
+
+=== Build
+
+You will need to compile this example first:
+
+[source,sh]
+----
+$ mvn compile
+----
+
+=== Run
+
+To run the example, type:
+
+[source,sh]
+----
+$ mvn camel:run
+----
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java+` directory.
+
+To stop the example hit ctrl+c.
+
+When we launch the example using the Camel Maven plugin, a standalone
+CDI container is created and started.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cdi/README.md b/examples/camel-example-cdi/README.md
deleted file mode 100644
index da83e75..0000000
--- a/examples/camel-example-cdi/README.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# CDI Example
-
-### Introduction
-
-This example shows how to work with Camel using CDI to configure components,
-endpoints and beans.
-
-A timer triggers a Camel route to run every 5th second which creates a message
-that is logged to the console.
-
-### Build
-
-You will need to compile this example first:
-
-```sh
-$ mvn compile
-```
-
-### Run
-
-To run the example, type:
-
-```sh
-$ mvn camel:run
-```
-
-You can see the routing rules by looking at the java code in the
-`src/main/java` directory.
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>.
-
-When we launch the example using the Camel Maven plugin, a standalone CDI container
-is created and started.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-console/README.adoc b/examples/camel-example-console/README.adoc
new file mode 100644
index 0000000..69f26a9
--- /dev/null
+++ b/examples/camel-example-console/README.adoc
@@ -0,0 +1,48 @@
+== Camel Console Example
+
+=== Introduction
+
+This is a simple example that shows how to get started with Camel.
+
+This is a beginner's example that demonstrates how to get started with
+Apache Camel. In this example we integrate with the console using the
+Stream component. The example is interactive - it reads input from the
+console, and then transforms the input to upper case and prints it back
+to the console.
+
+This is implemented with a Camel route defined in the Spring XML
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+You can see the routing rules by looking at the XML in the directory:
+`+src/main/resources/META-INF/spring+`
+
+To stop the example hit ctrl+c
+
+You can also run the example from your editor such as Eclipse, IDEA etc,
+by opening the org.apache.camel.example.console.CamelConsoleMain class
+and then right click, and chose run java application.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-console/README.md b/examples/camel-example-console/README.md
deleted file mode 100644
index f133591..0000000
--- a/examples/camel-example-console/README.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Camel Console Example
-
-### Introduction
-
-This is a simple example that shows how to get started with Camel.
-
-This is a beginner's example that demonstrates how to get started with Apache Camel.
-In this example we integrate with the console using the Stream component.
-The example is interactive - it reads input from the console, and then transforms the input to upper case and prints it back to the console.
-
-This is implemented with a Camel route defined in the Spring XML
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example type
-
- mvn camel:run
-
-You can see the routing rules by looking at the XML in the directory:
- `src/main/resources/META-INF/spring`
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-You can also run the example from your editor such as Eclipse, IDEA etc,
-by opening the org.apache.camel.example.console.CamelConsoleMain class
-and then right click, and chose run java application.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cxf-blueprint/README.adoc b/examples/camel-example-cxf-blueprint/README.adoc
new file mode 100644
index 0000000..30b5ad0
--- /dev/null
+++ b/examples/camel-example-cxf-blueprint/README.adoc
@@ -0,0 +1,112 @@
+== CXF OSGI Example using Blueprint
+
+=== Introduction
+
+A simple example which receives web service calls (via a CXF consumer,
+using bean binding) and writes these requests into the file system. It's
+not a very useful use case, but the goal of this example is to show you
+how you can use the CXF consumer component in an OSGI environment with
+the OSGI HTTP service. If your target container is Apache Karaf or
+Apache ServiceMix, you can use PAX Web to setup and start an OSGI HTTP
+service. All Camel bundles using a Camel CXF consumer can use this HTTP
+service without needing to start individual Jetty instances. Another
+advantage is that all provided services can now share the same port.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+To run the example on Apache Karaf 4.x or newer
+
+==== Step 1: Karaf
+
+Launch the server
+
+....
+karaf / karaf.bat
+....
+
+==== Step 2: Add features
+
+Add features required
+
+....
+feature:repo-add camel ${version}
+feature:install war
+feature:install cxf
+feature:install camel
+feature:install camel-jaxb
+feature:install camel-cxf
+....
+
+==== Step 3: Deploy
+
+Deploy the example
+
+....
+install -s mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
+....
+
+==== Step 4: Verify that your service is available using the following url in the browser.
+
+We assume you're using Karaf's default PAX Web configuration which uses
+port `8181` for http. If you would like to use another port or https,
+change the configuration in `+${KARAF_HOME}/etc/org.ops4j.pax.web.cfg+`.
+The immediate extension after the hostname and port (`cxf` in the
+below URL) is configured via the org.apache.cxf.osgi.cfg file (Please
+see http://team.ops4j.org/wiki//display/paxweb/Pax+Web for more
+information on PAX Web).
+
+....
+http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl
+....
+
+http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl
+
+==== Step 5: Start SOAPUI (2.x or later)
+
+Create a new project called camel-example-cxf-osgi Point to the
+following url:
+http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl
+Open the request 1 (under camel-example-cxf-blueprint –>
+ReportIncidentBinding –> ReportIncident) and copy/paste a SOAP message
+generated by the unit test, for example:
+
+....
+ <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
+ <soap:Header />
+ <soap:Body>
+ <ns2:inputReportIncident xmlns:ns2="http://reportincident.example.camel.apache.org">
+ <incidentId>111</incidentId>
+ <incidentDate>2011-03-05</incidentDate>
+ <givenName>Christian</givenName>
+ <familyName>Mueller</familyName>
+ <summary>Bla</summary>
+ <details>Bla bla</details>
+ <email>cmueller@apache.org</email>
+ <phone>0049 69 1234567</phone>
+ </ns2:inputReportIncident>
+ </soap:Body>
+ </soap:Envelope>
+....
+
+==== Step 6: Check the file system
+
+Check the folder `target/inbox/` in the Karaf base directory to see
+that a message has arrived.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cxf-blueprint/README.md b/examples/camel-example-cxf-blueprint/README.md
deleted file mode 100644
index 2afd5ba..0000000
--- a/examples/camel-example-cxf-blueprint/README.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# CXF OSGI Example using Blueprint
-
-### Introduction
-
-A simple example which receives web service calls (via a CXF consumer, using bean binding)
-and writes these requests into the file system. It's not a very useful use case, but the goal
-of this example is to show you how you can use the CXF consumer component in an OSGI
-environment with the OSGI HTTP service. If your target container is Apache Karaf or Apache
-ServiceMix, you can use PAX Web to setup and start an OSGI HTTP service. All Camel
-bundles using a Camel CXF consumer can use this HTTP service without needing to start
-individual Jetty instances. Another advantage is that all provided services can now share
-the same port.
-
-### Build
-You will need to compile this example first:
-
- mvn install
-
-### Run
-
-To run the example on Apache Karaf 4.x or newer
-
-#### Step 1: Karaf
-
-Launch the server
-
- karaf / karaf.bat
-
-#### Step 2: Add features
-
-Add features required
-
- feature:repo-add camel ${version}
- feature:install war
- feature:install cxf
- feature:install camel
- feature:install camel-jaxb
- feature:install camel-cxf
-
-#### Step 3: Deploy
-Deploy the example
-
- install -s mvn:org.apache.camel.example/camel-example-cxf-blueprint/${version}
-
-#### Step 4: Verify that your service is available using the following url in the browser.
-
-We assume you're using Karaf's default PAX Web configuration which uses port `8181` for http. If you would like to use another port or https, change the configuration in `${KARAF_HOME}/etc/org.ops4j.pax.web.cfg`. The immediate extension after the hostname and port ("cxf" in the below URL) is configured via the org.apache.cxf.osgi.cfg file (Please see [http://team.ops4j.org/wiki//display/paxweb/Pax+Web](http://team.ops4j.org/wiki//display/paxweb/Pax+Web) for more information on PAX Web).
-
- http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl
-
-[http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl](http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl)
-
-#### Step 5: Start SOAPUI (2.x or later)
-
-Create a new project called camel-example-cxf-osgi
-Point to the following url: [http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl](http://localhost:8181/cxf/camel-example-cxf-blueprint/webservices/incident?wsdl)
-Open the request 1 (under camel-example-cxf-blueprint --> ReportIncidentBinding --> ReportIncident) and copy/paste a SOAP
- message generated by the unit test, for example:
-
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Header />
- <soap:Body>
- <ns2:inputReportIncident xmlns:ns2="http://reportincident.example.camel.apache.org">
- <incidentId>111</incidentId>
- <incidentDate>2011-03-05</incidentDate>
- <givenName>Christian</givenName>
- <familyName>Mueller</familyName>
- <summary>Bla</summary>
- <details>Bla bla</details>
- <email>cmueller@apache.org</email>
- <phone>0049 69 1234567</phone>
- </ns2:inputReportIncident>
- </soap:Body>
- </soap:Envelope>
-
-#### Step 6: Check the file system
- Check the folder "target/inbox/" in the Karaf base directory to see that a message has arrived.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cxf-proxy/README.adoc b/examples/camel-example-cxf-proxy/README.adoc
new file mode 100644
index 0000000..e14f57d
--- /dev/null
+++ b/examples/camel-example-cxf-proxy/README.adoc
@@ -0,0 +1,88 @@
+== CXF WebService Proxy example
+
+=== Introduction
+
+An example which proxies a real web service by a Camel application using
+the camel-cxf component
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type:
+
+....
+mvn camel:run -Dmaven.test.skip=true
+....
+
+The proxied webservice is located at
+
+....
+http://localhost:${proxy.port}/camel-example-cxf-proxy/webservices/incident
+....
+
+http://localhost:9080/camel-example-cxf-proxy/webservices/incident
+
+The real webservice is located at
+
+....
+http://localhost:${real.port}/real-webservice
+....
+
+http://localhost:9081/real-webservice
+
+The webservice WSDL is exposed at:
+
+....
+http://localhost:${proxy.port}/camel-example-cxf-proxy/webservices/incident?wsdl
+....
+
+http://localhost:9080/camel-example-cxf-proxy/webservices/incident?wsdl
+
+Because we use dynamic port numbers, you have to check the console to
+get the used one. To stop the example hit ctrl+c
+
+To make a SOAP call open soapUI or another SOAP query tool and create a
+new project w/WSDL of
+http://localhost:$%7Bproxy.port%7D/camel-example-cxf-proxy/webservices/incident?wsdl.
+Then make SOAP requests of this format:
+
+....
+<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
+ xmlns:rep="http://reportincident.example.camel.apache.org">
+ <soapenv:Header/>
+ <soapenv:Body>
+ <rep:inputReportIncident>
+ <incidentId></incidentId>
+ <incidentDate>2011-11-18</incidentDate>
+ <givenName>Bob</givenName>
+ <familyName>Smith</familyName>
+ <summary>Bla bla</summary>
+ <details>More bla</details>
+ <email>your@email.org</email>
+ <phone>12345678</phone>
+ </rep:inputReportIncident>
+ </soapenv:Body>
+</soapenv:Envelope>
+....
+
+=== Configuration
+
+You can change `+${proxy.port}+` and `+${real.port}+` via configuration
+file `+src/main/resources/incident.properties+`
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cxf-proxy/README.md b/examples/camel-example-cxf-proxy/README.md
deleted file mode 100644
index a699782..0000000
--- a/examples/camel-example-cxf-proxy/README.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# CXF WebService Proxy example
-
-### Introduction
-
-An example which proxies a real web service by a Camel application using the camel-cxf component
-
-### Build
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example type:
-
- mvn camel:run -Dmaven.test.skip=true
-
-The proxied webservice is located at
-
- http://localhost:${proxy.port}/camel-example-cxf-proxy/webservices/incident
-
-<http://localhost:9080/camel-example-cxf-proxy/webservices/incident>
-
-The real webservice is located at
-
- http://localhost:${real.port}/real-webservice
-
-<http://localhost:9081/real-webservice>
-
-The webservice WSDL is exposed at:
-
- http://localhost:${proxy.port}/camel-example-cxf-proxy/webservices/incident?wsdl
-
-<http://localhost:9080/camel-example-cxf-proxy/webservices/incident?wsdl>
-
-Because we use dynamic port numbers, you have to check the console to get the used one.
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-To make a SOAP call open soapUI or another SOAP query tool and create a new
-project w/WSDL of <http://localhost:${proxy.port}/camel-example-cxf-proxy/webservices/incident?wsdl>.
-Then make SOAP requests of this format:
-
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
- xmlns:rep="http://reportincident.example.camel.apache.org">
- <soapenv:Header/>
- <soapenv:Body>
- <rep:inputReportIncident>
- <incidentId></incidentId>
- <incidentDate>2011-11-18</incidentDate>
- <givenName>Bob</givenName>
- <familyName>Smith</familyName>
- <summary>Bla bla</summary>
- <details>More bla</details>
- <email>your@email.org</email>
- <phone>12345678</phone>
- </rep:inputReportIncident>
- </soapenv:Body>
- </soapenv:Envelope>
-
-### Configuration
-
-You can change `${proxy.port}` and `${real.port}` via configuration file `src/main/resources/incident.properties`
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cxf-tomcat/README.adoc b/examples/camel-example-cxf-tomcat/README.adoc
new file mode 100644
index 0000000..fd5f7a4
--- /dev/null
+++ b/examples/camel-example-cxf-tomcat/README.adoc
@@ -0,0 +1,75 @@
+== Camel CXF (code first) and Apache Tomcat example
+
+=== Introduction
+
+An example which uses code-first to expose a web service in Camel
+running on Apache Tomcat.
+
+=== Build
+
+It can be run using Maven.
+
+You will need to first need to build the example:
+
+....
+mvn clean install
+....
+
+=== Run
+
+To run the example deploy it in Apache Tomcat by copying the .war
+located in the target directory to the deploy folder of Apache Tomcat.
+Alternatively, if your Tomcat installation is set up to use the Tomcat
+Maven plugin (http://mojo.codehaus.org/tomcat-maven-plugin/usage.html),
+you can simply run `mvn tomcat:deploy` (also `tomcat:undeploy`,
+`tomcat:redeploy`, etc.) to install the WAR file.
+
+The webservice is located at
+
+....
+http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl
+....
+
+http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl
+
+You can run a sample client using the `mvn exec:java` command, or,
+within soapUI, making sample SOAP requests such as the following:
+
+....
+<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
+ <soap:Body>
+ <ns1:reportIncident xmlns:ns1="http://incident.cxf.example.camel.apache.org/">
+ <arg0>
+ <details>blah blah</details>
+ <email>davsclaus@apache.org</email>
+ <familyName>Smith</familyName>
+ <givenName>Bob</givenName>
+ <incidentDate>2011-11-25</incidentDate>
+ <incidentId>123</incidentId>
+ <phone>123-456-7890</phone>
+ <summary>blah blah summary</summary>
+ </arg0>
+ </ns1:reportIncident>
+ </soap:Body>
+</soap:Envelope>
+
+<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
+ <soap:Body>
+ <ns1:statusIncident xmlns:ns1="http://incident.cxf.example.camel.apache.org/">
+ <arg0>
+ <incidentId>456</incidentId>
+ </arg0>
+ </ns1:statusIncident>
+ </soap:Body>
+</soap:Envelope>
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cxf-tomcat/README.md b/examples/camel-example-cxf-tomcat/README.md
deleted file mode 100644
index 7c59bc7..0000000
--- a/examples/camel-example-cxf-tomcat/README.md
+++ /dev/null
@@ -1,67 +0,0 @@
-# Camel CXF (code first) and Apache Tomcat example
-
-### Introduction
-An example which uses code-first to expose a web service in Camel running on Apache Tomcat.
-
-### Build
-It can be run using Maven.
-
-You will need to first need to build the example:
-
- mvn clean install
-
-### Run
-
-To run the example deploy it in Apache Tomcat by copying the .war located
-in the target directory to the deploy folder of Apache Tomcat. Alternatively,
-if your Tomcat installation is set up to use the Tomcat Maven plugin
-([http://mojo.codehaus.org/tomcat-maven-plugin/usage.html](http://mojo.codehaus.org/tomcat-maven-plugin/usage.html)), you can simply
-run `mvn tomcat:deploy` (also `tomcat:undeploy`, `tomcat:redeploy`, etc.)
-to install the WAR file.
-
-The webservice is located at
-
- http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl
-
-[http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl](http://localhost:8080/camel-example-cxf-tomcat/webservices/incident?wsdl)
-
-You can run a sample client using the "mvn exec:java" command, or, within
-soapUI, making sample SOAP requests such as the following:
-
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Body>
- <ns1:reportIncident xmlns:ns1="http://incident.cxf.example.camel.apache.org/">
- <arg0>
- <details>blah blah</details>
- <email>davsclaus@apache.org</email>
- <familyName>Smith</familyName>
- <givenName>Bob</givenName>
- <incidentDate>2011-11-25</incidentDate>
- <incidentId>123</incidentId>
- <phone>123-456-7890</phone>
- <summary>blah blah summary</summary>
- </arg0>
- </ns1:reportIncident>
- </soap:Body>
- </soap:Envelope>
-
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Body>
- <ns1:statusIncident xmlns:ns1="http://incident.cxf.example.camel.apache.org/">
- <arg0>
- <incidentId>456</incidentId>
- </arg0>
- </ns1:statusIncident>
- </soap:Body>
- </soap:Envelope>
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cxf-ws-security-signature/README.adoc b/examples/camel-example-cxf-ws-security-signature/README.adoc
new file mode 100644
index 0000000..6531a29
--- /dev/null
+++ b/examples/camel-example-cxf-ws-security-signature/README.adoc
@@ -0,0 +1,110 @@
+== CXF WS-SECURITY OSGi HTTP WEB SERVICE
+
+=== Introduction
+
+Create a web service with CXF using WS-SECURITY Signature action and expose it through the OSGi HTTP Service,
+the main purpose is to demonstrate how to use signaturePropRefId WSS4J configuration in OSGi container.
+
+=== Explanation
+
+The web service is a simple JAX-WS web service with ws-security Signature and UsernameToken action called HelloWorldSecurity.
+The interface and the implementation are located in the `src/main/java/org/apache/camel/example/cxf/ws` directory of this example.
+
+The camel-context.xml file, located in the `src/main/resources/META-INF/spring` directory:
+
+[arabic]
+Configures the web service endpoint as follows:
+....
+ <jaxws:endpoint id="helloWorld"
+ implementor="org.apache.camel.example.cxf.ws.HelloWorldImpl"
+ address="/HelloWorldSecurity">
+ <jaxws:inInterceptors>
+ <bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
+ <constructor-arg>
+ <map>
+ <entry key="action" value="UsernameToken Signature"/>
+ <entry key="passwordType" value="PasswordText"/>
+ <entry key="passwordCallbackRef">
+ <ref bean="myPasswordCallback"/>
+ </entry>
+ <entry key="signaturePropRefId" value="wsCryptoProperties"/>
+ <entry key="wsCryptoProperties" value-ref="wsCryptoProperties"/>
+ </map>
+ </constructor-arg>
+ </bean>
+ <bean class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor" />
+ </jaxws:inInterceptors>
+ </jaxws:endpoint>
+
+ <util:properties id="wsCryptoProperties">
+ <prop key="org.apache.ws.security.crypto.provider">org.apache.ws.security.components.crypto.Merlin</prop>
+ <prop key="org.apache.ws.security.crypto.merlin.keystore.type">jks</prop>
+ <prop key="org.apache.ws.security.crypto.merlin.keystore.password">storepassword</prop>
+ <prop key="org.apache.ws.security.crypto.merlin.keystore.file">server-truststore.jks</prop>
+ </util:properties>
+....
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+To run the example on Apache Karaf 4.x or newer
+
+==== Step 1: Karaf
+
+Launch the server
+
+....
+karaf / karaf.bat
+....
+
+==== Step 2: Add features
+
+Add features required
+
+....
+feature:install cxf
+feature:install camel
+feature:install camel-cxf
+....
+
+==== Step 3: Deploy
+
+Deploy the example
+
+....
+install -s mvn:org.apache.camel.example/camel-example-cxf-ws-security-signature/${version}
+....
+
+To view the service WSDL, open your browser and go to the following URL:
+
+http://localhost:8181/cxf/HelloWorldSecurity?wsdl
+
+=== Running a Client
+
+To run the java code client:
+
+[arabic]
+. Change to the /examples/camel-example-cxf-ws-security-signature
+directory.
+. Run the following command:
++
+`+mvn compile exec:java+`
++
+If the client request is successful, it will print out: Hello CXF
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cxf-ws-security-signature/README.md b/examples/camel-example-cxf-ws-security-signature/README.md
deleted file mode 100644
index bb187b8..0000000
--- a/examples/camel-example-cxf-ws-security-signature/README.md
+++ /dev/null
@@ -1,117 +0,0 @@
-CXF WS-SECURITY OSGi HTTP WEB SERVICE
-=========================
-
-### Introduction
-
-Create a web service with CXF using WS-SECURITY Signature action and expose it through the OSGi HTTP
-Service, the main purpose is to demonstrate how to use signaturePropRefId WSS4J configuration in
-OSGi container.
-
-
-### Explanation
-
-The web service is a simple JAX-WS web service with ws-security Signature and UsernameToken action called HelloWorldSecurity. The
-interface and the implementation are located in the src/main/java/org/
-apache/camel/example/cxf/ws directory of this example.
-
-The camel-context.xml file, located in the src/main/resources/META-INF/spring
-directory:
-
-
-1. Configures the web service endpoint as follows:
-
- <jaxws:endpoint id="helloWorld"
- implementor="org.apache.camel.example.cxf.ws.HelloWorldImpl"
- address="/HelloWorldSecurity">
- <jaxws:inInterceptors>
- <bean class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
- <constructor-arg>
- <map>
- <entry key="action" value="UsernameToken Signature"/>
- <entry key="passwordType" value="PasswordText"/>
- <entry key="passwordCallbackRef">
- <ref bean="myPasswordCallback"/>
- </entry>
- <entry key="signaturePropRefId" value="wsCryptoProperties"/>
- <entry key="wsCryptoProperties" value-ref="wsCryptoProperties"/>
- </map>
- </constructor-arg>
- </bean>
- <bean class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor" />
- </jaxws:inInterceptors>
- </jaxws:endpoint>
-
- <util:properties id="wsCryptoProperties">
-
- <prop
- key="org.apache.ws.security.crypto.provider">org.apache.ws.security.components.crypto.Merlin</prop>
-
- <prop
- key="org.apache.ws.security.crypto.merlin.keystore.type">jks</prop>
-
- <prop
- key="org.apache.ws.security.crypto.merlin.keystore.password">storepassword</prop>
-
- <prop
- key="org.apache.ws.security.crypto.merlin.keystore.file">server-truststore.jks</prop>
- </util:properties>
-
-### Build
-You will need to compile this example first:
-
- mvn install
-
-### Run
-
-To run the example on Apache Karaf 4.x or newer
-
-#### Step 1: Karaf
-
-Launch the server
-
- karaf / karaf.bat
-
-#### Step 2: Add features
-
-Add features required
-
- feature:install cxf
- feature:install camel
- feature:install camel-cxf
-
-#### Step 3: Deploy
-
-Deploy the example
-
- install -s mvn:org.apache.camel.example/camel-example-cxf-ws-security-signature/${version}
-
-To view the service WSDL, open your browser and go to the following
-URL:
-
- http://localhost:8181/cxf/HelloWorldSecurity?wsdl
-
-
-### Running a Client
-
-To run the java code client:
-
-1. Change to the <camel_home>/examples/camel-example-cxf-ws-security-signature
- directory.
-
-2. Run the following command:
-
- `mvn compile exec:java`
-
- If the client request is successful, it will print out:
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:sayHelloResponse xmlns:ns2="http://cxf.apache.org/wsse/handler/helloworld"><return>Hello CXF</return></ns2:sayHelloResponse></soap:Body></soap:Envelope>
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-cxf/README.adoc b/examples/camel-example-cxf/README.adoc
new file mode 100644
index 0000000..4e046a5
--- /dev/null
+++ b/examples/camel-example-cxf/README.adoc
@@ -0,0 +1,55 @@
+== Camel CXF Example
+
+=== Introduction
+
+This example shows how to work with CXF and Camel.
+
+The Camel CXF example is a demo of the camel-cxf component to show how
+to route messages between CXF endpoints, with one endpoint consuming a
+SOAP over HTTP request while the other providing a SOAP over JMS request
+for the actual CXF Service endpoint. The Camel router just routes the
+SOAP over HTTP CXF client request to the SOAP over JMS CXF service.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example of routing between different transport type
+
+....
+mvn exec:java -PHttpToJMS
+....
+
+To run the example of Camel transport type
+
+....
+mvn exec:java -PCamelTransport
+....
+
+To run the example of using WebServiceProvider API
+
+....
+mvn exec:java -PWebServiceProvider
+....
+
+To run the example of showing how to create CXF JAXRS endpoint
+
+....
+mvn exec:java -PJAXRS
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-cxf/README.md b/examples/camel-example-cxf/README.md
deleted file mode 100644
index f0d1f7b..0000000
--- a/examples/camel-example-cxf/README.md
+++ /dev/null
@@ -1,45 +0,0 @@
-# Camel CXF Example
-
-### Introduction
-
-This example shows how to work with CXF and Camel.
-
-The Camel CXF example is a demo of the camel-cxf component to show how to route messages between CXF endpoints,
-with one endpoint consuming a SOAP over HTTP request while the other providing a SOAP over JMS request for the actual CXF Service endpoint.
-The Camel router just routes the SOAP over HTTP CXF client request to the SOAP over JMS CXF service.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example of routing between different transport type
-
- mvn exec:java -PHttpToJMS
-
-To run the example of Camel transport type
-
- mvn exec:java -PCamelTransport
-
-To run the example of using WebServiceProvider API
-
- mvn exec:java -PWebServiceProvider
-
-To run the example of showing how to create CXF JAXRS endpoint
-
- mvn exec:java -PJAXRS
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-debezium/README.adoc b/examples/camel-example-debezium/README.adoc
index 6ec4bce..8a82d98 100644
--- a/examples/camel-example-debezium/README.adoc
+++ b/examples/camel-example-debezium/README.adoc
@@ -10,6 +10,7 @@ This project consists of the following examples:
2. Example how data can be sinked into Cassandra that produced by Debezium.
== Prerequisites
+
=== MySQL
In order to stream changes from MySQL, you will need to have https://debezium.io/documentation/reference/0.9/connectors/mysql.html#enabling-the-binlog[_row-level_] binary binlog enabled. However,
for the sake of this example, we will use the following docker image which is setup with row enabled binary logs and some sample data:
@@ -25,7 +26,6 @@ kinesis.accessKey ={{generated-access-key}}
kinesis.secretKey = {{generated-secret-key}}
```
-
=== Cassandra
In this example, we will use Cassandra to sink the events into, you will need to either to download and run Cassandra on your machine or you can simply use the following docker image that exposes a Cassandra instance on port 9042:
```
@@ -46,7 +46,6 @@ USE dbzSink;
```
*Note:* We will stream a table called `product` from MySQL docker image which is already set. Most of the configurations that will get you started with this example are already set in `application.properties`.
-
=== Build
Due to licensing issues, you will need to add the dependency for `mysql-conenctor-java`, just add the following to your POM file:
@@ -80,7 +79,6 @@ the changes reflecting on Cassandra as well, you can verify that by running the
select * from dbzSink.products;
```
-
=== Configuration
You can configure the details in the file:
@@ -89,13 +87,12 @@ You can configure the details in the file:
You can enable verbose logging by adjusting the `src/main/resources/log4j2.properties`
file as documented in the file.
-=== Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+=== Help and contributions
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-ehcache-blueprint/README.adoc b/examples/camel-example-ehcache-blueprint/README.adoc
new file mode 100644
index 0000000..89ece12
--- /dev/null
+++ b/examples/camel-example-ehcache-blueprint/README.adoc
@@ -0,0 +1,84 @@
+== Camel Ehcache Blueprint example
+
+=== Introduction
+
+This example shows how to use `+camel-ehcache+` to cache messages in a
+Camel route.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run with Karaf
+
+To install Apache Camel in Karaf you type in the shell (we use version
+$\{project.version}):
+
+....
+feature:repo-add camel ${project.version}
+feature:install camel
+....
+
+First you need to install the following features in Karaf with:
+
+....
+feature:install camel-ehcache
+feature:install camel-servlet
+feature:install camel-jackson
+....
+
+Then you can install the example:
+
+....
+install -s mvn:org.apache.camel.example/camel-example-ehcache-blueprint/${project.version}
+....
+
+And you can see the application running by tailing the logs:
+
+....
+log:tail
+....
+
+And you can use ctrl+c to stop tailing the log.
+
+There is a data REST service that supports the following operation(s):
+
+* GET /data/\{id} - to get data with the given id from an external
+service
+
+From a web browser you can access the service using the following
+link(s):
+
+....
+http://localhost:8181/camel-example-ehcache-blueprint/data/123 - to get the data with id 123
+....
+
+From the command shell you can use `+curl+` to access the service as
+shown below:
+
+....
+curl -X GET -H "Accept: application/json" http://localhost:8181/camel-example-ehcache-blueprint/data/123
+....
+
+The first time you try to get the data it will take 3 seconds as the
+example (pretends to) access an external data service. But then the data
+will be cached, so it will be quick afterward.
+
+=== Configuration
+
+This example is implemented in XML DSL in the
+`+src/main/resources/OSGI-INF/blueprint/camel-context.xml+` file.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-ehcache-blueprint/README.md b/examples/camel-example-ehcache-blueprint/README.md
deleted file mode 100644
index 4562725..0000000
--- a/examples/camel-example-ehcache-blueprint/README.md
+++ /dev/null
@@ -1,60 +0,0 @@
-# Camel Ehcache Blueprint example
-
-### Introduction
-This example shows how to use `camel-ehcache` to cache messages in a Camel route.
-
-### Build
-You will need to compile this example first:
-
- mvn install
-
-
-### Run with Karaf
-To install Apache Camel in Karaf you type in the shell (we use version ${project.version}):
-
- feature:repo-add camel ${project.version}
- feature:install camel
-
-First you need to install the following features in Karaf with:
-
- feature:install camel-ehcache
- feature:install camel-servlet
- feature:install camel-jackson
-
-
-Then you can install the example:
-
- install -s mvn:org.apache.camel.example/camel-example-ehcache-blueprint/${project.version}
-
-And you can see the application running by tailing the logs:
-
- log:tail
-
-And you can use <kbd>ctrl</kbd>+<kbd>c</kbd> to stop tailing the log.
-
-There is a data REST service that supports the following operation(s):
-
-- GET /data/{id} - to get data with the given id from an external service
-
-From a web browser you can access the service using the following link(s):
-
- http://localhost:8181/camel-example-ehcache-blueprint/data/123 - to get the data with id 123
-
-From the command shell you can use `curl` to access the service as shown below:
-
- curl -X GET -H "Accept: application/json" http://localhost:8181/camel-example-ehcache-blueprint/data/123
-
-The first time you try to get the data it will take 3 seconds as the example (pretends to) access an external data service.
-But then the data will be cached, so it will be quick afterward.
-
-
-### Configuration
-This example is implemented in XML DSL in the `src/main/resources/OSGI-INF/blueprint/camel-context.xml` file.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-fhir-auth-tx-spring-boot/readme.adoc b/examples/camel-example-fhir-auth-tx-spring-boot/readme.adoc
index d72771c..f07e85b 100644
--- a/examples/camel-example-fhir-auth-tx-spring-boot/readme.adoc
+++ b/examples/camel-example-fhir-auth-tx-spring-boot/readme.adoc
@@ -1,8 +1,7 @@
:experimental:
+== FHIR Authorization and Transaction Example - Spring Boot
-= FHIR Authorization and Transaction Example - Spring Boot
-
-== Introduction
+=== Introduction
This is an example application of the `camel-fhir` component. We'll be using `camel-spring-boot` as well for an easy setup.
@@ -20,7 +19,7 @@ However, you can edit the `application.properties` file to change the defaults a
There is an example of a test in the `MyCamelApplicationTest` class, which mocks out the FHIR server, thus can be run without the FHIR server.
-== Build
+=== Build
You can build this example using:
@@ -28,7 +27,7 @@ You can build this example using:
$ mvn package
```
-== Run
+=== Run
You can run this example using:
@@ -46,7 +45,7 @@ located in the `src/main/data` folder into it. You should see the following outp
The Camel application can be stopped pressing kbd:[Ctrl+c] in the shell.
-== To get health check
+=== To get health check
To show a summary of spring boot health check
@@ -54,7 +53,7 @@ To show a summary of spring boot health check
curl -XGET -s http://localhost:8080/actuator/health
----
-== To get info about the routes
+=== To get info about the routes
To show a summary of all the routes
@@ -68,14 +67,12 @@ To show detailed information for a specific route
curl -XGET -s http://localhost:8080/actuator/camelroutes/{id}/detail
----
+=== Help and contributions
-== Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
-
-
diff --git a/examples/camel-example-fhir-osgi/README.adoc b/examples/camel-example-fhir-osgi/README.adoc
new file mode 100644
index 0000000..d560afe
--- /dev/null
+++ b/examples/camel-example-fhir-osgi/README.adoc
@@ -0,0 +1,166 @@
+== FHIR Example - OSGi
+
+=== Introduction
+
+This is an example application of the `+camel-fhir+` component that can
+be executed inside an OSGi container. We will be using Apache Karaf.
+
+The example assumes you have a running FHIR server at your disposal. You
+may use
+https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-jpaserver-example[hapi-fhir-jpa-server-example]
+
+By default, the example uses
+`+http://localhost:8080/hapi-fhir-jpaserver-example/baseDstu3+` as the
+FHIR server URL, DSTU3 as the FHIR version and
+`+target/work/fhir/input+` as the directory to look for HL7V2 patients.
+However, you can edit the
+`+org.apache.camel.example.fhir.osgi.configuration.cfg+` file to
+override the defaults and provide your own configuration.
+
+=== Build
+
+You will need to build this example first:
+
+[source,sh]
+----
+$ mvn install
+----
+
+=== Run OSGi / Karaf
+
+This example can be executed within Karaf 4.x
+
+To run the example, from the command line:
+
+[arabic]
+. In the Karaf install root directory, start Karaf:
++
+[source,sh]
+----
+$ bin/karaf
+----
+. Install the pre-requisites:
++
+[source,sh]
+----
+karaf@root()> repo-add camel ${version}
+karaf@root()> feature:install camel-blueprint camel-hl7 camel-fhir
+----
+. Copy the configuration file
+org.apache.camel.example.fhir.osgi.configuration.cfg to the etc/
+directory of your Karaf installation:
+`+InstallDir/etc/org.apache.camel.example.fhir.osgi.configuration.cfg+`
+. Then install and start the example:
++
+[source,sh]
+----
+karaf@root()> install -s mvn:org.apache.camel.example/camel-example-fhir-osgi/${version}
+----
+
+When the Camel application runs, you should see a folder created under
+`+work/fhir/input+`. Copy the file `+hl7v2.patient+` located in the
+`+data+` folder into it.
+
+By tailing the log with:
+
+....
+```sh
+karaf@root()> log:tail
+```
+....
+
+The following messages should be displayed:
+
+....
+```
+2018-07-17 17:02:35,590 | INFO | nt Dispatcher: 1 | FhirContext | 52 - ca.uhn.hapi.fhir.hapi-fhir-base - 3.3.0 | Creating new FHIR context for FHIR version [DSTU3]
+2018-07-17 17:02:35,631 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Route: fhir-example-osgi started and consuming from: file://work/fhir/input
+2018-07-17 17:02:35,631 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Total 1 routes, of which 1 are started
+2018-07-17 17:02:35,632 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) started in 0.853 seconds
+2018-07-17 17:03:06,157 | INFO | /work/fhir/input | fhir-example-osgi | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Converting hl7v2.patient
+2018-07-17 17:03:06,577 | INFO | /work/fhir/input | fhir-example-osgi | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Inserting Patient: {"resourceType":"Patient","id":"100005056","name":[{"family":"Freeman","given":["Vincent"]}]}
+2018-07-17 17:03:08,829 | INFO | d #2 - CamelFhir | fhir-example-osgi | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Patient created successfully: true
+```
+....
+
+Hit ctrl+c to exit the log command.
+
+Camel commands can be used to gain some insights on the Camel context,
+e.g.:
+
+* The `+camel:context-list+` displays the Camel context:
++
+....
+karaf@root()> camel:context-list
+ Context Status Total # Failed # Inflight # Uptime
+ ------- ------ ------- -------- ---------- ------
+ camel-fhir Started 1 0 0 3 minute
+....
+* The `+camel:route-list+` command displays the Camel routes:
++
+....
+karaf@root()> camel:route-list
+ Context Route Status Total # Failed # Inflight # Uptime
+ ------- ----- ------ ------- -------- ---------- ------
+ camel-fhir fhir-example-osgi Started 1 0 0 4 minutes
+....
+* And the `+camel:route-info+` command displays route information:
++
+....
+karaf@root()> camel:route-info camel-fhir fhir-example-osgi
+Camel Route fhir-example-osgi
+ Camel Context: camel-fhir
+ State: Started
+ State: Started
+
+
+Statistics
+ Exchanges Total: 1
+ Exchanges Completed: 1
+ Exchanges Failed: 0
+ Exchanges Inflight: 0
+ Min Processing Time: 2674 ms
+ Max Processing Time: 2674 ms
+ Mean Processing Time: 2674 ms
+ Total Processing Time: 2674 ms
+ Last Processing Time: 2674 ms
+ Delta Processing Time: 2674 ms
+ Start Statistics Date: 2018-07-17 17:02:35
+ Reset Statistics Date: 2018-07-17 17:02:35
+ First Exchange Date: 2018-07-17 17:03:08
+ Last Exchange Date: 2018-07-17 17:03:08
+....
+
+Finally, you can stop the example with:
+
+....
+```sh
+karaf@root()> uninstall camel-example-fhir-osgi
+```
+....
+
+And check in the log that the Camel context has been gracefully
+shutdown:
+
+....
+```
+2018-07-17 17:09:32,418 | INFO | xample-fhir-osgi | BlueprintExtender | 12 - org.apache.aries.blueprint.core - 1.8.3 | Destroying BlueprintContainer for bundle org.apache.camel.example.camel-example-fhir-osgi/2.23.0.SNAPSHOT
+2018-07-17 17:09:32,420 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Stopping CamelContext: camel-fhir
+2018-07-17 17:09:32,421 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) is shutting down
+2018-07-17 17:09:32,423 | INFO | nt Dispatcher: 1 | DefaultShutdownStrategy | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Starting to graceful shutdown 1 routes (timeout 300 seconds)
+2018-07-17 17:09:32,427 | INFO | 3 - ShutdownTask | DefaultShutdownStrategy | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Route: fhir-example-osgi shutdown complete, was consuming from: file://work/fhir/input
+2018-07-17 17:09:32,428 | INFO | nt Dispatcher: 1 | DefaultShutdownStrategy | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Graceful shutdown of 1 routes completed in 0 seconds
+2018-07-17 17:09:32,438 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) uptime 6 minutes
+2018-07-17 17:09:32,438 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) is shutdown in 0.017 seconds
+```
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-fhir-osgi/README.md b/examples/camel-example-fhir-osgi/README.md
deleted file mode 100644
index 59f3223..0000000
--- a/examples/camel-example-fhir-osgi/README.md
+++ /dev/null
@@ -1,148 +0,0 @@
-# FHIR Example - OSGi
-
-### Introduction
-
-This is an example application of the `camel-fhir` component that can be executed inside an OSGi container. We will be using Apache Karaf.
-
-The example assumes you have a running FHIR server at your disposal.
-You may use [hapi-fhir-jpa-server-example](https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-jpaserver-example)
-
-By default, the example uses `http://localhost:8080/hapi-fhir-jpaserver-example/baseDstu3` as the FHIR server URL, DSTU3 as the FHIR version and `target/work/fhir/input`
-as the directory to look for HL7V2 patients.
-However, you can edit the `org.apache.camel.example.fhir.osgi.configuration.cfg` file to override the defaults and provide your own configuration.
-
-### Build
-
-You will need to build this example first:
-
-```sh
-$ mvn install
-```
-
-### Run OSGi / Karaf
-
-This example can be executed within Karaf 4.x
-
-To run the example, from the command line:
-
-1. In the Karaf install root directory, start Karaf:
-
- ```sh
- $ bin/karaf
- ```
-
-2. Install the pre-requisites:
-
- ```sh
- karaf@root()> repo-add camel ${version}
- karaf@root()> feature:install camel-blueprint camel-hl7 camel-fhir
- ```
-
-3. Copy the configuration file org.apache.camel.example.fhir.osgi.configuration.cfg to the etc/ directory of your Karaf installation:
- ```
- InstallDir/etc/org.apache.camel.example.fhir.osgi.configuration.cfg
- ```
-4. Then install and start the example:
-
- ```sh
- karaf@root()> install -s mvn:org.apache.camel.example/camel-example-fhir-osgi/${version}
- ```
-
-When the Camel application runs, you should see a folder created under `work/fhir/input`. Copy the file `hl7v2.patient`
-located in the `data` folder into it.
-
-By tailing the log with:
-
- ```sh
- karaf@root()> log:tail
- ```
-
-The following messages should be displayed:
-
- ```
- 2018-07-17 17:02:35,590 | INFO | nt Dispatcher: 1 | FhirContext | 52 - ca.uhn.hapi.fhir.hapi-fhir-base - 3.3.0 | Creating new FHIR context for FHIR version [DSTU3]
- 2018-07-17 17:02:35,631 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Route: fhir-example-osgi started and consuming from: file://work/fhir/input
- 2018-07-17 17:02:35,631 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Total 1 routes, of which 1 are started
- 2018-07-17 17:02:35,632 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) started in 0.853 seconds
- 2018-07-17 17:03:06,157 | INFO | /work/fhir/input | fhir-example-osgi | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Converting hl7v2.patient
- 2018-07-17 17:03:06,577 | INFO | /work/fhir/input | fhir-example-osgi | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Inserting Patient: {"resourceType":"Patient","id":"100005056","name":[{"family":"Freeman","given":["Vincent"]}]}
- 2018-07-17 17:03:08,829 | INFO | d #2 - CamelFhir | fhir-example-osgi | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Patient created successfully: true
- ```
-
-Hit <kbd>ctrl</kbd>+<kbd>c</kbd> to exit the log command.
-
-Camel commands can be used to gain some insights on the Camel context, e.g.:
-
-- The `camel:context-list` displays the Camel context:
-
- ```
- karaf@root()> camel:context-list
- Context Status Total # Failed # Inflight # Uptime
- ------- ------ ------- -------- ---------- ------
- camel-fhir Started 1 0 0 3 minute
- ```
-
-- The `camel:route-list` command displays the Camel routes:
-
- ```
- karaf@root()> camel:route-list
- Context Route Status Total # Failed # Inflight # Uptime
- ------- ----- ------ ------- -------- ---------- ------
- camel-fhir fhir-example-osgi Started 1 0 0 4 minutes
- ```
-
-- And the `camel:route-info` command displays route information:
-
- ```
- karaf@root()> camel:route-info camel-fhir fhir-example-osgi
- Camel Route fhir-example-osgi
- Camel Context: camel-fhir
- State: Started
- State: Started
-
-
- Statistics
- Exchanges Total: 1
- Exchanges Completed: 1
- Exchanges Failed: 0
- Exchanges Inflight: 0
- Min Processing Time: 2674 ms
- Max Processing Time: 2674 ms
- Mean Processing Time: 2674 ms
- Total Processing Time: 2674 ms
- Last Processing Time: 2674 ms
- Delta Processing Time: 2674 ms
- Start Statistics Date: 2018-07-17 17:02:35
- Reset Statistics Date: 2018-07-17 17:02:35
- First Exchange Date: 2018-07-17 17:03:08
- Last Exchange Date: 2018-07-17 17:03:08
- ```
-
-Finally, you can stop the example with:
-
- ```sh
- karaf@root()> uninstall camel-example-fhir-osgi
- ```
-
-And check in the log that the Camel context has been gracefully
-shutdown:
-
- ```
- 2018-07-17 17:09:32,418 | INFO | xample-fhir-osgi | BlueprintExtender | 12 - org.apache.aries.blueprint.core - 1.8.3 | Destroying BlueprintContainer for bundle org.apache.camel.example.camel-example-fhir-osgi/2.23.0.SNAPSHOT
- 2018-07-17 17:09:32,420 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Stopping CamelContext: camel-fhir
- 2018-07-17 17:09:32,421 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) is shutting down
- 2018-07-17 17:09:32,423 | INFO | nt Dispatcher: 1 | DefaultShutdownStrategy | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Starting to graceful shutdown 1 routes (timeout 300 seconds)
- 2018-07-17 17:09:32,427 | INFO | 3 - ShutdownTask | DefaultShutdownStrategy | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Route: fhir-example-osgi shutdown complete, was consuming from: file://work/fhir/input
- 2018-07-17 17:09:32,428 | INFO | nt Dispatcher: 1 | DefaultShutdownStrategy | 61 - org.apache.camel.camel-core - 2.23.0.SNAPSHOT | Graceful shutdown of 1 routes completed in 0 seconds
- 2018-07-17 17:09:32,438 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) uptime 6 minutes
- 2018-07-17 17:09:32,438 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 59 - org.apache.camel.camel-blueprint - 2.23.0.SNAPSHOT | Apache Camel 3.0.0-SNAPSHOT (CamelContext: camel-fhir) is shutdown in 0.017 seconds
- ```
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-fhir-spring-boot/readme.adoc b/examples/camel-example-fhir-spring-boot/readme.adoc
index 88ab139..e3c4e27 100644
--- a/examples/camel-example-fhir-spring-boot/readme.adoc
+++ b/examples/camel-example-fhir-spring-boot/readme.adoc
@@ -11,7 +11,7 @@ The Camel route is located in the `MyCamelRouter` class.
This example will read HL7V2 patients from a directory and convert them to FHIR dtsu3 patients and upload them to a configured FHIR server.
The example assumes you have a running FHIR server at your disposal.
-You may use [hapi-fhir-jpa-server-example](https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-jpaserver-example)
+You may use https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-jpaserver-example[hapi-fhir-jpa-server-example].
By default, the example uses `\http://localhost:8080/baseDstu3` as the FHIR server URL, DSTU3 as the FHIR version and `target/work/fhir/input`
as the directory to look for HL7V2 patients.
@@ -67,14 +67,12 @@ To show detailed information for a specific route
curl -XGET -s http://localhost:8080/actuator/camelroutes/{id}/detail
----
+=== Help and contributions
-== Forum, Help, etc
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
-
-
diff --git a/examples/camel-example-fhir/README.md b/examples/camel-example-fhir/README.adoc
similarity index 51%
rename from examples/camel-example-fhir/README.md
rename to examples/camel-example-fhir/README.adoc
index bb08030..6540c66 100644
--- a/examples/camel-example-fhir/README.md
+++ b/examples/camel-example-fhir/README.adoc
@@ -1,37 +1,47 @@
-# FHIR Example - CDI
+== FHIR Example - CDI
-### Introduction
+=== Introduction
-This is an example application of the `camel-fhir` component. We'll be using `camel-cdi` as well for an easy setup.
+This is an example application of the `+camel-fhir+` component. We’ll be
+using `+camel-cdi+` as well for an easy setup.
-This example will read HL7V2 patients from a directory and convert them to FHIR dtsu3 patients and upload them to a configured FHIR server.
+This example will read HL7V2 patients from a directory and convert them
+to FHIR dtsu3 patients and upload them to a configured FHIR server.
-The example assumes you have a running FHIR server at your disposal.
-You may use [hapi-fhir-jpa-server-example](https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-jpaserver-example)
+The example assumes you have a running FHIR server at your disposal. You
+may use
+https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-jpaserver-example[hapi-fhir-jpa-server-example]
-By default, the example uses `http://localhost:8080/hapi-fhir-jpaserver-example/baseDstu3` as the FHIR server URL, DSTU3 as the FHIR version and `target/work/fhir/input`
-as the directory to look for HL7V2 patients.
-However, you can edit the `application.properties` file to override the defaults and provide your own configuration.
+By default, the example uses
+`+http://localhost:8080/hapi-fhir-jpaserver-example/baseDstu3+` as the
+FHIR server URL, DSTU3 as the FHIR version and
+`+target/work/fhir/input+` as the directory to look for HL7V2 patients.
+However, you can edit the `+application.properties+` file to override
+the defaults and provide your own configuration.
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example using:
-```sh
+[source,sh]
+----
$ mvn camel:run
-```
+----
-When the Camel application runs, you should see a folder created under `target/work/fhir/input`. Copy the file `hl7v2.patient`
-located in the `data` folder into it. You should see the following output:
-```
+When the Camel application runs, you should see a folder created under
+`+target/work/fhir/input+`. Copy the file `+hl7v2.patient+` located in
+the `+data+` folder into it. You should see the following output:
+
+....
2018-07-04 16:22:52,189 [cdi.Main.main()] INFO DefaultCamelContext - Route: fhir-example started and consuming from: file://target/work/fhir/input
2018-07-04 16:22:52,189 [cdi.Main.main()] INFO DefaultCamelContext - Total 1 routes, of which 1 are started
2018-07-04 16:22:52,190 [cdi.Main.main()] INFO DefaultCamelContext - Apache Camel 2.22.0-SNAPSHOT (CamelContext: camel-example-fhir-cdi) started in 0.636 seconds
@@ -39,15 +49,16 @@ located in the `data` folder into it. You should see the following output:
2018-07-04 16:22:57,705 [work/fhir/input] INFO fhir-example - Converting hl7v2.patient
2018-07-04 16:22:58,176 [work/fhir/input] INFO fhir-example - Inserting Patient: {"resourceType":"Patient","id":"100005056","name":[{"family":"Freeman","given":["Vincent"]}]}
2018-07-04 16:22:58,669 [ #3 - CamelFhir] INFO fhir-example - Patient creating successfully: true
-```
+....
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-The Camel riders!
\ No newline at end of file
+The Camel riders!
diff --git a/examples/camel-example-ftp/README.md b/examples/camel-example-ftp/README.md
index 9b45186..2f05e18 100644
--- a/examples/camel-example-ftp/README.md
+++ b/examples/camel-example-ftp/README.md
@@ -50,13 +50,12 @@ To run the server you type:
You can enable verbose logging by adjustung the `src/main/resources/log4j.properties` file as documented in the file.
-### Forum, Help, etc
+### Help and contributions
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback,
+then please [let us know](https://camel.apache.org/support.html).
+We also love contributors,
+so [get involved](https://camel.apache.org/contributing.html) :-)
The Camel riders!
diff --git a/examples/camel-example-google-pubsub/README.adoc b/examples/camel-example-google-pubsub/README.adoc
index 13d2217..4e74f09 100644
--- a/examples/camel-example-google-pubsub/README.adoc
+++ b/examples/camel-example-google-pubsub/README.adoc
@@ -31,7 +31,6 @@ Using a json service account credentials file::
Using an account and key::
Set `credentials.account` to the service account email and `credentials.key` to the service account key.
-
== Run
Run the consumer and producer in separate shells:
@@ -50,7 +49,6 @@ As the pubsub channel is persistent the consumer and producer do not need to run
Messages can be send from the Google Pubsub console which will be picked up by the consumer.
-
== Configuration
You can configure the details in the file:
@@ -59,14 +57,12 @@ You can configure the details in the file:
You can enable verbose logging by adjusting the `src/main/resources/log4j2.properties`
file as documented in the file.
+=== Help and contributions
-== Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-grpc-kubernetes/README.adoc b/examples/camel-example-grpc-kubernetes/README.adoc
index 39a3e4f..cf32508 100644
--- a/examples/camel-example-grpc-kubernetes/README.adoc
+++ b/examples/camel-example-grpc-kubernetes/README.adoc
@@ -121,10 +121,12 @@ $ kubectl get pods
No resources found.
```
-== Help
+=== Help and contributions
-If you hit any problems please let us know on the http://camel.apache.org/discussion-forums.html[Camel Forums].
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-hazelcast-kubernetes/LICENSE.md b/examples/camel-example-hazelcast-kubernetes/LICENSE.md
deleted file mode 100644
index 8f71f43..0000000
--- a/examples/camel-example-hazelcast-kubernetes/LICENSE.md
+++ /dev/null
@@ -1,202 +0,0 @@
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "{}"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright {yyyy} {name of copyright owner}
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
diff --git a/examples/camel-example-hazelcast-kubernetes/ReadMe.md b/examples/camel-example-hazelcast-kubernetes/README.adoc
similarity index 86%
rename from examples/camel-example-hazelcast-kubernetes/ReadMe.md
rename to examples/camel-example-hazelcast-kubernetes/README.adoc
index aa1e152..2812a38 100644
--- a/examples/camel-example-hazelcast-kubernetes/ReadMe.md
+++ b/examples/camel-example-hazelcast-kubernetes/README.adoc
@@ -1,102 +1,104 @@
-# Camel Hazelcast route on Kubernetes cluster
+== Camel Hazelcast route on Kubernetes cluster
-This quickstart run in a Java standalone container, using Spring with Apache Camel (Hazelcast component).
+This quickstart run in a Java standalone container, using Spring with
+Apache Camel (Hazelcast component).
-This quickstart is based on the Kubernetes example here: https://github.com/kubernetes/kubernetes/tree/master/examples/storage/hazelcast
+This quickstart is based on the Kubernetes example here:
+https://github.com/kubernetes/kubernetes/tree/master/examples/storage/hazelcast
This example is based on:
-- Minikube (Kubernetes version >= 1.5) or Minishift (Openshift >= 3.5)
-- Fabric8 Maven Plugin (version >= 3.2)
+* Minikube (Kubernetes version >= 1.5) or Minishift (Openshift >= 3.5)
+* Fabric8 Maven Plugin (version >= 3.2)
-First thing you'll need to do is preparing the environment.
+First thing you’ll need to do is preparing the environment.
-Once your Minikube node is up and running you'll need to run the following command.
-In your src/main/resources/fabric8/ folder you'll find two yaml file. Run the following command using them:
+Once your Minikube node is up and running you’ll need to run the
+following command. In your `src/main/resources/fabric8/`` folder you’ll
+find two yaml file. Run the following command using them:
-```
+....
$ kubectl create -f src/main/resources/fabric8/hazelcast-service.yaml
$ kubectl create -f src/main/resources/fabric8/hazelcast-deployment.yaml
-```
+....
or once your Minishift cluster is up and running:
-```
+....
$ oc create -f src/main/resources/fabric8/hazelcast-service.yaml
$ oc create -f src/main/resources/fabric8/hazelcast-deployment.yaml
-```
+....
-To check the correct startup of the Hazelcast instance run the following command:
+To check the correct startup of the Hazelcast instance run the following
+command:
-```
+....
$ kubectl get deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
hazelcast 1 1 1 1 1m
-```
+....
or on Minishift
-```
+....
$ oc get deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
hazelcast 1 1 1 1 1m
-```
+....
and check the status of the pod
-```
+....
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
hazelcast-69df7cd6c-ccbft 1/1 Running 0 54s
-```
+....
on Minishift:
-```
+....
$ oc get pods
NAME READY STATUS RESTARTS AGE
hazelcast-1638707704-n64tk 1/1 Running 0 1m
-```
+....
Now you can decide to scale-up your Hazelcast cluster
-```
+....
$ kubectl scale deployment hazelcast --replicas 4
-```
+....
on Minishift
-```
+....
$ oc scale deployment hazelcast --replicas=4
-```
+....
and again check the status of your pods
-```
+....
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
hazelcast-69df7cd6c-2ps79 1/1 Running 0 30s
hazelcast-69df7cd6c-ccbft 1/1 Running 0 1m
hazelcast-69df7cd6c-csdwr 1/1 Running 0 30s
hazelcast-69df7cd6c-ghxgq 1/1 Running 0 30s
-
-```
+....
on Minishift
-```
+....
$ oc get pods
NAME READY STATUS RESTARTS AGE
hazelcast-1638707704-g8qwh 1/1 Running 0 1m
hazelcast-1638707704-n64tk 1/1 Running 0 3m
hazelcast-1638707704-wwwff 1/1 Running 0 1m
hazelcast-1638707704-z1g6r 1/1 Running 0 1m
-
-```
+....
You can also take a look at the logs from the pods with kubectl or oc
-```
+....
kubectl logs hazelcast-69df7cd6c-ghxgq
2018-02-19 07:14:43.728 INFO 5 --- [ main] com.github.pires.hazelcast.Application : Starting Application on hazelcast-69df7cd6c-ghxgq with PID 5 (/bootstrapper.jar started by root in /)
2018-02-19 07:14:43.751 INFO 5 --- [ main] com.github.pires.hazelcast.Application : No active profile set, falling back to default profiles: default
@@ -123,8 +125,8 @@ kubectl logs hazelcast-69df7cd6c-ghxgq
2018-02-19 07:14:54.429 INFO 5 --- [ration.thread-0] c.h.internal.cluster.ClusterService : [172.17.0.5]:5701 [someGroup] [3.9.3]
Members {size:2, ver:2} [
- Member [172.17.0.4]:5701 - 59045d20-faf3-4a73-b4de-e8036f4b7caa
- Member [172.17.0.5]:5701 - e737cd89-cbf1-4358-8d5a-f5b06a464c4a this
+ Member [172.17.0.4]:5701 - 59045d20-faf3-4a73-b4de-e8036f4b7caa
+ Member [172.17.0.5]:5701 - e737cd89-cbf1-4358-8d5a-f5b06a464c4a this
]
2018-02-19 07:14:55.482 INFO 5 --- [thread-Acceptor] com.hazelcast.nio.tcp.TcpIpAcceptor : [172.17.0.5]:5701 [someGroup] [3.9.3] Accepting socket connection from /172.17.0.6:38585
@@ -134,42 +136,54 @@ Members {size:2, ver:2} [
2018-02-19 07:15:02.079 INFO 5 --- [ration.thread-0] c.h.internal.cluster.ClusterService : [172.17.0.5]:5701 [someGroup] [3.9.3]
Members {size:4, ver:3} [
- Member [172.17.0.4]:5701 - 59045d20-faf3-4a73-b4de-e8036f4b7caa
- Member [172.17.0.5]:5701 - e737cd89-cbf1-4358-8d5a-f5b06a464c4a this
- Member [172.17.0.7]:5701 - d80f7b66-26b1-4b48-92ea-c07ddac05314
- Member [172.17.0.6]:5701 - b1c0aa3a-760e-4d89-955b-c1650e1e5661
+ Member [172.17.0.4]:5701 - 59045d20-faf3-4a73-b4de-e8036f4b7caa
+ Member [172.17.0.5]:5701 - e737cd89-cbf1-4358-8d5a-f5b06a464c4a this
+ Member [172.17.0.7]:5701 - d80f7b66-26b1-4b48-92ea-c07ddac05314
+ Member [172.17.0.6]:5701 - b1c0aa3a-760e-4d89-955b-c1650e1e5661
]
+....
-```
-
-### Building and running
+=== Building and running
Navigate to the project folder and the example can be built with
- $ mvn clean -Pkubernetes-install fabric8:deploy
+....
+$ mvn clean -Pkubernetes-install fabric8:deploy
+....
-When the example runs in fabric8, you can use the Kubectl command tool to inspect the status
+When the example runs in fabric8, you can use the Kubectl command tool
+to inspect the status
To list all the running pods on Minikube:
- $ kubectl get pods
+....
+$ kubectl get pods
+....
-Then find the name on Minikube of the pod that runs this quickstart, and output the logs from the running pods with:
+Then find the name on Minikube of the pod that runs this quickstart, and
+output the logs from the running pods with:
- $ kubectl logs <name of pod>
+....
+$ kubectl logs <name of pod>
+....
To list all the running pods on Minishift:
- $ oc get pods
+....
+$ oc get pods
+....
-Then find the name on Minishift of the pod that runs this quickstart, and output the logs from the running pods with:
+Then find the name on Minishift of the pod that runs this quickstart,
+and output the logs from the running pods with:
- $ kubectl logs <name of pod>
+....
+$ kubectl logs <name of pod>
+....
and you should see something like this:
-```
+....
Feb 19, 2018 7:18:39 AM com.hazelcast.client.connection.ClientConnectionManager
INFO: hz.client_0 [someGroup] [3.9.2] Setting ClientConnection{alive=true, connectionId=1, channel=NioChannel{/172.17.0.8:41011->hazelcast/10.102.1.255:5701}, remoteEndpoint=[172.17.0.4]:5701, lastReadTime=2018-02-19 07:18:39.464, lastWriteTime=2018-02-19 07:18:39.424, closedTime=never, lastHeartbeatRequested=never, lastHeartbeatReceived=never, connected server version=3.9.3} as owner with principal ClientPrincipal{uuid='0daabf2b-0b33-4a55-8453-683d7fa0436e', ownerUuid='59045d20-faf3-4a7 [...]
Feb 19, 2018 7:18:39 AM com.hazelcast.core.LifecycleService
@@ -197,34 +211,44 @@ INFO: hz.client_0 [someGroup] [3.9.2] Authenticated with server [172.17.0.7]:570
2018-02-19 07:18:46,842 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
2018-02-19 07:18:51,840 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
2018-02-19 07:18:51,842 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+....
-```
-
-### Cleanup
+=== Cleanup
Run following to undeploy on Minikube
-```
+....
$ mvn -Pkubernetes-install fabric8:undeploy
$ kubectl delete -f src/main/resources/fabric8/hazelcast-deployment.yaml
$ kubectl delete -f src/main/resources/fabric8/hazelcast-service.yaml
-```
+....
Run following to undeploy on Minishift
-```
+....
$ mvn -Pkubernetes-install fabric8:undeploy
$ oc delete -f src/main/resources/fabric8/hazelcast-deployment.yaml
$ oc delete -f src/main/resources/fabric8/hazelcast-service.yaml
-```
+....
Make sure no pod is running
-```
+
+....
$ kubectl get pods
No resources found.
-```
+....
-```
+....
$ oc get pods
No resources found.
-```
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
+
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-hystrix/README.adoc b/examples/camel-example-hystrix/README.adoc
new file mode 100644
index 0000000..c346e61
--- /dev/null
+++ b/examples/camel-example-hystrix/README.adoc
@@ -0,0 +1,93 @@
+== Hystrix Example
+
+=== Introduction
+
+This example shows how to use Camel with Hystrix EIP as circuit breaker
+in Camel routes
+
+The example includes three sub maven modules that implement
+
+* client
+* service1
+* service2
+
+Where client -> service1 client -> service2 (fallback)
+
+=== Configuration
+
+Service1 is configured in the
+`+src/main/java/sample/camel/Service1Application.java+` source code.
+Service2 is configured in the
+`+src/main/resources/application.properties+` properties file.
+
+=== Build
+
+You will need to compile this example first:
+
+[source,sh]
+----
+$ mvn compile
+----
+
+=== Run the example
+
+Then using three different shells and run service1 and service2 before
+the client.
+
+[source,sh]
+----
+$ cd service1
+$ mvn compile spring-boot:run
+----
+
+When service1 is ready then start service2
+
+[source,sh]
+----
+$ cd service2
+$ mvn compile camel:run
+----
+
+And then start the client that calls service1 every second.
+
+[source,sh]
+----
+$ cd client
+$ mvn compile spring-boot:run
+----
+
+You can then stop service1 and see that the client should fallback to
+call service2 in the Hystrix EIP circuit breaker. And then start service
+1 again and see the Hystrix EIP go back to normal.
+
+=== Hystrix web console
+
+You should be able to visualize the state of the Hystrix Circuit Breaker
+in the Hystrix Web Console.
+
+You can find instructions at Hystrix how to build and run the web
+console: https://github.com/Netflix/Hystrix/wiki/Dashboard
+
+For example using gradle, you can then access the web console locally
+at: `+http://localhost:7979/hystrix-dashboard+`.
+
+The stream is accessinble from the client at:
+`+http://localhost:8080/hystrix.stream+` which you can add as stream to
+the web console and then you should see the circuit breakers. In the
+screen shot below, we have just stopped service1, so the Hystrix EIP
+will execute the fallback via network, which is calling service2
+instead. If you start service 1 again then the Hystrix EIP should go
+back to green again.
+
+image:images/hystrix-web-console.png[Hystrix Web
+Console,title="Hystrix Web Console"]
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-hystrix/README.md b/examples/camel-example-hystrix/README.md
deleted file mode 100644
index 99846bd..0000000
--- a/examples/camel-example-hystrix/README.md
+++ /dev/null
@@ -1,78 +0,0 @@
-# Hystrix Example
-
-### Introduction
-
-This example shows how to use Camel with Hystrix EIP as circuit breaker in Camel routes
-
-The example includes three sub maven modules that implement
-
-- client
-- service1
-- service2
-
-Where client -> service1
- client -> service2 (fallback)
-
-### Configuration
-
-Service1 is configured in the `src/main/java/sample/camel/Service1Application.java` source code.
-Service2 is configured in the `src/main/resources/application.properties` properties file.
-
-### Build
-
-You will need to compile this example first:
-
-```sh
-$ mvn compile
-```
-
-### Run the example
-
-Then using three different shells and run service1 and service2 before the client.
-
-```sh
-$ cd service1
-$ mvn compile spring-boot:run
-```
-
-When service1 is ready then start service2
-
-```sh
-$ cd service2
-$ mvn compile camel:run
-```
-
-And then start the client that calls service1 every second.
-
-```sh
-$ cd client
-$ mvn compile spring-boot:run
-```
-
-You can then stop service1 and see that the client should fallback to call service2 in the Hystrix EIP circuit breaker.
-And then start service 1 again and see the Hystrix EIP go back to normal.
-
-### Hystrix web console
-
-You should be able to visualize the state of the Hystrix Circuit Breaker in the Hystrix Web Console.
-
-You can find instructions at Hystrix how to build and run the web console: https://github.com/Netflix/Hystrix/wiki/Dashboard
-
-For example using gradle, you can then access the web console locally at: `http://localhost:7979/hystrix-dashboard`.
-
-The stream is accessinble from the client at: `http://localhost:8080/hystrix.stream` which you can add as stream
-to the web console and then you should see the circuit breakers. In the screen shot below, we have just stopped service1, so
-the Hystrix EIP will execute the fallback via network, which is calling service2 instead. If you start service 1 again
-then the Hystrix EIP should go back to green again.
-
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-java8/readme.adoc b/examples/camel-example-java8/readme.adoc
index 52f2fbc..c206700 100644
--- a/examples/camel-example-java8/readme.adoc
+++ b/examples/camel-example-java8/readme.adoc
@@ -1,13 +1,19 @@
-# Camel Example Java 8
+== Camel Example Java 8
This example shows how to use Java 8 new features, such as lambda expressions and method references, in the definition of a Camel route.
-= How to run
+=== How to run
You can run this example using
mvn camel:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-jdbc/README.adoc b/examples/camel-example-jdbc/README.adoc
new file mode 100644
index 0000000..dd587bc
--- /dev/null
+++ b/examples/camel-example-jdbc/README.adoc
@@ -0,0 +1,49 @@
+== Camel JDBC Example
+
+=== Introduction
+
+This example shows how to use camel-jdbc component with an embedded
+Apache Derby database.
+
+=== Build
+
+First compile this example:
+
+....
+mvn compile
+....
+
+=== Compile
+
+Now to run the example type
+
+....
+mvn camel:run
+....
+
+To stop the example hit ctrl+c
+
+=== Configuration
+
+This example uses Spring to setup and configure the database, as well
+the CamelContext.
+
+You can see this in the following file:
+`+src/main/resources/META-INF/spring/camel-context.xml+`
+
+The spring config setups three routes as follow:
+
+* `+sample-generator-route+` This route will generate sample data into database upon Camel starts.
+* `+query-update-route-part1/query-update-route-part2+` These two are connected together. It first query the database for NEW
+record to be process, invoke RecordProcess bean to do the work, then
+update the record as DONE so not to re-process on next polled.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-jdbc/README.md b/examples/camel-example-jdbc/README.md
deleted file mode 100644
index ece3846..0000000
--- a/examples/camel-example-jdbc/README.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Camel JDBC Example
-
-### Introduction
-
-This example shows how to use camel-jdbc component with an embedded
-Apache Derby database.
-
-### Build
-
-First compile this example:
-
- mvn compile
-
-### Compile
-
-Now to run the example type
-
- mvn camel:run
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-### Configuration
-
-This example uses Spring to setup and configure the database,
-as well the CamelContext.
-
-You can see this in the following file:
-* `src/main/resources/META-INF/spring/camel-context.xml`
-
-The spring config setups three routes as follow:
-
-* `sample-generator-route`
- - This route will generate sample data into database upon Camel starts.
-* `query-update-route-part1/query-update-route-part2`
- - These two are connected together. It first query the database for NEW record to be process, invoke RecordProcess bean to do the work, then update the record as DONE so not to re-process on next polled.
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-jira/README.adoc b/examples/camel-example-jira/README.adoc
index 18cdf84..7de5be9 100644
--- a/examples/camel-example-jira/README.adoc
+++ b/examples/camel-example-jira/README.adoc
@@ -1,17 +1,27 @@
-# Jira API Example
+== Jira API Example
This example shows how to use Jira Camel Endpoint to retrieve new comments, add issue and add an attachment.
-= How to run
+=== How to run
You can run this example using
mvn compile exec:java
-== OAuth configuration
+=== OAuth configuration
This example uses OAuth authentication mechanism, then you should set the verificationCode, privateKey, accessToken in "application.properties" file.
-== More information
+=== More information
You can find more information about Apache Camel at the website: http://camel.apache.org/
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-jms-file/README.adoc b/examples/camel-example-jms-file/README.adoc
new file mode 100644
index 0000000..80079b8
--- /dev/null
+++ b/examples/camel-example-jms-file/README.adoc
@@ -0,0 +1,37 @@
+== JMS & File Example
+
+=== Introduction
+
+This example shows how to work with files and JMS.
+
+The example consumes messages from a queue and writes them to the file
+system.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+The example should run if you type
+
+....
+mvn exec:java -PExample
+....
+
+After the example is complete, then there should be 10 files written in
+the test directory.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-jms-file/README.md b/examples/camel-example-jms-file/README.md
deleted file mode 100644
index afa58b1..0000000
--- a/examples/camel-example-jms-file/README.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# JMS & File Example
-
-### Introduction
-This example shows how to work with files and JMS.
-
-The example consumes messages from a queue and writes them to the file
-system.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-The example should run if you type
-
- mvn exec:java -PExample
-
-After the example is complete, then there should be 10 files written
-in the test directory.
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-jmx/README.adoc b/examples/camel-example-jmx/README.adoc
new file mode 100644
index 0000000..ac4c35c
--- /dev/null
+++ b/examples/camel-example-jmx/README.adoc
@@ -0,0 +1,41 @@
+== JMX Example
+
+=== Introduction
+
+This example shows how to work with the Camel-JMX component.
+
+The example creates a simple MBean, registers a route to listen for
+notification events on that bean and creates another route that calls
+the MBean.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Compile
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java+` directory and the Spring XML configuration lives in
+`+src/main/resources/META-INF/spring+`
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-jmx/README.md b/examples/camel-example-jmx/README.md
deleted file mode 100644
index fdd0a96..0000000
--- a/examples/camel-example-jmx/README.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# JMX Example
-
-### Introduction
-
-This example shows how to work with the Camel-JMX component.
-
-The example creates a simple MBean, registers a route to listen for
-notification events on that bean and creates another route that calls
-the MBean.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Compile
-
-To run the example type
-
- mvn camel:run
-
-You can see the routing rules by looking at the java code in the
-`src/main/java` directory and the Spring XML configuration lives in
-`src/main/resources/META-INF/spring`
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-jooq/README.adoc b/examples/camel-example-jooq/README.adoc
index 69ad705..672df59 100644
--- a/examples/camel-example-jooq/README.adoc
+++ b/examples/camel-example-jooq/README.adoc
@@ -1,7 +1,7 @@
:experimental:
-= JOOQ Example
+== JOOQ Example
-== Introduction
+=== Introduction
This example shows how to use JOOQ library with Camel to build type safe SQL queries through its API.
@@ -9,21 +9,21 @@ Example project contains SQL script to create database.
Database is generated every time when Maven `generate-sources` phase is triggered.
JOOQ classes are generated inside `target/generated-sources/jooq` directory by `jooq-codegen-maven` plugin.
-== Build
+=== Build
You will need to compile this example first:
mvn clean install
This command will generate database and JOOQ classes.
-== Run with maven
+=== Run with maven
To run the example using Maven type
mvn camel:run
To stop the example hit kbd:[Ctrl+c]
-== Example routes
+=== Example routes
[source,xml]
------------------------------------------------------------
@@ -59,14 +59,12 @@ In this example route `produce-route` inserts and selects new entity every 1s.
And the consumer route `consume-route` selects and deletes all entities from database every 5s.
-== Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
-
-
-The Camel riders!
\ No newline at end of file
+The Camel riders!
diff --git a/examples/camel-example-kafka-avro/README.adoc b/examples/camel-example-kafka-avro/README.adoc
index fb23f52..189d23d 100644
--- a/examples/camel-example-kafka-avro/README.adoc
+++ b/examples/camel-example-kafka-avro/README.adoc
@@ -1,4 +1,4 @@
-= Camel Kafka example
+== Camel Kafka example
=== Introduction
@@ -26,22 +26,18 @@ curl -X DELETE http://localhost:8081/subjects/topic-value/versions/version-no
This example requires that Kafka Server is up and running.
$ ${KAFKA}/bin/zookeeper-server-start.sh ${KAFKA}/config/zookeeper.properties
-
$ ${KAFKA}/bin/kafka-server-start.sh ${KAFKA}/config/server.properties
You will need to create following topics before you run the examples.
On windows run
-
$ ${KAFKA}/bin/kafka-topics.bat --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 1 --topic employees-avro
On linux run
-
$ ${KAFKA}/bin/kafka-topics.sh --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 1 --topic employees-avro
-
=== Build
You will need to compile this example first:
@@ -54,7 +50,6 @@ Run the consumer first in separate shell
$ mvn spring-boot:run
-
camel-context.xml file has both kafka-producer and kafka-consumer routes defined to produce/consume messages to topic my-topic.
Press `Ctrl-C` to exit.
@@ -67,13 +62,13 @@ You can configure the details in the file:
You can enable verbose logging by adjusting the `src/main/resources/log4j2.properties`
file as documented in the file.
-=== Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+=== Help and contributions
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
+
diff --git a/examples/camel-example-kafka-offsetrepository/README.adoc b/examples/camel-example-kafka-offsetrepository/README.adoc
index 96da894..098bc6e 100644
--- a/examples/camel-example-kafka-offsetrepository/README.adoc
+++ b/examples/camel-example-kafka-offsetrepository/README.adoc
@@ -1,4 +1,4 @@
-= Camel Kafka example
+== Camel Kafka example
=== Introduction
@@ -9,8 +9,6 @@ This project consists of the following examples:
1. Producer triggers with a timer and produces messages to the configured topic partition
2. Consumer consumes from configured topic by reading the offset value from locally stored file.
-
-
=== Preparing Kafka
This example requires that Kafka Server is up and running.
@@ -23,15 +21,12 @@ You will need to create following topics before you run the examples.
On windows run
-
$ ${KAFKA}/bin/kafka-topics.bat --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 1 --topic my-topic
On linux run
-
-
+
$ ${KAFKA}/bin/kafka-topics.sh --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 1 --topic my-topic
-
=== Build
You will need to compile this example first:
@@ -44,7 +39,6 @@ Run the consumer first in separate shell
$ mvn spring-boot:run
-
camel-context.xml file has both kafka-producer and kafka-consumer routes defined to produce/consume messages to topic my-topic.
Press `Ctrl-C` to exit.
@@ -57,13 +51,12 @@ You can configure the details in the file:
You can enable verbose logging by adjusting the `src/main/resources/log4j2.properties`
file as documented in the file.
-=== Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+=== Help and contributions
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-kafka/README.adoc b/examples/camel-example-kafka/README.adoc
index f439cde..0433843 100644
--- a/examples/camel-example-kafka/README.adoc
+++ b/examples/camel-example-kafka/README.adoc
@@ -1,4 +1,4 @@
-= Camel Kafka example
+== Camel Kafka example
=== Introduction
@@ -10,13 +10,11 @@ This project consists of the following examples:
2. Example of partitioner for a given producer.
3. Topic is sent in the header as well as in the URL.
-
=== Preparing Kafka
This example requires that Kafka Server is up and running.
$ ${KAFKA}/bin/zookeeper-server-start.sh ${KAFKA}/config/zookeeper.properties
-
$ ${KAFKA}/bin/kafka-server-start.sh ${KAFKA}/config/server.properties
You will need to create following topics before you run the examples.
@@ -24,16 +22,13 @@ You will need to create following topics before you run the examples.
On windows run
$ ${KAFKA}/bin/kafka-topics.bat --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 2 --topic TestLog
-
$ ${KAFKA}/bin/kafka-topics.bat --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 1 --topic AccessLog
On linux run
$ ${KAFKA}/bin/kafka-topics.sh --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 2 --topic TestLog
-
$ ${KAFKA}/bin/kafka-topics.sh --create --zookeeper <zookeeper host ip>:<port> --replication-factor 1 --partitions 1 --topic AccessLog
-
=== Build
You will need to compile this example first:
@@ -62,13 +57,12 @@ You can configure the details in the file:
You can enable verbose logging by adjusting the `src/main/resources/log4j2.properties`
file as documented in the file.
-=== Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+=== Help and contributions
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback,
+then please https://camel.apache.org/support.html[let us know].
+We also love contributors,
+so https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-kotlin/README.adoc b/examples/camel-example-kotlin/README.adoc
new file mode 100644
index 0000000..86157db
--- /dev/null
+++ b/examples/camel-example-kotlin/README.adoc
@@ -0,0 +1,34 @@
+== Camel Router with Kotlin Project
+
+A simple example that uses Kotlin programming language to define a
+little Camel route.
+
+The Camel route listen on HTTP port 8080 and return back a constant
+response.
+
+=== How to run
+
+To build this project use
+
+....
+mvn install
+....
+
+To run this project
+
+....
+mvn exec:java
+....
+
+You can then open the following url from a web browser:
+http://localhost:8080
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-kotlin/ReadMe.md b/examples/camel-example-kotlin/ReadMe.md
deleted file mode 100644
index f36980e..0000000
--- a/examples/camel-example-kotlin/ReadMe.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Camel Router with Kotlin Project
-
-A simple example that uses Kotlin programming language to define a little Camel route.
-
-The Camel route listen on HTTP port 8080 and return back a constant response.
-
-### How to run
-
-To build this project use
-
- mvn install
-
-To run this project
-
- mvn exec:java
-
-You can then open the following url from a web browser: <http://localhost:8080>
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
\ No newline at end of file
diff --git a/examples/camel-example-loadbalancing/README.adoc b/examples/camel-example-loadbalancing/README.adoc
new file mode 100644
index 0000000..06b606d
--- /dev/null
+++ b/examples/camel-example-loadbalancing/README.adoc
@@ -0,0 +1,65 @@
+== Load balancing with MINA Example
+
+=== Introduction
+
+This example shows how you can easily use the Camel-MINA component to
+design a solution allowing for distributing message workload onto
+several servers. These servers are simple TCP/IP servers created by the
+Apache MINA framework and run in separate JVMs. The load balancer
+pattern of Camel which is used on top of them allows for sending in
+Round Robin mode the messages created from a Camel Bean component
+alternatively between each server running on localhost:9991 and
+localhost:9992.
+
+Within this demo every ten seconds, a Report object is created from the
+Camel load balancer server. This object is sent by the Camel load
+balancer to a MINA server where the object is then serialized. One of
+the two MINA servers (localhost:9991 and localhost:9992) receives the
+object and enriches the message by setting the field reply of the Report
+object. The reply is sent back by the MINA server to the client, which
+then logs the reply on the console.
+
+If any of the two MINA servers is not running, then the load balancer
+will automatic failover to the next server.
+
+=== Build
+
+To compile and install the project in your maven repo, execute the
+following command on the root of the project
+
+....
+mvn clean install
+....
+
+=== Run
+
+To run the example, then execute the following command in the respective
+folder:
+
+- mina1
+
+....
+mvn exec:java -Pmina1
+....
+
+- mina2
+
+....
+mvn exec:java -Pmina2
+....
+
+- loadbalancing
+
+....
+mvn exec:java -Ploadbalancer
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-loadbalancing/README.md b/examples/camel-example-loadbalancing/README.md
index 07c866a..c1ad691 100644
--- a/examples/camel-example-loadbalancing/README.md
+++ b/examples/camel-example-loadbalancing/README.md
@@ -42,10 +42,12 @@ To run the example, then execute the following command in the respective folder:
mvn exec:java -Ploadbalancer
-### Forum, Help, etc
+### Help and contributions
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback,
+then please [let us know](https://camel.apache.org/support.html).
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+We also love contributors,
+so [get involved](https://camel.apache.org/contributing.html) :-)
+
+The Camel riders!
diff --git a/examples/camel-example-loan-broker-cxf/README.adoc b/examples/camel-example-loan-broker-cxf/README.adoc
new file mode 100644
index 0000000..03ead0f
--- /dev/null
+++ b/examples/camel-example-loan-broker-cxf/README.adoc
@@ -0,0 +1,37 @@
+== Loan Broker Example with Apache CXF
+
+=== Introduction
+
+This example shows how to use Camel to implement the EIP’s loan broker
+example, from the EIP book
+(http://www.enterpriseintegrationpatterns.com/SystemManagementExample.html).
+
+The example use web services for exchanging messages between the client,
+credit agency, and the banks.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+....
+mvn exec:java -PWS.LoanBroker
+mvn exec:java -PWS.Client
+....
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-loan-broker-cxf/README.md b/examples/camel-example-loan-broker-cxf/README.md
deleted file mode 100644
index 719e42b..0000000
--- a/examples/camel-example-loan-broker-cxf/README.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# Loan Broker Example with Apache CXF
-
-### Introduction
-This example shows how to use Camel to implement the EIP's loan broker example,
-from the EIP book (http://www.enterpriseintegrationpatterns.com/SystemManagementExample.html).
-
-The example use web services for exchanging messages between
-the client, credit agency, and the banks.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
- mvn exec:java -PWS.LoanBroker
- mvn exec:java -PWS.Client
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-loan-broker-jms/README.adoc b/examples/camel-example-loan-broker-jms/README.adoc
new file mode 100644
index 0000000..da696f7
--- /dev/null
+++ b/examples/camel-example-loan-broker-jms/README.adoc
@@ -0,0 +1,37 @@
+== Loan Broker Example with JMS
+
+=== Introduction
+
+This example shows how to use Camel to implement the EIP’s loan broker
+example, from the EIP book
+(http://www.enterpriseintegrationpatterns.com/SystemManagementExample.html).
+
+The example uses JMS queues for exchanging messages between the client,
+credit agency, and the banks.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+....
+mvn exec:java -PQueue.LoanBroker
+mvn exec:java -PQueue.Client
+....
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-loan-broker-jms/README.md b/examples/camel-example-loan-broker-jms/README.md
deleted file mode 100644
index 37cb874..0000000
--- a/examples/camel-example-loan-broker-jms/README.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# Loan Broker Example with JMS
-
-### Introduction
-This example shows how to use Camel to implement the EIP's loan broker example,
-from the EIP book (http://www.enterpriseintegrationpatterns.com/SystemManagementExample.html).
-
-The example uses JMS queues for exchanging messages between
-the client, credit agency, and the banks.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
- mvn exec:java -PQueue.LoanBroker
- mvn exec:java -PQueue.Client
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-main-artemis/readme.adoc b/examples/camel-example-main-artemis/readme.adoc
index 6c541b5..9294ef5 100644
--- a/examples/camel-example-main-artemis/readme.adoc
+++ b/examples/camel-example-main-artemis/readme.adoc
@@ -1,4 +1,4 @@
-= Camel Example Main Artemis
+== Camel Example Main Artemis
This example shows how to run Camel standalone via the built-in Main class.
The example requires a running Apache ActiveMQ Artemis broker running.
@@ -17,7 +17,7 @@ via two different styles
that performs classpath scanning to auto-detect the JMS client and prepare for autowiring
by generating the `META-INF/services/org/apache/camel/autowire.properties` file.
-== Generating tooling meta-data
+=== Generating tooling meta-data
The `camel-main-maven-plugin` is used for pre-scanning your project and prepare
autowiring and sprint boot tooling support by classpath scanning.
@@ -31,7 +31,7 @@ which are generated in `target/classes/META-INF/services/org/apache/camel/autowi
See also more details in `application.properties`
-== How to run
+=== How to run
First install https://activemq.apache.org/components/artemis/[Apache ActiveMQ Artemis]
and create a broker, such as `mybroker`, and create the admin user as `admin` as username
@@ -45,6 +45,12 @@ Then you can run this example using
mvn camel-main:generate camel:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-main-tiny/readme.adoc b/examples/camel-example-main-tiny/readme.adoc
index b195ea7..15b4980 100644
--- a/examples/camel-example-main-tiny/readme.adoc
+++ b/examples/camel-example-main-tiny/readme.adoc
@@ -1,4 +1,4 @@
-= Camel Example Main Tiny
+== Camel Example Main Tiny
The example uses the `camel-core-engine` as dependency to use as few JARs
on the classpath as possible. For more details see the `pom.xml` file.
@@ -11,7 +11,7 @@ via Camel built-in dependency-injection that supports binding via the
Also notice how you can configure Camel in the `application.properties` file.
-== Generating tooling meta-data
+=== Generating tooling meta-data
The `camel-main-maven-plugin` is used for pre-scanning your project and prepare
autowiring and sprint boot tooling support by classpath scanning.
@@ -20,12 +20,18 @@ You can run this via
mvn camel-main:generate
-== How to run
+=== How to run
You can run this example using
mvn camel:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-main/readme.adoc b/examples/camel-example-main/readme.adoc
index a12affb..89561af 100644
--- a/examples/camel-example-main/readme.adoc
+++ b/examples/camel-example-main/readme.adoc
@@ -1,4 +1,4 @@
-= Camel Example Main
+== Camel Example Main
This example shows how to run Camel standalone via the built-in Main class.
The example also demonstrates how you can configure the Camel application
@@ -7,14 +7,14 @@ via Camel built-in dependency-injection that supports binding via the
Also notice how you can configure Camel in the `application.properties` file.
-== Alternative example
+=== Alternative example
The class `StandaloneCamel` is an alternative example that uses a
_public static void main_ class and where you manually setup Camel without
any help from Camel's built-in Main class. However it shows how to do this
in a _raw style_ without using any _magic_.
-== Generating tooling meta-data
+=== Generating tooling meta-data
The `camel-main-maven-plugin` is used for pre-scanning your project and prepare
autowiring and sprint boot tooling support by classpath scanning.
@@ -23,12 +23,18 @@ You can run this via
mvn camel-main:generate
-== How to run
+=== How to run
You can run this example using
mvn camel:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-management/README.adoc b/examples/camel-example-management/README.adoc
new file mode 100644
index 0000000..f66c56f
--- /dev/null
+++ b/examples/camel-example-management/README.adoc
@@ -0,0 +1,91 @@
+== Camel JMX Management
+
+=== Introduction
+
+This example shows how to manage Camel using JMX (with jconsole)
+
+The example uses a timer to every 5th second to generate a file with 100
+stock quotes.
+
+Another route uses a file consumer to read the files and split the file
+and send every single stock quote to a JMS queue.
+
+Then a third route consumes from this JMS queue and simulate a little
+CPU heavy work (by delaying) before the data is transformed and logged.
+The logger will log the progress by logging how long time it takes to
+process 100 messages.
+
+Now the idea is to use the Camel JMX management to be able to adjust
+this during runtime. What it allows you to do is to improve the
+performance of this example.
+
+At first there is a throttler that will throttle how fast Camel sends
+message to the JMS queue. For starters you can change this at runtime
+from the default 10 msg/sec to 500 msg/sec etc. This is done by changing
+the JMX attribute maximumRequestsPerPeriod on the throttler in the
+/producer group.
+
+The next issue is that the JMS consumer now cannot catch up and you
+should see that the number of messages on the JMS queue grows a little
+by little. You can find the queue from the ActiveMQ mbean and drill down
+under /queues.
+
+If this goes a bit to slow you can increase the first route in Camel to
+produce files faster. This is done by changing the period in the timer
+endpoint from 5000 to let say 2000. Before this takes effect you have to
+restart the timer consumer. So find the timer consumer and invoke the
+stop and start JMX operation.
+
+Now you should see the messages start to pile up in the JMS queue. What
+we do next is to increase the number of concurrent consumers. To do that
+you have to set this on the JMS endpoint. Set the concurrentConsumers
+from 1 to 20. And just as the timer consumer this only takes effect when
+the JMS consumer is restarted. So do a stop and start operation.
+
+What you should see is that Camel should be able to process the files
+much faster now and the logger should output a higher throughput.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+To use jconsole type
+
+....
+jconsole
+....
+
+And you should be able to see a process id in the connect to agent tab.
+If its there then click in and you should be connected to the Camel
+application. If its missing you can click on the advanced tab and type
+in JMX URL:
+`+service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel+` (some
+older versions of Java does not list the local processes)
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java directory+` and the Spring XML configuration lives in
+`+src/main/resources/META-INF/spring+`
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-management/README.md b/examples/camel-example-management/README.md
deleted file mode 100644
index 71251d6..0000000
--- a/examples/camel-example-management/README.md
+++ /dev/null
@@ -1,73 +0,0 @@
-# Camel JMX Management
-
-### Introduction
-
-This example shows how to manage Camel using JMX (with jconsole)
-
-The example uses a timer to every 5th second to generate a file with 100 stock quotes.
-
-Another route uses a file consumer to read the files and split the file and send every single
-stock quote to a JMS queue.
-
-Then a third route consumes from this JMS queue and simulate a little CPU heavy work (by delaying)
-before the data is transformed and logged. The logger will log the progress by logging how
-long time it takes to process 100 messages.
-
-Now the idea is to use the Camel JMX management to be able to adjust this during runtime.
-What it allows you to do is to improve the performance of this example.
-
-At first there is a throttler that will throttle how fast Camel sends message to the JMS queue.
-For starters you can change this at runtime from the default 10 msg/sec to 500 msg/sec etc.
-This is done by changing the JMX attribute maximumRequestsPerPeriod on the throttler in the /producer group.
-
-The next issue is that the JMS consumer now cannot catch up and you should see that the number of messages
-on the JMS queue grows a little by little. You can find the queue from the ActiveMQ mbean and drill down under /queues.
-
-If this goes a bit to slow you can increase the first route in Camel to produce files faster. This is done by
-changing the period in the timer endpoint from 5000 to let say 2000. Before this takes effect you have to
-restart the timer consumer. So find the timer consumer and invoke the stop and start JMX operation.
-
-Now you should see the messages start to pile up in the JMS queue.
-What we do next is to increase the number of concurrent consumers. To do that you have to set this on the JMS
-endpoint. Set the concurrentConsumers from 1 to 20. And just as the timer consumer this only takes effect when
-the JMS consumer is restarted. So do a stop and start operation.
-
-What you should see is that Camel should be able to process the files much faster now and the logger should
-output a higher throughput.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-
-### Run
-
-To run the example type
-
- mvn camel:run
-
-To use jconsole type
-
- jconsole
-
-And you should be able to see a process id in the connect to agent tab.
-If its there then click in and you should be connected to the Camel application.
-If its missing you can click on the advanced tab and type in JMX URL:
- `service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel`
- (some older versions of Java does not list the local processes)
-
-You can see the routing rules by looking at the java code in the
-`src/main/java directory` and the Spring XML configuration lives in
-`src/main/resources/META-INF/spring`
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-micrometer/README.adoc b/examples/camel-example-micrometer/README.adoc
new file mode 100644
index 0000000..08fd301
--- /dev/null
+++ b/examples/camel-example-micrometer/README.adoc
@@ -0,0 +1,80 @@
+== Spring Java Config Example
+
+=== Introduction
+
+This example shows how to work with Micrometer metrics, using Spring
+Java Config to boot up Camel, configure the routes and meters.
+
+The example triggers an exchange every 10s that runs through a route
+using a variable delay. The exchange is measured in various ways:
+
+* using Micrometer producers (timer and distribution summary)
+* using a Route Policy Factory
+* using Event Notifiers
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Setup of Monitoring backend
+
+This example uses https://prometheus.io[Prometheus] as monitoring
+backend.
+
+* Download the package for your platform and unpack it on your local
+host
+* Edit the `+prometheus.yml+` file and append another `+scrape_config+`:
+
+....
+...
+ - job_name: 'camel'
+ static_configs:
+ - targets: ['localhost:8088']
+....
+
+* Start up Prometheus
+
+Optionally, you can install a metrics visualizer,
+e.g. https://grafana.com/[Grafana]:
+
+* Download the package for your platform and unpack it on your local
+host
+* Add your Prometheus server as a data source
+* Import a https://grafana.com/dashboards/4701[suitable dashboard]
+* Add some graphs to display Camel metrics (this is out of scope for
+this example).
+
+=== Run
+
+To run the example type
+
+....
+mvn exec:java
+....
+
+* You can access http://localhost:8088/metrics in order to manually
+obtain the Micrometer output for Prometheus.
+* In Prometheus, you can
+https://prometheus.io/docs/prometheus/latest/querying/examples/[query]
+for one of the metrics related to Camel or the JVM.
+
+To stop the example hit Ctrl+c
+
+=== Configuration
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java directory+`
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-micrometer/README.md b/examples/camel-example-micrometer/README.md
deleted file mode 100644
index 8fd6123..0000000
--- a/examples/camel-example-micrometer/README.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Spring Java Config Example
-
-### Introduction
-This example shows how to work with Micrometer metrics, using Spring Java Config
-to boot up Camel, configure the routes and meters.
-
-The example triggers an exchange every 10s that runs through a route using a variable delay.
-The exchange is measured in various ways:
-
-* using Micrometer producers (timer and distribution summary)
-* using a Route Policy Factory
-* using Event Notifiers
-
-
-### Build
-You will need to compile this example first:
-
- mvn compile
-
-
-### Setup of Monitoring backend
-
-This example uses [Prometheus](https://prometheus.io) as monitoring backend.
-
-* Download the package for your platform and unpack it on your local host
-* Edit the `prometheus.yml` file and append another `scrape_config`:
-
-```
-...
- - job_name: 'camel'
- static_configs:
- - targets: ['localhost:8088']
-```
-
-* Start up Prometheus
-
-Optionally, you can install a metrics visualizer, e.g. [Grafana](https://grafana.com/):
-
-* Download the package for your platform and unpack it on your local host
-* Add your Prometheus server as a data source
-* Import a [suitable dashboard](https://grafana.com/dashboards/4701)
-* Add some graphs to display Camel metrics (this is out of scope for this example).
-
-
-### Run
-To run the example type
-
- mvn exec:java
-
-
-* You can access http://localhost:8088/metrics in order to manually obtain the Micrometer output for Prometheus.
-* In Prometheus, you can [query](https://prometheus.io/docs/prometheus/latest/querying/examples/) for one of
-the metrics related to Camel or the JVM.
-
-To stop the example hit <kbd>Ctrl</kbd>+<kbd>c</kbd>
-
-### Configuration
-You can see the routing rules by looking at the java code in the
-`src/main/java directory`
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-
-The Camel riders!
diff --git a/examples/camel-example-mybatis/README.adoc b/examples/camel-example-mybatis/README.adoc
new file mode 100644
index 0000000..1020324
--- /dev/null
+++ b/examples/camel-example-mybatis/README.adoc
@@ -0,0 +1,59 @@
+== Camel MyBatis Example
+
+=== Introduction
+
+This example shows how to exchange data using a shared database table.
+
+The example has two Camel routes. The first route inserts new data into
+the table, triggered by a timer to run every 5th second.
+
+The second route picks up the newly inserted rows from the table,
+process the row(s), and mark the row(s) as processed when done; to avoid
+picking up the same rows again.
+
+=== Build
+
+You will need to install this example first to your local maven
+repository with:
+
+....
+mvn install
+....
+
+=== Run
+
+This example requires running in Apache Karaf / ServiceMix
+
+You can install this example from the shell using this example’s
+`+features.xml+` for easy provisioning.
+
+....
+feature:repo-add camel ${version}
+feature:install camel
+feature:repo-add mvn:org.apache.camel.example/camel-example-mybatis/${version}/xml/features
+feature:install camel-example-mybatis
+....
+
+And you can see the application running by tailing the logs
+
+....
+log:tail
+....
+
+And you can use ctrl+c to stop tailing the log.
+
+=== Configuration
+
+This example uses OSGi Blueprint to setup and configure the database, as
+well the CamelContext. You can see this in the following file: In the
+`+src/main/resources/OSGI-INF/blueprint/camel-mybatis.xml+`
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-mybatis/README.md b/examples/camel-example-mybatis/README.md
deleted file mode 100644
index 2b8b365..0000000
--- a/examples/camel-example-mybatis/README.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# Camel MyBatis Example
-
-### Introduction
-
-This example shows how to exchange data using a shared database table.
-
-The example has two Camel routes. The first route inserts new data into the table,
-triggered by a timer to run every 5th second.
-
-The second route picks up the newly inserted rows from the table,
-process the row(s), and mark the row(s) as processed when done;
-to avoid picking up the same rows again.
-
-### Build
-
-You will need to install this example first to your local maven repository with:
-
- mvn install
-
-### Run
-
-This example requires running in Apache Karaf / ServiceMix
-
-You can install this example from the shell using this example's `features.xml`
-for easy provisioning.
-
- feature:repo-add camel ${version}
- feature:install camel
- feature:repo-add mvn:org.apache.camel.example/camel-example-mybatis/${version}/xml/features
- feature:install camel-example-mybatis
-
-And you can see the application running by tailing the logs
-
- log:tail
-
-And you can use <kbd>ctrl</kbd>+<kbd>c</kbd> to stop tailing the log.
-
-### Configuration
-
-This example uses OSGi Blueprint to setup and configure the database,
-as well the CamelContext. You can see this in the following file:
-In the `src/main/resources/OSGI-INF/blueprint/camel-mybatis.xml`
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-netty-custom-correlation/readme.adoc b/examples/camel-example-netty-custom-correlation/readme.adoc
index 8950f0d..51f44a7 100644
--- a/examples/camel-example-netty-custom-correlation/readme.adoc
+++ b/examples/camel-example-netty-custom-correlation/readme.adoc
@@ -1,4 +1,4 @@
-= Camel Example Netty Custom Correlation
+== Camel Example Netty Custom Correlation
This example shows how to use TCP communication with Netty using a custom codec
to encode and decode the data over the wire.
@@ -8,7 +8,7 @@ to multiplex concurrent messages over the same connection. A custom correlation
is implemented to be able to correlate the request and response message pairs so you
do not mix-data to wrong replies.
-== How to run
+=== How to run
You can run this example using two JVMs.
@@ -25,6 +25,12 @@ For requests that contains the word `beer` is delayed on the server side, and yo
should notice that its corresponding reply is correlated correclty to its beloing request thread.
Also the messages can be inter-leaved when some messages are faster than others.
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-netty-http/README.md b/examples/camel-example-netty-http/README.adoc
similarity index 67%
rename from examples/camel-example-netty-http/README.md
rename to examples/camel-example-netty-http/README.adoc
index bf9e41b..9460ff6 100644
--- a/examples/camel-example-netty-http/README.md
+++ b/examples/camel-example-netty-http/README.adoc
@@ -1,84 +1,97 @@
-# Camel Netty HTTP Server Example
+== Camel Netty HTTP Server Example
-### Introduction
+=== Introduction
-This example shows how to use a shared Netty HTTP Server in an OSGi environment.
+This example shows how to use a shared Netty HTTP Server in an OSGi
+environment.
There is 4 modules in this example:
-* `shared-netty-http-server` - The Shared Netty HTTP server that the other Camel applications uses
-* `myapp-one` - A Camel application that reuses the shared Netty HTTP server
-* `myapp-two` - A Camel application that reuses the shared Netty HTTP server
+* `+shared-netty-http-server+` - The Shared Netty HTTP server that the
+other Camel applications uses
+* `+myapp-one+` - A Camel application that reuses the shared Netty HTTP
+server
+* `+myapp-two+` - A Camel application that reuses the shared Netty HTTP
+server
-### Build
+=== Build
You will need to compile this example first:
-```sh
+[source,sh]
+----
$ mvn install
-```
+----
-### Run
+=== Run
-This example runs in Apache Karaf / ServiceMix. To install Apache Camel in Karaf you type in the shell:
+This example runs in Apache Karaf / ServiceMix. To install Apache Camel
+in Karaf you type in the shell:
-```sh
+[source,sh]
+----
karaf@root()> repo-add camel ${version}
karaf@root()> feature:install camel
-```
+----
Then you need to install the following features in Karaf/ServiceMix:
-```sh
+[source,sh]
+----
karaf@root()> feature:install camel-netty-http
-```
+----
-Then you can install the shared Netty HTTP server which by default runs on port `8888`.
-The port number can be changed by editing the following source file:
+Then you can install the shared Netty HTTP server which by default runs
+on port `+8888+`. The port number can be changed by editing the
+following source file:
- `shared-netty-http-server/src/main/resources/OSGI-INF/blueprint/http-server.xml`
+`+shared-netty-http-server/src/main/resources/OSGI-INF/blueprint/http-server.xml+`
In the Apache Karaf / ServiceMix shell type:
-```sh
+[source,sh]
+----
karaf@root()> install -s mvn:org.apache.camel.example/camel-example-netty-http-shared/${version}
-```
+----
Then you can install the Camel applications:
-```sh
+[source,sh]
+----
karaf@root()> install -s mvn:org.apache.camel.example/camel-example-netty-myapp-one/${version}
karaf@root()> install -s mvn:org.apache.camel.example/camel-example-netty-myapp-two/${version}
-```
+----
-From a web browser you can then try the example by accessing the following URLs:
+From a web browser you can then try the example by accessing the
+following URLs:
-<http://localhost:8888/one>
+http://localhost:8888/one
-<http://localhost:8888/two>
+http://localhost:8888/two
Camel commands can be used to gain some insights on the CDI Camel
context, e.g.:
-- The `camel:context-list` displays the CDI Camel contexts:
-
- ```
- karaf@root()> camel:context-list
- Context Status Total # Failed # Inflight # Uptime
- ------- ------ ------- -------- ---------- ------
- camel-1 Started 1 0 0 1 minute
- camel-2 Started 1 0 0 1 minute
- ```
+* The `+camel:context-list+` displays the CDI Camel contexts:
++
+....
+karaf@root()> camel:context-list
+ Context Status Total # Failed # Inflight # Uptime
+ ------- ------ ------- -------- ---------- ------
+ camel-1 Started 1 0 0 1 minute
+ camel-2 Started 1 0 0 1 minute
+....
Or by tailing the log with:
-```sh
+[source,sh]
+----
karaf@root()> log:tail
-```
+----
The following messages should be displayed:
-```
+....
2017-05-10 21:36:55,582 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 52 - org.apache.camel.camel-blueprint - 2.17.0 | Attempting to start Camel Context camel-2
2017-05-10 21:36:55,582 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 52 - org.apache.camel.camel-blueprint - 2.17.0 | Apache Camel 2.17.0 (CamelContext: camel-2) is starting
2017-05-10 21:36:55,583 | INFO | nt Dispatcher: 1 | ManagedManagementStrategy | 54 - org.apache.camel.camel-core - 2.17.0 | JMX is enabled
@@ -89,14 +102,16 @@ The following messages should be displayed:
2017-05-10 21:36:55,646 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 52 - org.apache.camel.camel-blueprint - 2.17.0 | Route: http-route-two started and consuming from: http://localhost/two
2017-05-10 21:36:55,647 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 52 - org.apache.camel.camel-blueprint - 2.17.0 | Total 1 routes, of which 1 are started.
2017-05-10 21:36:55,647 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 52 - org.apache.camel.camel-blueprint - 2.17.0 | Apache Camel 2.17.0 (CamelContext: camel-2) started in 0.065 seconds
-```
+....
+
+Hit ctrl+c to exit the log command.
-Hit <kbd>ctrl</kbd>+<kbd>c</kbd> to exit the log command.
+=== Help and contributions
-### Forum, Help, etc
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+The Camel riders!
diff --git a/examples/camel-example-olingo4-blueprint/README.md b/examples/camel-example-olingo4-blueprint/README.adoc
similarity index 75%
rename from examples/camel-example-olingo4-blueprint/README.md
rename to examples/camel-example-olingo4-blueprint/README.adoc
index b8bb0bd..ff346b8 100644
--- a/examples/camel-example-olingo4-blueprint/README.md
+++ b/examples/camel-example-olingo4-blueprint/README.adoc
@@ -1,47 +1,53 @@
-# Camel Olingo4 OSGI Example using Blueprint
+== Camel Olingo4 OSGI Example using Blueprint
-### Introduction
+=== Introduction
-This example shows how to use the camel-olingo4 component in an OSGI environment. We will use the
-the sample OData 4.0 remote TripPinservice published on http://services.odata.org/TripPinRESTierService by creating
-two People who's data are loaded from a directory.
+This example shows how to use the camel-olingo4 component in an OSGI
+environment. We will use the the sample OData 4.0 remote TripPinservice
+published on http://services.odata.org/TripPinRESTierService by creating
+two People who’s data are loaded from a directory.
-#### OSGi / Karaf
+==== OSGi / Karaf
-This example can be executed within Karaf 4.x. and relies on the ```camel-olingo4``` feature.
+This example can be executed within Karaf 4.x. and relies on the
+`+camel-olingo4+` feature.
To run the example, from the command line:
-1. In the Karaf install root directory, start Karaf:
-
- ```sh
- $ bin/karaf
- ```
-
-2. Install the pre-requisites:
-
- ```sh
- karaf@root()> repo-add camel ${version}
- karaf@root()> feature:install camel-blueprint camel-olingo4
- ```
-
-3. Then install and start the example:
-
- ```sh
- karaf@root()> install -s mvn:org.apache.camel.example/camel-example-olingo4-blueprint/${version}
- ```
-4. Copy the files found in ```src/main/resources``` to the ```work/odata/input``` in the karaf install
- root directory created by the camel route.
+[arabic]
+. In the Karaf install root directory, start Karaf:
++
+[source,sh]
+----
+$ bin/karaf
+----
+. Install the pre-requisites:
++
+[source,sh]
+----
+karaf@root()> repo-add camel ${version}
+karaf@root()> feature:install camel-blueprint camel-olingo4
+----
+. Then install and start the example:
++
+[source,sh]
+----
+karaf@root()> install -s mvn:org.apache.camel.example/camel-example-olingo4-blueprint/${version}
+----
+. Copy the files found in `+src/main/resources+` to the
+`+work/odata/input+` in the karaf install root directory created by the
+camel route.
By tailing the log with:
-```sh
+[source,sh]
+----
karaf@root()> log:tail
-```
+----
The following messages should be displayed:
-```
+....
2017-11-29 15:46:22,524 | INFO | nt Dispatcher: 1 | BlueprintCamelContext | 62 - org.apache.camel.camel-core - 2.21.0.SNAPSHOT | Apache Camel 2.21.0-SNAPSHOT (CamelContext: odata4-example-context) started in 0.102 seconds
2017-11-29 15:46:23,528 | INFO | work/odata/input | odata-route | 62 - org.apache.camel.camel-core - 2.21.0.SNAPSHOT | Receiving file person2.json
2017-11-29 15:46:23,528 | INFO | work/odata/input | odata-route | 62 - org.apache.camel.camel-core - 2.21.0.SNAPSHOT | Sending file person2.json to OData Test Service
@@ -49,22 +55,21 @@ The following messages should be displayed:
2017-11-29 15:46:24,317 | INFO | work/odata/input | odata-route | 62 - org.apache.camel.camel-core - 2.21.0.SNAPSHOT | Sending file person1.json to OData Test Service
2017-11-29 15:46:24,665 | INFO | I/O dispatcher 1 | odata-route | 62 - org.apache.camel.camel-core - 2.21.0.SNAPSHOT | Done creating person with properties [ClientPropertyImpl{name=UserName, value=jdoe, annotations=[]}, ClientPropertyImpl{name=FirstName, value=John, annotations=[]}, ClientPropertyImpl{name=LastName, value=Doe, annotations=[]}, ClientPropertyImpl{name=MiddleName, value=, annotations=[]}, ClientPropertyImpl{name=Gender, value=Male, annotations=[]}, Cl [...]
2017-11-29 15:46:24,689 | INFO | I/O dispatcher 2 | odata-route | 62 - org.apache.camel.camel-core - 2.21.0.SNAPSHOT | Done creating person with properties [ClientPropertyImpl{name=UserName, value=jmorrow, annotations=[]}, ClientPropertyImpl{name=FirstName, value=Jerome, annotations=[]}, ClientPropertyImpl{name=LastName, value=Morrow, annotations=[]}, ClientPropertyImpl{name=MiddleName, value=, annotations=[]}, ClientPropertyImpl{name=Gender, value=Male, annotations [...]
-
-```
+....
You can uninstall the example with:
-```sh
+[source,sh]
+----
karaf@root()> uninstall camel-example-olingo4-blueprint
-```
-
-### Forum, Help, etc
+----
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+=== Help and contributions
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-opentracing/README.adoc b/examples/camel-example-opentracing/README.adoc
new file mode 100644
index 0000000..63190d7
--- /dev/null
+++ b/examples/camel-example-opentracing/README.adoc
@@ -0,0 +1,71 @@
+== OpenTracing Example
+
+=== Introduction
+
+This example shows how to use Camel with OpenTracing to trace all
+incoming and outgoing Camel messages.
+
+The example uses a logging tracer (based on the MockTracer) to display
+tracing information on the console.
+
+The example includes four sub maven modules that implement
+
+* client
+* service1
+* service2
+* loggingtracer
+
+Where client -> service1 -> service2 using HTTP.
+
+=== Build
+
+You will need to compile this example first:
+
+[source,sh]
+----
+$ mvn compile
+----
+
+=== Run the example
+
+Then using three different shells and run service1 and service2 before
+the client. These services use an annotation _CamelOpenTracing_ to
+indicate that the service should be traced.
+
+[source,sh]
+----
+$ cd service1
+$ mvn compile spring-boot:run
+----
+
+When service1 is ready then start service2
+
+[source,sh]
+----
+$ cd service2
+$ mvn compile spring-boot:run
+----
+
+And then start the client that calls service1 every 30 seconds.
+
+[source,sh]
+----
+$ cd client
+$ mvn compile camel:run
+----
+
+The client application explicitly instantiates and initializes the
+OpenTracing Tracer with the _CamelContext_.
+
+The shells will show _SPAN FINISHED_ messages indicating what spans have
+been reported from the client and two services.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-opentracing/README.md b/examples/camel-example-opentracing/README.md
deleted file mode 100644
index c5060de..0000000
--- a/examples/camel-example-opentracing/README.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# OpenTracing Example
-
-### Introduction
-
-This example shows how to use Camel with OpenTracing to trace all incoming and outgoing Camel messages.
-
-The example uses a logging tracer (based on the MockTracer) to display tracing information on the console.
-
-The example includes four sub maven modules that implement
-
-- client
-- service1
-- service2
-- loggingtracer
-
-Where client -> service1 -> service2 using HTTP.
-
-### Build
-
-You will need to compile this example first:
-
-```sh
-$ mvn compile
-```
-
-### Run the example
-
-Then using three different shells and run service1 and service2 before the client. These services use an annotation _CamelOpenTracing_ to indicate that the service should be traced.
-
-```sh
-$ cd service1
-$ mvn compile spring-boot:run
-```
-
-When service1 is ready then start service2
-
-```sh
-$ cd service2
-$ mvn compile spring-boot:run
-```
-
-And then start the client that calls service1 every 30 seconds.
-
-```sh
-$ cd client
-$ mvn compile camel:run
-```
-
-The client application explicitly instantiates and initializes the OpenTracing Tracer with the _CamelContext_.
-
-The shells will show *SPAN FINISHED* messages indicating what spans have been reported from the client
-and two services.
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-The Camel riders!
diff --git a/examples/camel-example-pojo-messaging/README.adoc b/examples/camel-example-pojo-messaging/README.adoc
new file mode 100644
index 0000000..57f9e16
--- /dev/null
+++ b/examples/camel-example-pojo-messaging/README.adoc
@@ -0,0 +1,35 @@
+== POJO Messaging Example
+
+=== Introduction
+
+This example shows that you don’t need to learn Camel’s super cool DSLs
+if you don’t want to. Camel has a set of annotations that allow you to
+produce, consume or route messages to endpoints.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-pojo-messaging/README.md b/examples/camel-example-pojo-messaging/README.md
deleted file mode 100644
index 90bf8c9..0000000
--- a/examples/camel-example-pojo-messaging/README.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# POJO Messaging Example
-
-### Introduction
-
-This example shows that you don't need to learn Camel's super cool DSLs
-if you don't want to. Camel has a set of annotations that allow you to
-produce, consume or route messages to endpoints.
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the example type
-
- mvn camel:run
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-rabbitmq/readme.adoc b/examples/camel-example-rabbitmq/readme.adoc
index c82d5d3..991656b 100644
--- a/examples/camel-example-rabbitmq/readme.adoc
+++ b/examples/camel-example-rabbitmq/readme.adoc
@@ -1,4 +1,4 @@
-= Camel Example RabbitMQ
+== Camel Example RabbitMQ
This example shows how to work with a simple Apache Camel application that routes message to RabbitMQ.
@@ -12,7 +12,7 @@ This can be configured in the `application.properties` file.
The login information is the default `guest/guest` account, which can be configured
in the `application.properties` file as well.
-== How to run
+=== How to run
The sample requires a RabbitMQ broker to be running.
@@ -24,6 +24,12 @@ Then you can run this example using
mvn spring-boot:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-reactive-executor-vertx/readme.adoc b/examples/camel-example-reactive-executor-vertx/readme.adoc
index 51277db..03d30e7 100644
--- a/examples/camel-example-reactive-executor-vertx/readme.adoc
+++ b/examples/camel-example-reactive-executor-vertx/readme.adoc
@@ -1,15 +1,25 @@
-= Camel Example Reactive Executor VertX
+== Camel Example Reactive Executor VertX
This example uses VertX as the reactive executor for routing messages with Camel.
By default Camel uses its own reactive engine for routing messages, but you can plugin
different engines via a SPI interface. This example uses VertX as the engine.
-== How to run
+=== How to run
You can run this example using
mvn camel:run
-== More information
+=== More information
You can find more information about Apache Camel at the website: http://camel.apache.org/
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-reactive-streams/readme.adoc b/examples/camel-example-reactive-streams/readme.adoc
index e7860e2..b25103b 100644
--- a/examples/camel-example-reactive-streams/readme.adoc
+++ b/examples/camel-example-reactive-streams/readme.adoc
@@ -1,4 +1,4 @@
-# Camel Example Reactive Streams
+== Camel Example Reactive Streams
This example shows some possible usages of the Camel reactive streams component.
@@ -15,12 +15,18 @@ The following sample routes are started together in a spring-boot application (a
All routes are enabled by default, but they can be switched off by changing the `src/main/resources/application.yml` file.
Each route is contained in a separate Java class.
-= How to run
+=== How to run
You can run this example using
mvn spring-boot:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-rest-producer/readme.adoc b/examples/camel-example-rest-producer/readme.adoc
index a381635..e2eb264 100644
--- a/examples/camel-example-rest-producer/readme.adoc
+++ b/examples/camel-example-rest-producer/readme.adoc
@@ -1,17 +1,17 @@
-# Camel Example Rest Producer
+== Camel Example Rest Producer
This example shows how to call a REST service using Camel Rest.
The example uses a timer to trigger a Camel route to call the REST service.
The REST service is embedded within Spring Boot itself so it can run standalone.
-= Camel routes
+=== Camel routes
The Camel route is located in the `RestRoute` class. In this class the route
starts from a timer, that triggers every 2nd second and calls the REST service using the rest endpoint
which returns a message, that is logged.
-== Configuring Rest
+=== Configuring Rest
The rest producer is configured using Camels Rest DSL which is done using the `restConfiguration` in the route.
The actual HTTP client that is used to call the REST service is `camel-http` which is added as dependency
@@ -23,12 +23,18 @@ in the `pom.xml` file. You can use other HTTP clients with the REST producer suc
- camel-restlet
- camel-undertow
-== How to run
+=== How to run
You can run this example using
mvn spring-boot:run
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-rest-swagger/README.adoc b/examples/camel-example-rest-swagger/README.adoc
new file mode 100644
index 0000000..a942e16
--- /dev/null
+++ b/examples/camel-example-rest-swagger/README.adoc
@@ -0,0 +1,41 @@
+== Camel Rest Swagger example
+
+This example shows how to call a REST service defined using Swagger
+specification with the help of Camel Rest Swagger component.
+
+The example is a standalong Spring Boot application that acts as a REST
+client, you can run simply by issuing:
+
+....
+$ mvn spring-boot:run
+....
+
+Or by packaging it and running it using `+java+` CLI:
+
+....
+$ mvn package
+$ java -jar target/camel-example-rest-swagger-*.jar
+....
+
+The example by default uses the PetStore demo hosted on swagger.io and
+invokes the `+getInventory+` operation. You can make it call any API
+that you have Swagger specification for and any operation with simple
+arguments, for instance this retrives a pet from the PetStore demo with
+ID `+9584+`:
+
+....
+$ java -jar target/camel-example-rest-swagger-*.jar \
+ --swagger=http://petstore.swagger.io/v2/swagger.json \
+ --operation=getPetById \
+ --petId=9584
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-rest-swagger/README.md b/examples/camel-example-rest-swagger/README.md
deleted file mode 100644
index d8c0bcb..0000000
--- a/examples/camel-example-rest-swagger/README.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# Camel Rest Swagger example
-
-This example shows how to call a REST service defined using Swagger
-specification with the help of Camel Rest Swagger component.
-
-The example is a standalong Spring Boot application that acts as a REST
-client, you can run simply by issuing:
-
- $ mvn spring-boot:run
-
-Or by packaging it and running it using `java` CLI:
-
- $ mvn package
- $ java -jar target/camel-example-rest-swagger-*.jar
-
-The example by default uses the PetStore demo hosted on swagger.io and
-invokes the `getInventory` operation. You can make it call any API
-that you have Swagger specification for and any operation with simple
-arguments, for instance this retrives a pet from the PetStore demo with
-ID `9584`:
-
- $ java -jar target/camel-example-rest-swagger-*.jar \
- --swagger=http://petstore.swagger.io/v2/swagger.json \
- --operation=getPetById \
- --petId=9584
-
-## More information
-
-You can find more information about Apache Camel at the website:
-http://camel.apache.org/
diff --git a/examples/camel-example-restlet-jdbc/README.adoc b/examples/camel-example-restlet-jdbc/README.adoc
new file mode 100644
index 0000000..535d6e9
--- /dev/null
+++ b/examples/camel-example-restlet-jdbc/README.adoc
@@ -0,0 +1,102 @@
+== Camel Restlet and JDBC Example
+
+=== Introduction
+
+An example which shows how to expose CRUD operations with REST DSL
+interface and JDBC implementation
+
+Two implementations are available
+
+* XML Rest DSL (default)
+* Java Rest DSL
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+=== Run Java-REST-DSL
+
+To run with Java-REST-DSL use:
+
+....
+mvn jetty:run -Dimpl=java-rest-dsl
+....
+
+=== Run XML-REST-DSL
+
+To run with XML-REST-DSL use:
+
+....
+mvn jetty:run -Dimpl=xml-rest-dsl
+....
+
+=== Check
+
+To create an person, make a http POST request with firstName and
+lastName parameters:
+
+....
+curl -X POST -d "firstName=test&lastName=person" http://localhost:8080/rs/persons
+....
+
+_Result :_
+
+....
+[{ID=1, FIRSTNAME=test, LASTNAME=person}]
+....
+
+To update an existing person, make a http PUT request with firstName and
+lastName parameters:
+
+....
+curl -X PUT -d "firstName=updated&lastName=person" http://localhost:8080/rs/persons/1
+....
+
+To retrieve an existing person, make a http GET request with the
+personId as part of the url:
+
+....
+curl http://localhost:8080/rs/persons/1
+....
+
+_Result :_
+
+....
+[{ID=1, FIRSTNAME=updated, LASTNAME=person}]
+....
+
+To retrieve all the existing persons, make a http GET request to persons
+url:
+
+....
+curl http://localhost:8080/rs/persons
+....
+
+_Result :_
+
+....
+[{ID=1, FIRSTNAME=updated, LASTNAME=person}]
+....
+
+To delete an existing person, make a http DELETE request with the
+personId as part of the url:
+
+....
+curl -X DELETE http://localhost:8080/rs/persons/1
+....
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-restlet-jdbc/README.md b/examples/camel-example-restlet-jdbc/README.md
deleted file mode 100644
index 54ce869..0000000
--- a/examples/camel-example-restlet-jdbc/README.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# Camel Restlet and JDBC Example
-
-### Introduction
-An example which shows how to expose CRUD operations with REST DSL interface and JDBC implementation
-
-Two implementations are available
-
-* XML Rest DSL (default)
-* Java Rest DSL
-
-
-### Build
-
-You will need to compile this example first:
-
- mvn install
-
-### Run
-
-### Run Java-REST-DSL
-To run with Java-REST-DSL use:
-
- mvn jetty:run -Dimpl=java-rest-dsl
-
-### Run XML-REST-DSL
-To run with XML-REST-DSL use:
-
- mvn jetty:run -Dimpl=xml-rest-dsl
-
-### Check
-To create an person, make a http POST request with firstName and lastName parameters:
-
- curl -X POST -d "firstName=test&lastName=person" http://localhost:8080/rs/persons
-
-*Result :*
-
- [{ID=1, FIRSTNAME=test, LASTNAME=person}]
-
-To update an existing person, make a http PUT request with firstName and lastName parameters:
-
- curl -X PUT -d "firstName=updated&lastName=person" http://localhost:8080/rs/persons/1
-
-To retrieve an existing person, make a http GET request with the personId as part of the url:
-
- curl http://localhost:8080/rs/persons/1
-
-*Result :*
-
- [{ID=1, FIRSTNAME=updated, LASTNAME=person}]
-
-
-To retrieve all the existing persons, make a http GET request to persons url:
-
- curl http://localhost:8080/rs/persons
-
-*Result :*
-
- [{ID=1, FIRSTNAME=updated, LASTNAME=person}]
-
-To delete an existing person, make a http DELETE request with the personId as part of the url:
-
- curl -X DELETE http://localhost:8080/rs/persons/1
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-route-throttling/README.adoc b/examples/camel-example-route-throttling/README.adoc
new file mode 100644
index 0000000..5acaa25
--- /dev/null
+++ b/examples/camel-example-route-throttling/README.adoc
@@ -0,0 +1,73 @@
+== Camel Route Throttling
+
+=== Introduction
+
+This example shows how to use the new feature in Camel 2.1 which is
+RoutePolicy. A route policy allows you to associate a route with a
+policy. Camel provides a throttling policy which allows Camel to dynamic
+throttle the route consumer depending on the number of concurrent
+messages current in flight.
+
+The Server is required to be running when you start the client. You can
+see on the server it should log in the console how it adjust the
+throttling dynamically.
+
+The goal of this example is to illustrate that Camel throttles the JMS
+queue to be on same pace with the rest of the Camel routing. When
+running the example you should observe that the JMS route and the SEDA
+route completes nearly in sync.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== How to Run
+
+The example has 3 maven goals to run the example
+
+....
+mvn compile exec:java -PCamelServer
+....
+
+Starts the Camel Server which contains the 3 routes and where you should
+check its log output for how it goes.
+
+....
+mvn compile exec:java -PCamelClient
+....
+
+Is a client that sends 10000 JMS messages to the JMS broker which is
+consumed by route1. The Server must be started beforehand.
+
+....
+mvn compile exec:java -PCamelFileClient
+....
+
+Is a client that creates 5000 files that are consumed by route2. The
+server may be started beforehand, but its not required.
+
+So at first you start the server. Then at any time you can run a client
+at will. For example you can run the JMS client and let it run to
+completion at the server. You can see at the server console logging that
+it reports the progress. And at sometime it will reach 10000 messages
+processed. You can then start the client again if you like. You can also
+start the other client to create the files which then let the example be
+a bit more complicated as we have concurrent processing of JMS messages
+and files at the same time. And where as both of these should be dynamic
+throttled so we wont go too fast.
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-route-throttling/README.md b/examples/camel-example-route-throttling/README.md
index 81116ae..3588a48 100644
--- a/examples/camel-example-route-throttling/README.md
+++ b/examples/camel-example-route-throttling/README.md
@@ -42,11 +42,12 @@ You can also start the other client to create the files which then let the examp
To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
+### Help and contributions
-### Forum, Help, etc
+If you hit any problem using Camel or have some feedback,
+then please [let us know](https://camel.apache.org/support.html).
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
+We also love contributors,
+so [get involved](https://camel.apache.org/contributing.html) :-)
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
+The Camel riders!
diff --git a/examples/camel-example-servlet-httpregistry-blueprint/README.adoc b/examples/camel-example-servlet-httpregistry-blueprint/README.adoc
new file mode 100644
index 0000000..fe90290
--- /dev/null
+++ b/examples/camel-example-servlet-httpregistry-blueprint/README.adoc
@@ -0,0 +1,72 @@
+== Camel Servlet HttpRegistry Blueprint example
+
+=== Introduction
+
+This example shows how to use `+camel-servlet+`
+https://github.com/apache/camel/blob/master/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/HttpRegistry.java[HttpRegistry]
+so that a `+CamelServlet+` can serve multiple OSGi bundles.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+To install Apache Camel in Karaf you type in the shell (we use version `${project.version}`):
+
+....
+feature:repo-add camel ${project.version}
+feature:install camel
+....
+
+First you need to install the following features in Karaf/ServiceMix
+with:
+
+....
+feature:install camel-servlet
+feature:install war
+....
+
+Then you can install the example:
+
+....
+install -s mvn:org.apache.camel.example/camel-example-servlet-httpregistry-blueprint/${project.version}
+....
+
+And you can see the application running by tailing the logs
+
+....
+log:tail
+....
+
+And you can use ctrl+c to stop tailing the log.
+
+There is a servlet that supports the following operation:
+
+* POST /camel/services/hello - to echo the request body
+
+From the command shell you can use `+curl+` to post a request to the
+servlet as shown below:
+
+....
+curl -X POST -H "Content-Type: text/plain" -d "Hello World" http://localhost:8181/camel/services/hello
+....
+
+=== Configuration
+
+This example is implemented in XML DSL in the
+`src/main/resources/OSGI-INF/blueprint/camel-context.xml` file.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-servlet-httpregistry-blueprint/README.md b/examples/camel-example-servlet-httpregistry-blueprint/README.md
deleted file mode 100644
index 7746755..0000000
--- a/examples/camel-example-servlet-httpregistry-blueprint/README.md
+++ /dev/null
@@ -1,55 +0,0 @@
-# Camel Servlet HttpRegistry Blueprint example
-
-### Introduction
-
-This example shows how to use `camel-servlet` [HttpRegistry](https://github.com/apache/camel/blob/master/components/camel-servlet/src/main/java/org/apache/camel/component/servlet/HttpRegistry.java) so that a `CamelServlet` can serve multiple OSGi bundles.
-
-### Build
-
-You will need to compile this example first:
-
- mvn install
-
-### Run
-
-To install Apache Camel in Karaf you type in the shell (we use version ${project.version}):
-
- feature:repo-add camel ${project.version}
- feature:install camel
-
-First you need to install the following features in Karaf/ServiceMix with:
-
- feature:install camel-servlet
- feature:install war
-
-Then you can install the example:
-
- install -s mvn:org.apache.camel.example/camel-example-servlet-httpregistry-blueprint/${project.version}
-
-And you can see the application running by tailing the logs
-
- log:tail
-
-And you can use <kbd>ctrl</kbd>+<kbd>c</kbd> to stop tailing the log.
-
-There is a servlet that supports the following operation:
-
-- POST /camel/services/hello - to echo the request body
-
-From the command shell you can use `curl` to post a request to the servlet as shown below:
-
- curl -X POST -H "Content-Type: text/plain" -d "Hello World" http://localhost:8181/camel/services/hello
-
-
-### Configuration
-
-This example is implemented in XML DSL in the [src/main/resources/OSGI-INF/blueprint/camel-context.xml](src/main/resources/OSGI-INF/blueprint/camel-context.xml) file.
-
-
-### Forum, Help, etc
-
-If you hit problems please let us know on the Camel Forums:
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-servlet-rest-blueprint/README.adoc b/examples/camel-example-servlet-rest-blueprint/README.adoc
new file mode 100644
index 0000000..1ba42b1
--- /dev/null
+++ b/examples/camel-example-servlet-rest-blueprint/README.adoc
@@ -0,0 +1,87 @@
+== Camel Servlet REST and OSGi Blueprint example
+
+=== Introduction
+
+This example shows how to use Servlet REST to define REST endpoints in
+Camel routes using the Rest DSL
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+To install Apache Camel in Karaf you type in the shell (we use version
+$\{project.version}):
+
+....
+feature:repo-add camel ${project.version}
+feature:install camel
+....
+
+First you need to install the following features in Karaf/ServiceMix
+with:
+
+....
+feature:install camel-servlet
+feature:install camel-jackson
+feature:install war
+....
+
+Then you can install the Camel example:
+
+....
+install -s mvn:org.apache.camel.example/camel-example-servlet-rest-blueprint/${project.version}
+....
+
+And you can see the application running by tailing the logs
+
+....
+log:tail
+....
+
+And you can use ctrl+c to stop tailing the log.
+
+There is a user REST service that supports the following operations
+
+* GET /user/\{id} - to view a user with the given id
+* GET /user/final - to view all users
+* PUT /user - to update/create an user
+
+The view operations are HTTP GET, and update is using HTTP PUT.
+
+From a web browser you can access the first two services using the
+following links
+
+....
+ http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/123 - to view the user with id 123
+ http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/findAll - to list all users
+....
+
+From the command shell you can use curl to access the service as shown
+below:
+
+....
+curl -X GET -H "Accept: application/json" http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/123
+curl -X GET -H "Accept: application/json" http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/findAll
+curl -X PUT -d "{ \"id\": 666, \"name\": \"The devil\"}" -H "Accept: application/json" http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user
+....
+
+=== Configuration
+
+This example is implemented in XML DSL in the
+`+src/main/resources/OSGI-INF/blueprint/camel.xml+` file.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-servlet-rest-blueprint/README.md b/examples/camel-example-servlet-rest-blueprint/README.md
deleted file mode 100644
index b3cc147..0000000
--- a/examples/camel-example-servlet-rest-blueprint/README.md
+++ /dev/null
@@ -1,65 +0,0 @@
-# Camel Servlet REST and OSGi Blueprint example
-
-### Introduction
-This example shows how to use Servlet REST to define REST endpoints in Camel routes using the Rest DSL
-
-
-### Build
-You will need to compile this example first:
-
- mvn install
-
-
-### Run
-To install Apache Camel in Karaf you type in the shell (we use version ${project.version}):
-
- feature:repo-add camel ${project.version}
- feature:install camel
-
-First you need to install the following features in Karaf/ServiceMix with:
-
- feature:install camel-servlet
- feature:install camel-jackson
- feature:install war
-
-Then you can install the Camel example:
-
- install -s mvn:org.apache.camel.example/camel-example-servlet-rest-blueprint/${project.version}
-
-And you can see the application running by tailing the logs
-
- log:tail
-
-And you can use <kbd>ctrl</kbd>+<kbd>c</kbd> to stop tailing the log.
-
-There is a user REST service that supports the following operations
-
- - GET /user/{id} - to view a user with the given id
- - GET /user/final - to view all users
- - PUT /user - to update/create an user
-
-The view operations are HTTP GET, and update is using HTTP PUT.
-
-From a web browser you can access the first two services using the following links
-
- http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/123 - to view the user with id 123
- http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/findAll - to list all users
-
-From the command shell you can use curl to access the service as shown below:
-
- curl -X GET -H "Accept: application/json" http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/123
- curl -X GET -H "Accept: application/json" http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user/findAll
- curl -X PUT -d "{ \"id\": 666, \"name\": \"The devil\"}" -H "Accept: application/json" http://localhost:8181/camel-example-servlet-rest-blueprint/rest/user
-
-
-### Configuration
-This example is implemented in XML DSL in the `src/main/resources/OSGI-INF/blueprint/camel.xml` file.
-
-
-### Forum, Help, etc
-
-If you hit problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-servlet-tomcat/README.adoc b/examples/camel-example-servlet-tomcat/README.adoc
new file mode 100644
index 0000000..e740aa8
--- /dev/null
+++ b/examples/camel-example-servlet-tomcat/README.adoc
@@ -0,0 +1,44 @@
+== Camel Servlet and Apache Tomcat example
+
+=== Introduction
+
+An example which shows how to use the Camel Servlet with Apache Tomcat.
+
+=== Build
+
+You will need to package this example first:
+
+....
+mvn package
+....
+
+=== Run
+
+To run the example deploy it in Apache Tomcat by copying the `+.war+` to
+the deploy folder of Apache Tomcat.
+
+And then hit this url from a webbrowser which has further instructions
+
+....
+http://localhost:8080/camel-example-servlet-tomcat
+....
+
+http://localhost:8080/camel-example-servlet-tomcat
+
+The servlet is located at
+
+....
+http://localhost:8080/camel-example-servlet-tomcat/camel/hello
+....
+
+http://localhost:8080/camel-example-servlet-tomcat/camel/hello
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-servlet-tomcat/README.md b/examples/camel-example-servlet-tomcat/README.md
deleted file mode 100644
index 00f469e..0000000
--- a/examples/camel-example-servlet-tomcat/README.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Camel Servlet and Apache Tomcat example
-
-
-### Introduction
-An example which shows how to use the Camel Servlet with Apache Tomcat.
-
-### Build
-You will need to package this example first:
-
- mvn package
-
-### Run
-
-To run the example deploy it in Apache Tomcat by copying the `.war` to the
-deploy folder of Apache Tomcat.
-
-And then hit this url from a webbrowser which has further
-instructions
-
- http://localhost:8080/camel-example-servlet-tomcat
-<http://localhost:8080/camel-example-servlet-tomcat>
-
-The servlet is located at
-
- http://localhost:8080/camel-example-servlet-tomcat/camel/hello
-<http://localhost:8080/camel-example-servlet-tomcat/camel/hello>
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
diff --git a/examples/camel-example-spark-rest/README.adoc b/examples/camel-example-spark-rest/README.adoc
new file mode 100644
index 0000000..b4c35f4
--- /dev/null
+++ b/examples/camel-example-spark-rest/README.adoc
@@ -0,0 +1,78 @@
+== Camel Spark REST
+
+=== Introduction
+
+This example shows how to use Spark REST to define REST endpoints in
+Camel routes using the Rest DSL Spark requires Java 8, so you will need
+to use Java 8.
+
+=== Introduction
+
+This is an example that uses the rest-dsl to define a rest services
+which provides three operations
+
+* GET user/view/{id} - View user by id
+* GET user/list - List all users
+* PUT user/update - Updates or create a user
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn camel:run
+....
+
+The rest service can be accessed from the following url
+
+....
+curl http://localhost:8080/user
+....
+
+http://localhost:8080/user
+
+For example to get a user with id 123
+
+....
+curl http://localhost:8080/user/view/123
+....
+
+http://localhost:8080/user/view/123
+
+And to list all the users
+
+....
+curl http://localhost:8080/user/list
+....
+
+http://localhost:8080/user/view/list
+
+The rest services provides Swagger API which can be accessed from the
+following url in json or yaml format:
+
+....
+curl http://localhost:8080/api-doc/swagger.json
+curl http://localhost:8080/api-doc/swagger.yaml
+....
+
+http://localhost:8080/api-doc/swagger.json
+
+To stop the example hit ctrl+c
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spark-rest/README.md b/examples/camel-example-spark-rest/README.md
deleted file mode 100644
index 4abd1c3..0000000
--- a/examples/camel-example-spark-rest/README.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Camel Spark REST
-
-### Introduction
-This example shows how to use Spark REST to define REST endpoints in Camel routes using the Rest DSL
-Spark requires Java 8, so you will need to use Java 8.
-
-
-### Introduction
-This is an example that uses the rest-dsl to define a rest services which provides three operations
-
-- GET user/view/{id} - View user by id
-- GET user/list - List all users
-- PUT user/update - Updates or create a user
-
-### Build
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-To run the example type
-
- mvn camel:run
-
-The rest service can be accessed from the following url
-
- curl http://localhost:8080/user
-
-<http://localhost:8080/user>
-
-For example to get a user with id 123
-
- curl http://localhost:8080/user/view/123
-
-<http://localhost:8080/user/view/123>
-
-And to list all the users
-
- curl http://localhost:8080/user/list
-
-<http://localhost:8080/user/view/list>
-
-The rest services provides Swagger API which can be accessed
-from the following url in json or yaml format:
-
- curl http://localhost:8080/api-doc/swagger.json
- curl http://localhost:8080/api-doc/swagger.yaml
-
-<http://localhost:8080/api-doc/swagger.json>
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
-
-### Forum, Help, etc
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-The Camel riders!
diff --git a/examples/camel-example-splunk/README.adoc b/examples/camel-example-splunk/README.adoc
new file mode 100644
index 0000000..66bd74c
--- /dev/null
+++ b/examples/camel-example-splunk/README.adoc
@@ -0,0 +1,65 @@
+== Camel Splunk example
+
+=== Introduction
+
+An example which shows how to integrate Camel with Splunk.
+
+This example requires that an Splunk Server is up and running. (For this
+example, sample data provide by Splunk was used. Steps for loading this
+data into splunk are documented here:
+http://docs.splunk.com/Documentation/Splunk/latest/SearchTutorial/GetthetutorialdataintoSplunk)
+
+This project consists of the following examples: -Random search query on
+Splunk -Saved search query on Splunk -Publish an event to Splunk
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the random search client you type:
+
+....
+mvn compile exec:java -Psearch-client
+....
+
+… and response data will be printed on the console.
+
+To run the saved search client you type:
+
+....
+mvn compile exec:java -Psaved-search-client
+....
+
+… and response data will be printed on the console.
+
+To run the saved search client you type:
+
+....
+mvn compile exec:java -Ppublish-event-client
+....
+
+… and logs will be printed on the console.
+
+=== Configuration
+
+You can configure the details of the Splunk server in the file:
+`+src/main/resources/application.properties+`
+
+You can enable verbose logging by adjusting the
+`+src/main/resources/log4j.properties+` file as documented in the file.
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-splunk/README.md b/examples/camel-example-splunk/README.md
deleted file mode 100644
index 6ffaeca..0000000
--- a/examples/camel-example-splunk/README.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# Camel Splunk example
-
-### Introduction
-An example which shows how to integrate Camel with Splunk.
-
-This example requires that an Splunk Server is up and running.
-(For this example, sample data provide by Splunk was used. Steps
-for loading this data into splunk are documented here:
- <http://docs.splunk.com/Documentation/Splunk/latest/SearchTutorial/GetthetutorialdataintoSplunk>)
-
-
-This project consists of the following examples:
- -Random search query on Splunk
- -Saved search query on Splunk
- -Publish an event to Splunk
-
-
-### Build
-
-You will need to compile this example first:
-
- mvn compile
-
-### Run
-
-To run the random search client you type:
-
- mvn compile exec:java -Psearch-client
-
-... and response data will be printed on the console.
-
-To run the saved search client you type:
-
- mvn compile exec:java -Psaved-search-client
-
-... and response data will be printed on the console.
-
-To run the saved search client you type:
-
- mvn compile exec:java -Ppublish-event-client
-
-... and logs will be printed on the console.
-
-
-### Configuration
-
-You can configure the details of the Splunk server in the file:
- `src/main/resources/application.properties`
-
-You can enable verbose logging by adjusting the `src/main/resources/log4j.properties`
- file as documented in the file.
-
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-
-The Camel riders!
diff --git a/examples/camel-example-spring-boot-activemq/readme.adoc b/examples/camel-example-spring-boot-activemq/readme.adoc
index 8ae2186..d16d1ba 100644
--- a/examples/camel-example-spring-boot-activemq/readme.adoc
+++ b/examples/camel-example-spring-boot-activemq/readme.adoc
@@ -1,10 +1,10 @@
-# Camel Example Spring Boot and ActiveMQ
+== Camel Example Spring Boot and ActiveMQ
This example shows how to work with a simple Apache Camel application using Spring Boot and Apache ActiveMQ.
-= Preparing ActiveMQ brokers
+=== Preparing ActiveMQ brokers
-From Apache ActiveMQ you can download the broker as a .zip or .tar.gz file.
+From Apache ActiveMQ you can download the broker as a `.zip` or `.tar.gz` file.
Unzip/tar the archive, and start a terminal.
@@ -14,17 +14,23 @@ Change directory to the unzipped directory and start the broker.
Which runs the broker in the foreground and logs to the console.
-== How to run the example
+=== How to run the example
You can run this example using
mvn spring-boot:run
-== Using Camel components
+=== Using Camel components
Apache Camel provides 200+ components which you can use to integrate and route messages between many systems
and data formats. To use any of these Camel components, add the component as a dependency to your project.
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-amqp/readme.adoc b/examples/camel-example-spring-boot-amqp/readme.adoc
index 519ac49..50fba31 100644
--- a/examples/camel-example-spring-boot-amqp/readme.adoc
+++ b/examples/camel-example-spring-boot-amqp/readme.adoc
@@ -1,10 +1,10 @@
-# Camel Example Spring Boot and ActiveMQ AMQP
+== Camel Example Spring Boot and ActiveMQ AMQP
This example shows how to work with a simple Apache Camel application using Spring Boot and Apache ActiveMQ.
-= Preparing ActiveMQ brokers
+=== Preparing ActiveMQ brokers
-From Apache ActiveMQ you can download the broker as a .zip or .tar.gz file.
+From Apache ActiveMQ you can download the broker as a `.zip` or `.tar.gz` file.
Unzip/tar the archive, and start a terminal.
@@ -14,17 +14,23 @@ Change directory to the unzipped directory and start the broker.
Which runs the broker in the foreground and logs to the console.
-== How to run the example
+=== How to run the example
You can run this example using
mvn spring-boot:run
-== Using Camel components
+=== Using Camel components
Apache Camel provides 200+ components which you can use to integrate and route messages between many systems
and data formats. To use any of these Camel components, add the component as a dependency to your project.
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-clustered-route-controller/readme.adoc b/examples/camel-example-spring-boot-clustered-route-controller/readme.adoc
index 1b86577..aa3471f 100644
--- a/examples/camel-example-spring-boot-clustered-route-controller/readme.adoc
+++ b/examples/camel-example-spring-boot-clustered-route-controller/readme.adoc
@@ -1,25 +1,30 @@
-# Camel Clustered Route Controller Example Spring Boot
+== Camel Clustered Route Controller Example Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot and a Clustered Route Controller.
-= How to run
+=== How to run
1. build the project:
-+
mvn clean package
2. in a shell, run the cluster node
-+
+
mvn -pl cluster-bootstrap spring-boot:run
3. in a separate shell, run the first camel node
-+
+
mvn -pl cluster-node spring-boot:run
4. in a separate shell, run the second camel node
-+
+
mvn -pl cluster-node spring-boot:run
-== More information
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-geocoder/README.adoc b/examples/camel-example-spring-boot-geocoder/README.adoc
index 62dce55..2ac68e0 100644
--- a/examples/camel-example-spring-boot-geocoder/README.adoc
+++ b/examples/camel-example-spring-boot-geocoder/README.adoc
@@ -1,6 +1,6 @@
-# Spring Boot Example with Camel REST DSL, Geocoder and Swagger
+== Spring Boot Example with Camel REST DSL, Geocoder and Swagger
-= Introduction
+=== Introduction
This example illustrates how to use https://projects.spring.io/spring-boot/[Spring Boot] with http://camel.apache.org[Camel]. It provides a simple REST service that is created with http://camel.apache.org/rest-dsl.html[Camel REST DSL], using the http://camel.apache.org/geocoder.html[Geocoder component] and documented with http://swagger.io[Swagger].
@@ -8,13 +8,13 @@ The project uses the `camel-spring-boot-starter` and `camel-geocoder-starter` de
The project was based on it's `camel-example-spring-boot-rest-swagger` sibling.
-== Build
+=== Build
You can build this example using:
$ mvn package
-== Run
+=== Run
You can run this example using:
@@ -106,10 +106,12 @@ The Swagger documentation is located at: http://localhost:8080/camel/api-doc and
The Spring Boot application can be stopped pressing `[CTRL]`+`[C]` in the shell.
-== Help
+=== Help and contributions
-If you hit any problems please let us know on the http://camel.apache.org/discussion-forums.html[Camel Forums].
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-spring-boot-grpc/README.adoc b/examples/camel-example-spring-boot-grpc/README.adoc
index 0748ed9..2cf4861 100644
--- a/examples/camel-example-spring-boot-grpc/README.adoc
+++ b/examples/camel-example-spring-boot-grpc/README.adoc
@@ -1,10 +1,10 @@
-# Spring Boot Example with gRPC
+== Spring Boot Example with gRPC
-= Introduction
+=== Introduction
This example demonstrates how you can use Camel-gRPC Starter component. The example is composed of a standalone gRPC server and a Camel Spring-boot gRPC route acting as client.
-== Server
+=== Server
You can build the server under the directory hello-camel-grpc-server with:
@@ -22,7 +22,7 @@ Aug 08, 2017 8:00:00 AM org.apache.camel.examples.grpc.HelloCamelServer start
INFO: Server started. I'm listening on 50051
----
-== Run the client
+=== Run the client
You can build the client example under the directory hello-camel-grpc-client with:
@@ -57,10 +57,12 @@ And you should see this output in the console.
----
-== Help
+=== Help and contributions
-If you hit any problems please let us know on the http://camel.apache.org/discussion-forums.html[Camel Forums].
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-The Camel riders!
+The Camel riders!
\ No newline at end of file
diff --git a/examples/camel-example-spring-boot-health-checks/readme.adoc b/examples/camel-example-spring-boot-health-checks/readme.adoc
index 6a1a915..2641562 100644
--- a/examples/camel-example-spring-boot-health-checks/readme.adoc
+++ b/examples/camel-example-spring-boot-health-checks/readme.adoc
@@ -1,17 +1,17 @@
-# Camel Health Checks and Spring Boot
+== Camel Health Checks and Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot.
NOTE: Some of the routes fail intentionally to have health check monitor their failures
-= How to run
+=== How to run
* mvn clean package
* service/src/main/bash/consul-run-linux.sh
* mvn -pl service spring-boot:run
* mvn -pl application spring-boot:run
-== How to play with the example
+=== How to play with the example
You can interact with the example using curl or httpie
@@ -199,7 +199,7 @@ $ http -b GET localhost:8080/health
}
----
-== Using the HealthCheckService
+=== Using the HealthCheckService
The HealthCheckService can be enabled by setting the property `camel.health.check.service.enabled` to `true`. Once done every call to the Camel health check endpoint as well as the SpringBoot one will return the last known response or an error if the requested check has not yet been invoked.
@@ -210,6 +210,12 @@ To force the service to refresh a check, you can use:
$ http -b GET localhost:8080/camel/health/check/{id}/invoke
----
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-infinispan/README.adoc b/examples/camel-example-spring-boot-infinispan/README.adoc
index a93b5ce..cbc1aec 100644
--- a/examples/camel-example-spring-boot-infinispan/README.adoc
+++ b/examples/camel-example-spring-boot-infinispan/README.adoc
@@ -1,17 +1,17 @@
-# Spring Boot Example with Infinispan
+== Spring Boot Example with Infinispan
-= Introduction
+=== Introduction
This example demonstrates how you can use Camel-Infinispan Starter component. The example is really simple: put a key/value pair in a remote cache and get the same key.
You'll need a running Infinispan server to run this example.
-== Build
+=== Build
You can build this example using:
$ mvn package
-== Run
+=== Run
You can run this example using:
@@ -19,10 +19,12 @@ You can run this example using:
And you should see output in the console.
-== Help
+=== Help and contributions
-If you hit any problems please let us know on the http://camel.apache.org/discussion-forums.html[Camel Forums].
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-spring-boot-master/readme.adoc b/examples/camel-example-spring-boot-master/readme.adoc
index f45eb6a..60f44d8 100644
--- a/examples/camel-example-spring-boot-master/readme.adoc
+++ b/examples/camel-example-spring-boot-master/readme.adoc
@@ -1,21 +1,27 @@
-# Camel Clustered Route Controller Example Spring Boot
+== Camel Clustered Route Controller Example Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot and a Master component.
-= How to run
+=== How to run
1. build the project:
-+
+
mvn clean package
2. in a separate shell, run the first camel node
-+
+
mvn spring-boot:run
3. in a separate shell, run the second camel node
-+
+
mvn spring-boot:run
-== More information
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-metrics/README.adoc b/examples/camel-example-spring-boot-metrics/README.adoc
new file mode 100644
index 0000000..1763342
--- /dev/null
+++ b/examples/camel-example-spring-boot-metrics/README.adoc
@@ -0,0 +1,59 @@
+== Camel Spring Boot Metrics Example
+
+=== Introduction
+
+This example sends Camel route metrics to Graphite from a Spring Boot
+app.
+
+Please read *Configuration* first
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn install
+....
+
+=== Run
+
+To run the example type
+
+....
+java -jar target/camel-example-spring-boot-metrics.jar
+....
+
+You will see logging from the ``Fast'' and ``Slow'' routes, and metrics
+will be sent to Graphite (or nc) every 5 seconds.
+
+=== Configuration
+
+Spring Boot auto-configures the `+com.codahale.metrics.MetricRegistry+`.
+See code comments in `+Application.java+` for further details.
+
+If you already have a Graphite server, make sure that UDP is enabled
+(set `+ENABLE_UDP_LISTENER = True+` in carbon.conf).
+
+If Graphite is not on your local machine, replace `+localhost+` in
+`+Application.java+` with the hostname or IP address of your Graphite
+server.
+
+If you want to use TCP instead of UDP, use
+`+com.codahale.metrics.graphite.Graphite+` instead of
+`+com.codahale.metrics.graphite.GraphiteUDP+`, as shown here:
+http://metrics.dropwizard.io/3.1.0/manual/graphite/
+
+If you can't be bothered to set up a Graphite server right now, you can
+simulate it by running `+nc -ul 2003+` on Linux. If you don't have
+`+nc+`, use `+yum search netcat+` to find a suitable package to install
+(e.g. nmap-ncat.x86_64).
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-metrics/README.md b/examples/camel-example-spring-boot-metrics/README.md
deleted file mode 100644
index d3534da..0000000
--- a/examples/camel-example-spring-boot-metrics/README.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# Camel Spring Boot Metrics Example
-
-
-### Introduction
-This example sends Camel route metrics to Graphite from a Spring Boot app.
-
-Please read **Configuration** first
-
-### Build
-You will need to compile this example first:
-
- mvn install
-
-### Run
-To run the example type
-
- java -jar target/camel-example-spring-boot-metrics.jar
-
-
-
-You will see logging from the "Fast" and "Slow" routes, and metrics will be sent to Graphite (or nc) every 5 seconds.
-
-### Configuration
-Spring Boot auto-configures the `com.codahale.metrics.MetricRegistry`. See code comments in `Application.java` for further details.
-
-If you already have a Graphite server, make sure that UDP is enabled (set `ENABLE_UDP_LISTENER = True` in carbon.conf).
-
-If Graphite is not on your local machine, replace `localhost` in `Application.java` with the hostname or IP address of your Graphite server.
-
-If you want to use TCP instead of UDP, use `com.codahale.metrics.graphite.Graphite` instead of `com.codahale.metrics.graphite.GraphiteUDP`,
-as shown here: http://metrics.dropwizard.io/3.1.0/manual/graphite/
-
-If you can't be bothered to set up a Graphite server right now, you can simulate it by running `nc -ul 2003` on Linux.
-If you don't have `nc`, use `yum search netcat` to find a suitable package to install (e.g. nmap-ncat.x86_64).
-
-### Forum, Help, etc
-
-If you hit an problems please let us know on the Camel Forums
- <http://camel.apache.org/discussion-forums.html>
-
-Please help us make Apache Camel better - we appreciate any feedback you may
-have. Enjoy!
-
-
-
-The Camel riders!
diff --git a/examples/camel-example-spring-boot-pojo/README.adoc b/examples/camel-example-spring-boot-pojo/README.adoc
index 6771536a..efe3a7e 100644
--- a/examples/camel-example-spring-boot-pojo/README.adoc
+++ b/examples/camel-example-spring-boot-pojo/README.adoc
@@ -1,19 +1,19 @@
-# Spring Boot Example with POJO Routing
+== Spring Boot Example with POJO Routing
-= Introduction
+=== Introduction
This example demonstrates how you can use POJO Royting with Camel's `@Consume` and `@Produce` annotations
on your Java beans. The example will generate a series of random numbers that is routed to either a low
or high method call. The method then constructs a new message that is routed to another POJO that is
hidden by an interface.
-== Build
+=== Build
You can build this example using:
$ mvn package
-== Run
+=== Run
You can run this example using:
@@ -21,10 +21,12 @@ You can run this example using:
And you should see output in the console with high and low numbers. The example will self stop after one minute.
-== Help
+=== Help and contributions
-If you hit any problems please let us know on the http://camel.apache.org/discussion-forums.html[Camel Forums].
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-spring-boot-rest-jpa/README.md b/examples/camel-example-spring-boot-rest-jpa/README.adoc
similarity index 71%
rename from examples/camel-example-spring-boot-rest-jpa/README.md
rename to examples/camel-example-spring-boot-rest-jpa/README.adoc
index 475a5e7..df028d7 100644
--- a/examples/camel-example-spring-boot-rest-jpa/README.md
+++ b/examples/camel-example-spring-boot-rest-jpa/README.adoc
@@ -1,46 +1,52 @@
-# Spring Boot REST DSL / JPA Example
+== Spring Boot REST DSL / JPA Example
-### Introduction
+=== Introduction
-This example demonstrates how to use JPA and Spring Data along with Camel's REST DSL
-to expose a RESTful API that performs CRUD operations on a database.
+This example demonstrates how to use JPA and Spring Data along with
+Camel’s REST DSL to expose a RESTful API that performs CRUD operations
+on a database.
It generates orders for books referenced in database at a regular pace.
-Orders are processed asynchronously by another Camel route. Books available
-in database as well as the status of the generated orders can be retrieved via
-the REST API.
+Orders are processed asynchronously by another Camel route. Books
+available in database as well as the status of the generated orders can
+be retrieved via the REST API.
-It relies on Swagger to expose the API documentation of the REST service.
+It relies on Swagger to expose the API documentation of the REST
+service.
-### Build
+=== Build
You can build this example using:
-```sh
+[source,sh]
+----
$ mvn package
-```
+----
-### Run
+=== Run
You can run this example with Maven using:
-```sh
+[source,sh]
+----
$ mvn spring-boot:run -Dspring.profiles.active=dev
-```
+----
Alternatively, you can also run this example using the executable JAR:
-```sh
+[source,sh]
+----
$ java -jar -Dspring.profiles.active=dev target/camel-example-spring-boot-rest-jpa-${project.version}.jar
-```
+----
This uses an embedded in-memory HSQLDB database. You can use the default
-Spring Boot profile in case you have a MySQL server available for you to test.
+Spring Boot profile in case you have a MySQL server available for you to
+test.
When the Camel application runs, you should see the following messages
being logged to the console, e.g.:
-```
+....
2016-09-02 09:54:29.702 INFO 27253 --- [mer://new-order] generate-order : Inserted new order 1
2016-09-02 09:54:31.597 INFO 27253 --- [mer://new-order] generate-order : Inserted new order 2
2016-09-02 09:54:33.596 INFO 27253 --- [mer://new-order] generate-order : Inserted new order 3
@@ -53,26 +59,28 @@ being logged to the console, e.g.:
2016-09-02 09:54:39.668 INFO 27253 --- [rts.camel.Order] process-order : Processed order #id 4 with 7 copies of the «Camel in Action» book
2016-09-02 09:54:39.671 INFO 27253 --- [rts.camel.Order] process-order : Processed order #id 5 with 1 copies of the «ActiveMQ in Action» book
2016-09-02 09:54:39.674 INFO 27253 --- [rts.camel.Order] process-order : Processed order #id 6 with 4 copies of the «Camel in Action» book
-```
+....
You can then access the REST API directly from your Web browser, e.g.:
-- <http://localhost:8080/camel-rest-jpa/books>
-- <http://localhost:8080/camel-rest-jpa/books/order/1>
+* http://localhost:8080/camel-rest-jpa/books
+* http://localhost:8080/camel-rest-jpa/books/order/1
-The Camel application can be stopped pressing <kbd>ctrl</kbd>+<kbd>c</kbd> in the shell.
+The Camel application can be stopped pressing ctrl+c in the shell.
-### Swagger API
+=== Swagger API
-The example provides API documentation of the service using Swagger using
-the _context-path_ `camel-rest-jpa/api-doc`. You can access the API documentation
-from your Web browser at <http://localhost:8080/camel-rest-jpa/api-doc>.
+The example provides API documentation of the service using Swagger
+using the _context-path_ `+camel-rest-jpa/api-doc+`. You can access the
+API documentation from your Web browser at
+http://localhost:8080/camel-rest-jpa/api-doc.
-### Forum, Help, etc
+=== Help and contributions
-If you hit an problems please let us know on the Camel Forums
-<http://camel.apache.org/discussion-forums.html>
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-The Camel riders!
\ No newline at end of file
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-rest-swagger/README.adoc b/examples/camel-example-spring-boot-rest-swagger/README.adoc
index 5df4553..b15697b 100644
--- a/examples/camel-example-spring-boot-rest-swagger/README.adoc
+++ b/examples/camel-example-spring-boot-rest-swagger/README.adoc
@@ -1,6 +1,6 @@
-= Spring Boot Example with Camel REST DSL and Swagger
+== Spring Boot Example with Camel REST DSL and Swagger
-== Introduction
+=== Introduction
This example illustrates how to use https://projects.spring.io/spring-boot/[Spring Boot] with http://camel.apache.org[Camel]. It provides a simple REST service that is created with http://camel.apache.org/rest-dsl.html[Camel REST DSL] and documented with http://swagger.io[Swagger].
@@ -8,13 +8,13 @@ The project uses the `camel-spring-boot-starter` dependency, a Spring Boot start
The project also uses `camel-servlet` component as the HTTP transport component for Camel REST DSL.
-== Build
+=== Build
You can build this example using:
$ mvn package
-== Run
+=== Run
You can run this example using:
@@ -75,10 +75,12 @@ $ curl http://localhost:8080/api/api-doc
The Spring Boot application can be stopped pressing `[CTRL] + [C]` in the shell.
-== Help
+=== Help and contributions
-If you hit any problems please let us know on the http://camel.apache.org/discussion-forums.html[Camel Forums].
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-Please help us make Apache Camel better - we appreciate any feedback you may have. Enjoy!
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
The Camel riders!
diff --git a/examples/camel-example-spring-boot-servicecall/README.adoc b/examples/camel-example-spring-boot-servicecall/README.adoc
index eb77dba..d97ab80 100644
--- a/examples/camel-example-spring-boot-servicecall/README.adoc
+++ b/examples/camel-example-spring-boot-servicecall/README.adoc
@@ -1,4 +1,4 @@
-# Spring Boot and ServiceCall EIP Example
+== Spring Boot and ServiceCall EIP Example
This example show how to use Camel with ServiceCall EIP with spring-boot and consul.
@@ -7,7 +7,7 @@ This example includes two maven modules:
- services that exposes a number of services
- consumer that consumes services
-= Configuration
+=== Configuration
The consumer is configured in the src/main/resources/application.properties in which we blacklist some services for being discovered and we add some additional services not managed by consul
@@ -17,14 +17,13 @@ The consumer is configured in the src/main/resources/application.properties in w
# Configure additional services
camel.cloud.service-discovery.services[service-2] = localhost:9021,localhost:9022,localhost:9023
-
-== Build
+=== Build
You can build this example using
mvn compile
-== Run the example
+=== Run the example
Using multiple shells:
@@ -49,7 +48,7 @@ Using multiple shells:
$ cd consumer
$ mvn spring-boot:run
-== Test the example:
+=== Test the example:
In a new shell:
@@ -60,7 +59,7 @@ In a new shell:
If you keep calling the http endpoint you'll notice they are consumed using a round robin policy and that one of the services registered in consul is not taken into account according to the blacklist.
-== Web console
+=== Web console
You can open the Consul web console
@@ -68,8 +67,12 @@ You can open the Consul web console
Where you can find information about the services and its state.
+=== Help and contributions
-== More information
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-supervising-route-controller/readme.adoc b/examples/camel-example-spring-boot-supervising-route-controller/readme.adoc
index 48777f1..6d70815 100644
--- a/examples/camel-example-spring-boot-supervising-route-controller/readme.adoc
+++ b/examples/camel-example-spring-boot-supervising-route-controller/readme.adoc
@@ -1,8 +1,8 @@
-# Camel Supervising Route Controller Example Spring Boot
+== Camel Supervising Route Controller Example Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot and a Supervising Route Controller.
-= How to run
+=== How to run
You can run this example using
@@ -11,41 +11,46 @@ You can run this example using
Beside JMX you can use Spring Boot Endpoints to interact with the routes:
* To get info about the routes
-+
+
[source]
----
curl -XGET -s http://localhost:8080/actuator/camelroutes
----
* To get details about a route
-+
+
[source]
----
curl -XGET -s http://localhost:8080/actuator/camelroutes/{id}/detail
----
* To get info about a route
-+
+
[source]
----
curl -XGET -s http://localhost:8080/actuator/camelroutes/{id}/info
----
* To stop a route
-+
+
[source]
----
curl -XPOST -H "Content-Type: application/json" -s http://localhost:8080/actuator/camelroutes/{id}/stop
----
* To start a route
-+
+
[source]
----
curl -XPOST -H "Content-Type: application/json" -s http://localhost:8080/actuator/camelroutes/{id}/start
----
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-== More information
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+The Camel riders!
diff --git a/examples/camel-example-spring-boot-xml/readme.adoc b/examples/camel-example-spring-boot-xml/readme.adoc
index 8d46507..a02346d 100644
--- a/examples/camel-example-spring-boot-xml/readme.adoc
+++ b/examples/camel-example-spring-boot-xml/readme.adoc
@@ -1,27 +1,27 @@
-# Camel Example Spring Boot
+== Camel Example Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot.
The example generates messages using timer trigger, writes them to standard output.
-= Camel routes
+=== Camel routes
The Camel route is located in the `SampleCamelRouter` class. In this class the route
starts from a timer, that triggers every 2nd second and calls a Spring Bean `SampleBean`
which returns a message, that is routed to a stream endpoint which writes to standard output.
-== Using Camel components
+=== Using Camel components
Apache Camel provides 200+ components which you can use to integrate and route messages between many systems
and data formats. To use any of these Camel components, add the component as a dependency to your project.
-== How to run
+=== How to run
You can run this example using
mvn spring-boot:run
-== To get info about the routes
+=== To get info about the routes
To show a summary of all the routes
@@ -35,7 +35,12 @@ To show detailed information for a specific route
curl -XGET -s http://localhost:8080/camel/routes/{id}/info
----
+=== Help and contributions
-== More information
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-boot/readme.adoc b/examples/camel-example-spring-boot/readme.adoc
index 82e59f1..741bdaf 100644
--- a/examples/camel-example-spring-boot/readme.adoc
+++ b/examples/camel-example-spring-boot/readme.adoc
@@ -1,27 +1,27 @@
-= Camel Example Spring Boot
+== Camel Example Spring Boot
This example shows how to work with a simple Apache Camel application using Spring Boot.
The example generates messages using timer trigger, writes them to standard output.
-== Camel routes
+=== Camel routes
The Camel route is located in the `MyCamelRouter` class. In this class the route
starts from a timer, that triggers every 2nd second and calls a Spring Bean `MyBean`
which returns a message, that is routed to a stream endpoint which writes to standard output.
-== Using Camel components
+=== Using Camel components
Apache Camel provides 200+ components which you can use to integrate and route messages between many systems
and data formats. To use any of these Camel components, add the component as a dependency to your project.
-== How to run
+=== How to run
You can run this example using
mvn spring-boot:run
-== To get health check
+=== To get health check
To show a summary of spring boot health check
@@ -29,7 +29,7 @@ To show a summary of spring boot health check
curl -XGET -s http://localhost:8080/actuator/health
----
-== To get info about the routes
+=== To get info about the routes
To show a summary of all the routes
@@ -43,10 +43,15 @@ To show detailed information for a specific route
curl -XGET -s http://localhost:8080/actuator/camelroutes/{id}/detail
----
+=== Help and contributions
-== More information
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-cloud-servicecall/README.adoc b/examples/camel-example-spring-cloud-servicecall/README.adoc
index 9a94615..b1919d9 100644
--- a/examples/camel-example-spring-cloud-servicecall/README.adoc
+++ b/examples/camel-example-spring-cloud-servicecall/README.adoc
@@ -1,4 +1,4 @@
-# Spring Cloud and ServiceCall EIP Example
+== Spring Cloud and ServiceCall EIP Example
This example show how to use Camel with ServiceCall EIP with spring-cloud and consul.
@@ -7,17 +7,17 @@ This example includes two maven modules:
- service that exposes a number of services
- consumer that consumes services
-= Configuration
+== Configuration
The consumer is configured in the src/main/resources/application.properties
-== Build
+=== Build
You can build this example using
mvn compile
-== Run the example
+=== Run the example
Using multiple shells:
@@ -37,7 +37,7 @@ Using multiple shells:
$ cd consumer
$ mvn spring-boot:run
-== Test the example:
+=== Test the example:
In a new shell:
@@ -56,7 +56,13 @@ You can open the Consul web console
Where you can find information about the services and its state.
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-cloud-serviceregistry/README.adoc b/examples/camel-example-spring-cloud-serviceregistry/README.adoc
index c0890fd..547613f 100644
--- a/examples/camel-example-spring-cloud-serviceregistry/README.adoc
+++ b/examples/camel-example-spring-cloud-serviceregistry/README.adoc
@@ -1,4 +1,4 @@
-# Spring Cloud and ServiceCall EIP Example
+== Spring Cloud and ServiceCall EIP Example
This example show how to use Camel with Service Registry, spring-cloud and consul.
@@ -7,17 +7,17 @@ This example includes two maven modules:
- service that exposes a number of services
- consumer that consumes services
-= Configuration
+=== Configuration
The consumer is configured in the src/main/resources/application.properties
-== Build
+=== Build
You can build this example using
mvn compile
-== Run the example
+=== Run the example
Using multiple shells:
@@ -39,12 +39,12 @@ Using multiple shells:
$ cd service
$ mvn spring-boot:run
- - start the consumer
+- start the consumer
$ cd consumer
$ mvn spring-boot:run
-== Test the example:
+=== Test the example:
In a new shell:
@@ -53,7 +53,7 @@ In a new shell:
$ curl localhost:8080/camel/serviceCall
Hi!, I'm service-1 on path: /path/to/service/2
-== Web console
+=== Web console
You can open the Consul web console
@@ -61,7 +61,12 @@ You can open the Consul web console
Where you can find information about the services and its state.
-== More information
+=== Help and contributions
-You can find more information about Apache Camel at the website: http://camel.apache.org/
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-javaconfig/README.adoc b/examples/camel-example-spring-javaconfig/README.adoc
new file mode 100644
index 0000000..27b44f9
--- /dev/null
+++ b/examples/camel-example-spring-javaconfig/README.adoc
@@ -0,0 +1,42 @@
+== Spring Java Config Example
+
+=== Introduction
+
+This example shows how to work with files and JMS, using Spring Java
+Config to boot up Camel and configure the routes.
+
+The example consumes messages from a queue and writes them to the file
+system.
+
+=== Build
+
+You will need to compile this example first:
+
+....
+mvn compile
+....
+
+=== Run
+
+To run the example type
+
+....
+mvn exec:java
+....
+
+To stop the example hit ctrl+c
+
+=== Configuration
+
+You can see the routing rules by looking at the java code in the
+`+src/main/java directory+`
+
+=== Help and contributions
+
+If you hit any problem using Camel or have some feedback, then please
+https://camel.apache.org/support.html[let us know].
+
+We also love contributors, so
+https://camel.apache.org/contributing.html[get involved] :-)
+
+The Camel riders!
diff --git a/examples/camel-example-spring-javaconfig/README.md b/examples/camel-example-spring-javaconfig/README.md
deleted file mode 100644
index 712b26a..0000000
--- a/examples/camel-example-spring-javaconfig/README.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# Spring Java Config Example
-
-### Introduction
-This example shows how to work with files and JMS, using Spring Java Config
-to boot up Camel and configure the routes.
-
-The example consumes messages from a queue and writes them to the file
-system.
-
-### Build
-You will need to compile this example first:
-
- mvn compile
-
-
-### Run
-To run the example type
-
- mvn exec:java
-
-To stop the example hit <kbd>ctrl</kbd>+<kbd>c</kbd>
-
... 3058 lines suppressed ...