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 2016/08/16 08:03:46 UTC
[22/51] [partial] camel git commit: CAMEL-9541: Use -component as
suffix for component docs.
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-gora/src/main/docs/gora-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-gora/src/main/docs/gora-component.adoc b/components/camel-gora/src/main/docs/gora-component.adoc
new file mode 100644
index 0000000..834dacc
--- /dev/null
+++ b/components/camel-gora/src/main/docs/gora-component.adoc
@@ -0,0 +1,265 @@
+[[Gora-GoraComponent]]
+Gora Component
+~~~~~~~~~~~~~~
+
+*Camel-Gora* is an http://camel.apache.org/[Apache Camel] component that
+allows you to work with NoSQL databases using the
+http://gora.apache.org/[Apache Gora] framework.
+
+*Available as of Camel 2.14*
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+[source,xml]
+---------------------------------------------------------
+<dependency>
+�<groupId>org.apache.camel</groupId>
+�<artifactId>camel-gora</artifactId>
+�<version>x.x.x</version>
+�<!-- use the same version as your Camel core version -->
+</dependency>
+---------------------------------------------------------
+
+[[Gora-ApacheGoraOverview]]
+Apache Gora Overview
+~~~~~~~~~~~~~~~~~~~~
+
+The http://gora.apache.org/[Apache Gora] open source framework provides
+an in-memory data model and persistence for big data. Gora supports
+persisting to column stores, key value stores, document stores and
+RDBMSs, and analyzing the data with extensive
+http://hadoop.apache.org/[Apache Hadoop\u2122 MapReduce] support. Gora uses
+the http://www.apache.org/licenses/LICENSE-2.0.html[Apache Software
+License v2.0] and graduated from the Apache Incubator in Janauary 2012
+to become a top-level Apache project.
+
+Apache Gora currently supports the following datastores:
+http://hbase.apache.org/[Apache HBase],
+http://cassandra.apache.org/[Apache Cassandra],
+http://accumulo.apache.org/[Apache Accumulo],
+http://aws.amazon.com/dynamodb/[Amazon DynamoDB] and SQL databases such
+as http://hsqldb.org/[hsqldb], http://www.mysql.com/[MySQL] and more.
+
+[[Gora-URIformat]]
+URI format
+~~~~~~~~~~
+
+[source,text]
+---------------------------
+gora:instanceName[?options]
+---------------------------
+
+Hbase examples with mandatory options :
+
+_XML_
+
+[source,xml]
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+_Java DSL_
+
+[source,java]
+-------------------------------------------------------------------------------------------------------------------------------------------------------------
+to("gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore")
+-------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+[[Gora-Configuratiion]]
+Configuratiion
+~~~~~~~~~~~~~~
+
+Using camel-gora needs some configuration. This mainly involve to
+configure the _AvroStore_ through the _gora.properties_ file and to
+define the relevant mappings as part of the
+_http://gora.apache.org/current/gora-core.html[gora-core]_ module.
+
+Extensive information for this configuration can be found in the apache
+http://gora.apache.org/current/index.html[gora documentation] and the
+http://gora.apache.org/current/gora-conf.html[gora-conf] page.
+
+[[Gora-Options]]
+Options
+~~~~~~~
+
+
+// component options: START
+The Gora component has no options.
+// component options: END
+
+
+
+
+
+// endpoint options: START
+The Gora component supports 22 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| name | common | | String | *Required* Instance name
+| dataStoreClass | common | | String | The type of the dataStore
+| keyClass | common | | String | The type class of the key
+| valueClass | common | | String | The type of the value
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| concurrentConsumers | consumer | 1 | int | Number of concurrent consumers
+| endKey | consumer | | Object | The End Key
+| endTime | consumer | | long | The End Time
+| fields | consumer | | Strings | The Fields
+| keyRangeFrom | consumer | | Object | The Key Range From
+| keyRangeTo | consumer | | Object | The Key Range To
+| limit | consumer | | long | The Limit
+| startKey | consumer | | Object | The Start Key
+| startTime | consumer | | long | The Start Time
+| timeRangeFrom | consumer | | long | The Time Range From
+| timeRangeTo | consumer | | long | The Time Range To
+| timestamp | consumer | | long | The Timestamp
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| flushOnEveryOperation | producer | true | boolean | Flush on every operation
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| hadoopConfiguration | advanced | | Configuration | Hadoop Configuration
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+
+[[Gora-SupportedGoraOperations]]
+Supported Gora Operations
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Supported operations include : *put*, *get*, *delete*, *getSchemaName*,
+*deleteSchema*, *createSchema*, *query*, *deleteByQuery*,
+*schemaExists*.
+
+Some of the operations require arguments while some others no. The
+arguments to operations could be either the _body_ of the _in_ message
+or defined in a header property. Below there is a list with some
+additional info for each operation.
+
+[width="100%",cols="10%,90%",options="header",]
+|=======================================================================
+|Property |Description
+
+|put |_Inserts the persistent object with the given key._
+
+|get |_Returns the object corresponding to the given key fetching all the
+fields._
+
+|delete |_Deletes the object with the given key._
+
+|getSchemaName |_Returns the schema name given to this DataStore._
+
+|deleteSchema |_Deletes the underlying schema or table (or similar) in the datastore
+that holds the objects._
+
+|createSchema |_Creates the optional schema or table (or similar) in the datastore to
+hold the objects._
+
+|query |_Executes the given query and returns the results._
+
+|deleteByQuery |_Deletes all the objects matching the query._
+
+|schemaExists |_Returns whether the schema that holds the data exists in the
+datastore._
+|=======================================================================
+
+[[Gora-GoraHeaders]]
+Gora Headers
+^^^^^^^^^^^^
+
+[width="100%",cols="20%,80%",options="header",]
+|=======================================================================
+|Property |Description
+
+|GoraOperation |_Used in order to define the operation to execute._
+
+|GoraKey | _Used in order to define the datum key for the operations need it._
+|=======================================================================
+
+[[Gora-Usageexamples]]
+Usage examples
+^^^^^^^^^^^^^^
+
+*Create Schema* _(XML DSL)_:
+
+[source,xml]
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<setHeader headerName="GoraOperation">
+�<constant>CreateSchema</constant>
+</setHeader>
+<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+*SchemaExists* _(XML DSL)_:
+
+[source,xml]
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<setHeader headerName="GoraOperation">
+�<constant>SchemaExists</constant>
+</setHeader>
+�<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+*Put* _(XML DSL)_:
+
+[source,xml]
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<setHeader headerName="GoraOperation">
+�<constant>put</constant>
+</setHeader>
+<setHeader headerName="GoraKey">
+�<constant>22222</constant>
+</setHeader>
+<to uri="gora:foo?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+*Get* _(XML DSL)_:
+
+[source,xml]
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<setHeader headerName="GoraOperation">
+�<constant>GET</constant>
+</setHeader>
+<setHeader headerName="GoraKey">
+�<constant>10101</constant>
+</setHeader>
+<to uri="gora:bar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+*Delete* _(XML DSL)_:
+
+[source,xml]
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<setHeader headerName="GoraOperation">
+�<constant>DELETE</constant>
+</setHeader>
+<setHeader headerName="GoraKey">
+�<constant>22222</constant>
+</setHeader>
+<to uri="gora:bar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+*Query* _(XML DSL)_:
+
+[source,xml]
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+
+The full usage examples in the form of integration tests can be found at
+https://github.com/ipolyzos/camel-gora-examples/[camel-gora-examples]
+repository.
+
+[[Gora-Moreresources]]
+More resources
+^^^^^^^^^^^^^^
+
+For more please information and in depth configuration refer to the
+http://gora.apache.org/current/overview.html[Apache Gora Documentation]
+and the http://gora.apache.org/current/tutorial.html[Apache Gora
+Tutorial].
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-gora/src/main/docs/gora.adoc
----------------------------------------------------------------------
diff --git a/components/camel-gora/src/main/docs/gora.adoc b/components/camel-gora/src/main/docs/gora.adoc
deleted file mode 100644
index 834dacc..0000000
--- a/components/camel-gora/src/main/docs/gora.adoc
+++ /dev/null
@@ -1,265 +0,0 @@
-[[Gora-GoraComponent]]
-Gora Component
-~~~~~~~~~~~~~~
-
-*Camel-Gora* is an http://camel.apache.org/[Apache Camel] component that
-allows you to work with NoSQL databases using the
-http://gora.apache.org/[Apache Gora] framework.
-
-*Available as of Camel 2.14*
-
-Maven users will need to add the following dependency to their pom.xml
-for this component:
-
-[source,xml]
----------------------------------------------------------
-<dependency>
-�<groupId>org.apache.camel</groupId>
-�<artifactId>camel-gora</artifactId>
-�<version>x.x.x</version>
-�<!-- use the same version as your Camel core version -->
-</dependency>
----------------------------------------------------------
-
-[[Gora-ApacheGoraOverview]]
-Apache Gora Overview
-~~~~~~~~~~~~~~~~~~~~
-
-The http://gora.apache.org/[Apache Gora] open source framework provides
-an in-memory data model and persistence for big data. Gora supports
-persisting to column stores, key value stores, document stores and
-RDBMSs, and analyzing the data with extensive
-http://hadoop.apache.org/[Apache Hadoop\u2122 MapReduce] support. Gora uses
-the http://www.apache.org/licenses/LICENSE-2.0.html[Apache Software
-License v2.0] and graduated from the Apache Incubator in Janauary 2012
-to become a top-level Apache project.
-
-Apache Gora currently supports the following datastores:
-http://hbase.apache.org/[Apache HBase],
-http://cassandra.apache.org/[Apache Cassandra],
-http://accumulo.apache.org/[Apache Accumulo],
-http://aws.amazon.com/dynamodb/[Amazon DynamoDB] and SQL databases such
-as http://hsqldb.org/[hsqldb], http://www.mysql.com/[MySQL] and more.
-
-[[Gora-URIformat]]
-URI format
-~~~~~~~~~~
-
-[source,text]
----------------------------
-gora:instanceName[?options]
----------------------------
-
-Hbase examples with mandatory options :
-
-_XML_
-
-[source,xml]
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-_Java DSL_
-
-[source,java]
--------------------------------------------------------------------------------------------------------------------------------------------------------------
-to("gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore")
--------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-[[Gora-Configuratiion]]
-Configuratiion
-~~~~~~~~~~~~~~
-
-Using camel-gora needs some configuration. This mainly involve to
-configure the _AvroStore_ through the _gora.properties_ file and to
-define the relevant mappings as part of the
-_http://gora.apache.org/current/gora-core.html[gora-core]_ module.
-
-Extensive information for this configuration can be found in the apache
-http://gora.apache.org/current/index.html[gora documentation] and the
-http://gora.apache.org/current/gora-conf.html[gora-conf] page.
-
-[[Gora-Options]]
-Options
-~~~~~~~
-
-
-// component options: START
-The Gora component has no options.
-// component options: END
-
-
-
-
-
-// endpoint options: START
-The Gora component supports 22 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| name | common | | String | *Required* Instance name
-| dataStoreClass | common | | String | The type of the dataStore
-| keyClass | common | | String | The type class of the key
-| valueClass | common | | String | The type of the value
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| concurrentConsumers | consumer | 1 | int | Number of concurrent consumers
-| endKey | consumer | | Object | The End Key
-| endTime | consumer | | long | The End Time
-| fields | consumer | | Strings | The Fields
-| keyRangeFrom | consumer | | Object | The Key Range From
-| keyRangeTo | consumer | | Object | The Key Range To
-| limit | consumer | | long | The Limit
-| startKey | consumer | | Object | The Start Key
-| startTime | consumer | | long | The Start Time
-| timeRangeFrom | consumer | | long | The Time Range From
-| timeRangeTo | consumer | | long | The Time Range To
-| timestamp | consumer | | long | The Timestamp
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| flushOnEveryOperation | producer | true | boolean | Flush on every operation
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| hadoopConfiguration | advanced | | Configuration | Hadoop Configuration
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-
-[[Gora-SupportedGoraOperations]]
-Supported Gora Operations
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Supported operations include : *put*, *get*, *delete*, *getSchemaName*,
-*deleteSchema*, *createSchema*, *query*, *deleteByQuery*,
-*schemaExists*.
-
-Some of the operations require arguments while some others no. The
-arguments to operations could be either the _body_ of the _in_ message
-or defined in a header property. Below there is a list with some
-additional info for each operation.
-
-[width="100%",cols="10%,90%",options="header",]
-|=======================================================================
-|Property |Description
-
-|put |_Inserts the persistent object with the given key._
-
-|get |_Returns the object corresponding to the given key fetching all the
-fields._
-
-|delete |_Deletes the object with the given key._
-
-|getSchemaName |_Returns the schema name given to this DataStore._
-
-|deleteSchema |_Deletes the underlying schema or table (or similar) in the datastore
-that holds the objects._
-
-|createSchema |_Creates the optional schema or table (or similar) in the datastore to
-hold the objects._
-
-|query |_Executes the given query and returns the results._
-
-|deleteByQuery |_Deletes all the objects matching the query._
-
-|schemaExists |_Returns whether the schema that holds the data exists in the
-datastore._
-|=======================================================================
-
-[[Gora-GoraHeaders]]
-Gora Headers
-^^^^^^^^^^^^
-
-[width="100%",cols="20%,80%",options="header",]
-|=======================================================================
-|Property |Description
-
-|GoraOperation |_Used in order to define the operation to execute._
-
-|GoraKey | _Used in order to define the datum key for the operations need it._
-|=======================================================================
-
-[[Gora-Usageexamples]]
-Usage examples
-^^^^^^^^^^^^^^
-
-*Create Schema* _(XML DSL)_:
-
-[source,xml]
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<setHeader headerName="GoraOperation">
-�<constant>CreateSchema</constant>
-</setHeader>
-<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-*SchemaExists* _(XML DSL)_:
-
-[source,xml]
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<setHeader headerName="GoraOperation">
-�<constant>SchemaExists</constant>
-</setHeader>
-�<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-*Put* _(XML DSL)_:
-
-[source,xml]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<setHeader headerName="GoraOperation">
-�<constant>put</constant>
-</setHeader>
-<setHeader headerName="GoraKey">
-�<constant>22222</constant>
-</setHeader>
-<to uri="gora:foo?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-*Get* _(XML DSL)_:
-
-[source,xml]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<setHeader headerName="GoraOperation">
-�<constant>GET</constant>
-</setHeader>
-<setHeader headerName="GoraKey">
-�<constant>10101</constant>
-</setHeader>
-<to uri="gora:bar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-*Delete* _(XML DSL)_:
-
-[source,xml]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<setHeader headerName="GoraOperation">
-�<constant>DELETE</constant>
-</setHeader>
-<setHeader headerName="GoraKey">
-�<constant>22222</constant>
-</setHeader>
-<to uri="gora:bar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-*Query* _(XML DSL)_:
-
-[source,xml]
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-<to uri="gora:foobar?keyClass=java.lang.Long&valueClass=org.apache.camel.component.gora.generated.Pageview&dataStoreClass=org.apache.gora.hbase.store.HBaseStore"/>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-
-The full usage examples in the form of integration tests can be found at
-https://github.com/ipolyzos/camel-gora-examples/[camel-gora-examples]
-repository.
-
-[[Gora-Moreresources]]
-More resources
-^^^^^^^^^^^^^^
-
-For more please information and in depth configuration refer to the
-http://gora.apache.org/current/overview.html[Apache Gora Documentation]
-and the http://gora.apache.org/current/tutorial.html[Apache Gora
-Tutorial].
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-grape/src/main/docs/grape-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-grape/src/main/docs/grape-component.adoc b/components/camel-grape/src/main/docs/grape-component.adoc
new file mode 100644
index 0000000..9f7956e
--- /dev/null
+++ b/components/camel-grape/src/main/docs/grape-component.adoc
@@ -0,0 +1,250 @@
+[[Grape-GrapeComponent]]
+Grape Component
+~~~~~~~~~~~~~~~
+
+Available as of Camel 2.16�
+
+http://docs.groovy-lang.org/latest/html/documentation/grape.html[Grape]
+component allows you to fetch, load and manage additional jars when
+`CamelContext` is running. In practice with Camel Grape component you
+can add new components, data formats and beans to your `CamelContext`
+without the restart of the router.
+
+
+[[Grape-Options]]
+Grape options
+^^^^^^^^^^^^^
+
+// component options: START
+The Grape component has no options.
+// component options: END
+
+
+// endpoint options: START
+The Grape component supports 3 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| defaultCoordinates | | | String | *Required* Maven coordinates to use as default to grab if the message body is empty.
+| exchangePattern | | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange.
+| synchronous | | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+[[Grape-Settingupclassloader]]
+Setting up class loader
+^^^^^^^^^^^^^^^^^^^^^^^
+
+Grape requires using Groovy class loader with the `CamelContext`. You
+can enable Groovy class loading on the existing Camel Context using the
+`GrapeComponent#grapeCamelContext()` method:
+
+[source,java]
+--------------------------------------------------------------------------------
+import static org.apache.camel.component.grape.GrapeComponent.grapeCamelContext;
+...
+CamelContext camelContext = grapeCamelContext(new DefaultCamelContext());
+--------------------------------------------------------------------------------
+
+You can also set up the Groovy class loader used be Camel context by
+yourself:
+
+[source,java]
+------------------------------------------------------------------------------------
+camelContext.setApplicationContextClassLoader(new GroovyClassLoader(myClassLoader));
+------------------------------------------------------------------------------------
+
+[[Grape-URIformat]]
+URI format
+^^^^^^^^^^
+
+Grape component supports only producer endpoints.
+
+[source,java]
+-----------------------------
+grape:defaultMavenCoordinates
+-----------------------------
+
+For example the following snippet loads Camel FTP component:
+
+[source,java]
+------------------------------------------------
+from("direct:loadCamelFTP").
+ to("grape:org.apache.camel/camel-ftp/2.15.2");
+------------------------------------------------
+
+You can also specify the Maven coordinates by sending them to the
+endpoint as the exchange body:
+
+[source,java]
+----------------------------------------------------------
+from("direct:loadCamelFTP").
+ setBody().constant("org.apache.camel/camel-ftp/2.15.2").
+ to("grape:defaultMavenCoordinates");
+----------------------------------------------------------
+
+[[Grape-AddingtheGrapecomponenttotheproject]]
+Adding the Grape component to the project
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-grape</artifactId>
+ <version>x.y.z</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+[[Grape-Defaultpayloadtype]]
+Default payload type
+^^^^^^^^^^^^^^^^^^^^
+
+By default Camel Grape component operates on the String payloads:
+
+[source,java]
+------------------------------------------------------------------------------------------------
+producerTemplate.sendBody("grape:defaultMavenCoordinates", "org.apache.camel/camel-ftp/2.15.2");
+------------------------------------------------------------------------------------------------
+
+But of course Camel build-in�link:type-converter.html[type conversion
+API] can perform the automatic data type transformations for you. In the
+example below Camel automatically converts binary payload into the
+String:
+
+�
+
+[source,java]
+-----------------------------------------------------------------------------------------------------------
+producerTemplate.sendBody("grape:defaultMavenCoordinates", "org.apache.camel/camel-ftp/2.15.2".getBytes());
+-----------------------------------------------------------------------------------------------------------
+
+[[Grape-Headers]]
+Headers
+^^^^^^^
+
+The following headers are recognized by the Grape component:
+
+[width="100%",cols="10%,10%,10%,10%,60%",options="header",]
+|=======================================================================
+|Header |Java constant |Endpoint type |Value type |Description
+
+|`CamelGrapeCommand` |`GrapeConstants.GRAPE_COMMAND` |Producer |`org.apache.camel.component.grape.GrapeCommand` |The command to be performed by the Grape endpoint. Default to `grab`.
+|=======================================================================
+
+[[Grape-Loadingcomponentsatruntime]]
+Loading components at runtime
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In order to load the new component at the router runtime, just grab the
+jar containing the given component:
+
+[source,java]
+-------------------------------------------------------------------------
+ProducerTemplate template = camelContext.createProducerTemplate();
+template.sendBody("grape:grape", "org.apache.camel/camel-stream/2.15.2");
+template.sendBody("stream:out", "msg");
+-------------------------------------------------------------------------
+
+[[Grape-Loadingprocessorsbeanatruntime]]
+Loading processors�bean�at runtime
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In order to load the new processor�bean �with your custom business login
+at the router runtime, just grab the jar containing the required bean:
+
+[source,java]
+-----------------------------------------------------------------------------------------------------------------
+ProducerTemplate template = camelContext.createProducerTemplate();
+template.sendBody("grape:grape", "com.example/my-business-processors/1.0");
+int productId = 1;
+int price = template.requestBody("bean:com.example.PricingBean?method=currentProductPrice", productId, int.class)
+-----------------------------------------------------------------------------------------------------------------
+
+�
+
+[[Grape-LoadingdeployedjarsafterCamelcontextrestart]]
+Loading deployed jars after Camel context restart
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+After you download new jar, you usually would like to have it loaded by
+the Camel again after the restart of the `CamelContext`. It is certainly
+possible, as Grape component keeps track of the jar files you have
+installed. In order to load again the installed jars on the context
+startup, use the�`GrapeEndpoint.loadPatches()`�method in your route:�
+
+�
+
+[source,java]
+-------------------------------------------------------------------------
+import static org.apache.camel.component.grape.GrapeEndpoint.loadPatches;
+
+...�
+camelContext.addRoutes(
+ new RouteBuilder() {�
+ @Override�
+ public void configure() throws Exception {�
+ loadPatches(camelContext);
+�
+ from("direct:loadCamelFTP").
+ to("grape:org.apache.camel/camel-ftp/2.15.2");�
+ }
+ });
+-------------------------------------------------------------------------
+
+�
+
+[[Grape-Managingtheinstalledjars]]
+Managing the installed jars
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you would like to check what jars have been installed into the given
+`CamelContext`, send message to the grape endpoint with
+the�`CamelGrapeCommand` header set to `GrapeCommand.listPatches`:
+
+[source,java]
+----------------------------------------------------------------------------------------
+ from("netty-http4:http://0.0.0.0:80/patches").
+ setHeader(GrapeConstats.GRAPE_COMMAND, constant(CamelGrapeCommand.listPatches)).
+ to("grape:list");�
+----------------------------------------------------------------------------------------
+
+Connecting the to the route defined above using the HTTP client returns
+the list of the jars installed by Grape component:
+
+[source,java]
+---------------------------------------
+$ curl http://my-router.com/patches
+grape:org.apache.camel/camel-ftp/2.15.2
+grape:org.apache.camel/camel-jms/2.15.2
+---------------------------------------
+
+If you would like to remove the installed jars, so these won't be loaded
+again after the context restart, use the�`GrapeCommand.``clearPatches`
+command:
+
+[source,java]
+-----------------------------------------------------------------------------------------
+ from("netty-http4:http://0.0.0.0:80/patches").
+ setHeader(GrapeConstats.GRAPE_COMMAND, constant(CamelGrapeCommand.clearPatches)).
+ setBody().constant("Installed patches have been deleted.");�
+-----------------------------------------------------------------------------------------
+
+[[Grape-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-grape/src/main/docs/grape.adoc
----------------------------------------------------------------------
diff --git a/components/camel-grape/src/main/docs/grape.adoc b/components/camel-grape/src/main/docs/grape.adoc
deleted file mode 100644
index 9f7956e..0000000
--- a/components/camel-grape/src/main/docs/grape.adoc
+++ /dev/null
@@ -1,250 +0,0 @@
-[[Grape-GrapeComponent]]
-Grape Component
-~~~~~~~~~~~~~~~
-
-Available as of Camel 2.16�
-
-http://docs.groovy-lang.org/latest/html/documentation/grape.html[Grape]
-component allows you to fetch, load and manage additional jars when
-`CamelContext` is running. In practice with Camel Grape component you
-can add new components, data formats and beans to your `CamelContext`
-without the restart of the router.
-
-
-[[Grape-Options]]
-Grape options
-^^^^^^^^^^^^^
-
-// component options: START
-The Grape component has no options.
-// component options: END
-
-
-// endpoint options: START
-The Grape component supports 3 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| defaultCoordinates | | | String | *Required* Maven coordinates to use as default to grab if the message body is empty.
-| exchangePattern | | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange.
-| synchronous | | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-[[Grape-Settingupclassloader]]
-Setting up class loader
-^^^^^^^^^^^^^^^^^^^^^^^
-
-Grape requires using Groovy class loader with the `CamelContext`. You
-can enable Groovy class loading on the existing Camel Context using the
-`GrapeComponent#grapeCamelContext()` method:
-
-[source,java]
---------------------------------------------------------------------------------
-import static org.apache.camel.component.grape.GrapeComponent.grapeCamelContext;
-...
-CamelContext camelContext = grapeCamelContext(new DefaultCamelContext());
---------------------------------------------------------------------------------
-
-You can also set up the Groovy class loader used be Camel context by
-yourself:
-
-[source,java]
-------------------------------------------------------------------------------------
-camelContext.setApplicationContextClassLoader(new GroovyClassLoader(myClassLoader));
-------------------------------------------------------------------------------------
-
-[[Grape-URIformat]]
-URI format
-^^^^^^^^^^
-
-Grape component supports only producer endpoints.
-
-[source,java]
------------------------------
-grape:defaultMavenCoordinates
------------------------------
-
-For example the following snippet loads Camel FTP component:
-
-[source,java]
-------------------------------------------------
-from("direct:loadCamelFTP").
- to("grape:org.apache.camel/camel-ftp/2.15.2");
-------------------------------------------------
-
-You can also specify the Maven coordinates by sending them to the
-endpoint as the exchange body:
-
-[source,java]
-----------------------------------------------------------
-from("direct:loadCamelFTP").
- setBody().constant("org.apache.camel/camel-ftp/2.15.2").
- to("grape:defaultMavenCoordinates");
-----------------------------------------------------------
-
-[[Grape-AddingtheGrapecomponenttotheproject]]
-Adding the Grape component to the project
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Maven users will need to add the following dependency to their `pom.xml`
-for this component:
-
-[source,xml]
-------------------------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-grape</artifactId>
- <version>x.y.z</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-------------------------------------------------------------
-
-[[Grape-Defaultpayloadtype]]
-Default payload type
-^^^^^^^^^^^^^^^^^^^^
-
-By default Camel Grape component operates on the String payloads:
-
-[source,java]
-------------------------------------------------------------------------------------------------
-producerTemplate.sendBody("grape:defaultMavenCoordinates", "org.apache.camel/camel-ftp/2.15.2");
-------------------------------------------------------------------------------------------------
-
-But of course Camel build-in�link:type-converter.html[type conversion
-API] can perform the automatic data type transformations for you. In the
-example below Camel automatically converts binary payload into the
-String:
-
-�
-
-[source,java]
------------------------------------------------------------------------------------------------------------
-producerTemplate.sendBody("grape:defaultMavenCoordinates", "org.apache.camel/camel-ftp/2.15.2".getBytes());
------------------------------------------------------------------------------------------------------------
-
-[[Grape-Headers]]
-Headers
-^^^^^^^
-
-The following headers are recognized by the Grape component:
-
-[width="100%",cols="10%,10%,10%,10%,60%",options="header",]
-|=======================================================================
-|Header |Java constant |Endpoint type |Value type |Description
-
-|`CamelGrapeCommand` |`GrapeConstants.GRAPE_COMMAND` |Producer |`org.apache.camel.component.grape.GrapeCommand` |The command to be performed by the Grape endpoint. Default to `grab`.
-|=======================================================================
-
-[[Grape-Loadingcomponentsatruntime]]
-Loading components at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-In order to load the new component at the router runtime, just grab the
-jar containing the given component:
-
-[source,java]
--------------------------------------------------------------------------
-ProducerTemplate template = camelContext.createProducerTemplate();
-template.sendBody("grape:grape", "org.apache.camel/camel-stream/2.15.2");
-template.sendBody("stream:out", "msg");
--------------------------------------------------------------------------
-
-[[Grape-Loadingprocessorsbeanatruntime]]
-Loading processors�bean�at runtime
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-In order to load the new processor�bean �with your custom business login
-at the router runtime, just grab the jar containing the required bean:
-
-[source,java]
------------------------------------------------------------------------------------------------------------------
-ProducerTemplate template = camelContext.createProducerTemplate();
-template.sendBody("grape:grape", "com.example/my-business-processors/1.0");
-int productId = 1;
-int price = template.requestBody("bean:com.example.PricingBean?method=currentProductPrice", productId, int.class)
------------------------------------------------------------------------------------------------------------------
-
-�
-
-[[Grape-LoadingdeployedjarsafterCamelcontextrestart]]
-Loading deployed jars after Camel context restart
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-After you download new jar, you usually would like to have it loaded by
-the Camel again after the restart of the `CamelContext`. It is certainly
-possible, as Grape component keeps track of the jar files you have
-installed. In order to load again the installed jars on the context
-startup, use the�`GrapeEndpoint.loadPatches()`�method in your route:�
-
-�
-
-[source,java]
--------------------------------------------------------------------------
-import static org.apache.camel.component.grape.GrapeEndpoint.loadPatches;
-
-...�
-camelContext.addRoutes(
- new RouteBuilder() {�
- @Override�
- public void configure() throws Exception {�
- loadPatches(camelContext);
-�
- from("direct:loadCamelFTP").
- to("grape:org.apache.camel/camel-ftp/2.15.2");�
- }
- });
--------------------------------------------------------------------------
-
-�
-
-[[Grape-Managingtheinstalledjars]]
-Managing the installed jars
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you would like to check what jars have been installed into the given
-`CamelContext`, send message to the grape endpoint with
-the�`CamelGrapeCommand` header set to `GrapeCommand.listPatches`:
-
-[source,java]
-----------------------------------------------------------------------------------------
- from("netty-http4:http://0.0.0.0:80/patches").
- setHeader(GrapeConstats.GRAPE_COMMAND, constant(CamelGrapeCommand.listPatches)).
- to("grape:list");�
-----------------------------------------------------------------------------------------
-
-Connecting the to the route defined above using the HTTP client returns
-the list of the jars installed by Grape component:
-
-[source,java]
----------------------------------------
-$ curl http://my-router.com/patches
-grape:org.apache.camel/camel-ftp/2.15.2
-grape:org.apache.camel/camel-jms/2.15.2
----------------------------------------
-
-If you would like to remove the installed jars, so these won't be loaded
-again after the context restart, use the�`GrapeCommand.``clearPatches`
-command:
-
-[source,java]
------------------------------------------------------------------------------------------
- from("netty-http4:http://0.0.0.0:80/patches").
- setHeader(GrapeConstats.GRAPE_COMMAND, constant(CamelGrapeCommand.clearPatches)).
- setBody().constant("Installed patches have been deleted.");�
------------------------------------------------------------------------------------------
-
-[[Grape-SeeAlso]]
-See Also
-^^^^^^^^
-
-* link:configuring-camel.html[Configuring Camel]
-* link:component.html[Component]
-* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
new file mode 100644
index 0000000..dd943fe
--- /dev/null
+++ b/components/camel-guava-eventbus/src/main/docs/guava-eventbus-component.adoc
@@ -0,0 +1,215 @@
+[[GuavaEventBus-GuavaEventBusComponent]]
+Guava EventBus Component
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+*Available since Camel 2.10.0*
+
+The
+http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html[Google
+Guava EventBus] allows publish-subscribe-style communication between
+components without requiring the components to explicitly register with
+one another (and thus be aware of each other). The *guava-eventbus:*
+component provides integration bridge between Camel and
+http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html[Google
+Guava EventBus] infrastructure. With the latter component, messages
+exchanged with the Guava `EventBus` can be transparently forwarded to
+the Camel routes. EventBus component allows also to route body of Camel
+exchanges to the Guava `EventBus`.
+
+Maven users will need to add the following dependency to their `pom.xml`
+for this component:
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-guava-eventbus</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+[[GuavaEventBus-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+--------------------------------
+guava-eventbus:busName[?options]
+--------------------------------
+
+Where *busName* represents the name of the
+`com.google.common.eventbus.EventBus` instance located in the Camel
+registry.
+
+[[GuavaEventBus-Options]]
+Options
+^^^^^^^
+
+
+
+
+// component options: START
+The Guava EventBus component supports 2 options which are listed below.
+
+
+
+{% raw %}
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| eventBus | EventBus | To use the given Guava EventBus instance
+| listenerInterface | Class<?> | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option.
+|=======================================================================
+{% endraw %}
+// component options: END
+
+
+
+
+// endpoint options: START
+The Guava EventBus component supports 7 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| eventBusRef | common | | String | To lookup the Guava EventBus from the registry with the given name
+| eventClass | common | | Class<?> | If used on the consumer side of the route will filter events received from the EventBus to the instances of the class and superclasses of eventClass. Null value of this option is equal to setting it to the java.lang.Object i.e. the consumer will capture all messages incoming to the event bus. This option cannot be used together with listenerInterface option.
+| listenerInterface | common | | Class<?> | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option.
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+[[GuavaEventBus-Usage]]
+Usage
+^^^^^
+
+Using `guava-eventbus` component on the consumer side of the route will
+capture messages sent to the Guava `EventBus` and forward them to the
+Camel route. Guava EventBus consumer processes incoming messages
+http://camel.apache.org/asynchronous-routing-engine.html[asynchronously].
+
+[source,java]
+-------------------------------------------------------
+SimpleRegistry registry = new SimpleRegistry();
+EventBus eventBus = new EventBus();
+registry.put("busName", eventBus);
+CamelContext camel = new DefaultCamelContext(registry);
+
+from("guava-eventbus:busName").to("seda:queue");
+
+eventBus.post("Send me to the SEDA queue.");
+-------------------------------------------------------
+
+Using `guava-eventbus` component on the producer side of the route will
+forward body of the Camel exchanges to the Guava `EventBus` instance.
+
+[source,java]
+----------------------------------------------------------------------
+SimpleRegistry registry = new SimpleRegistry();
+EventBus eventBus = new EventBus();
+registry.put("busName", eventBus);
+CamelContext camel = new DefaultCamelContext(registry);
+
+from("direct:start").to("guava-eventbus:busName");
+
+ProducerTemplate producerTemplate = camel.createProducerTemplate();
+producer.sendBody("direct:start", "Send me to the Guava EventBus.");
+
+eventBus.register(new Object(){
+ @Subscribe
+ public void messageHander(String message) {
+ System.out.println("Message received from the Camel: " + message);
+ }
+});
+----------------------------------------------------------------------
+
+[[GuavaEventBus-DeadEventconsiderations]]
+DeadEvent considerations
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+Keep in mind that due to the limitations caused by the design of the
+Guava EventBus, you cannot specify event class to be received by the
+listener without creating class annotated with `@Subscribe` method. This
+limitation implies that endpoint with `eventClass` option specified
+actually listens to all possible events (`java.lang.Object`) and filter
+appropriate messages programmatically at runtime. The snipped below
+demonstrates an appropriate excerpt from the Camel code base.
+
+[source,java]
+----------------------------------------------------------------------------
+@Subscribe
+public void eventReceived(Object event) {
+ if (eventClass == null || eventClass.isAssignableFrom(event.getClass())) {
+ doEventReceived(event);
+...
+----------------------------------------------------------------------------
+
+This drawback of this approach is that `EventBus` instance used by Camel
+will never generate `com.google.common.eventbus.DeadEvent`
+notifications. If you want Camel to listen only to the precisely
+specified event (and therefore enable `DeadEvent` support), use
+`listenerInterface` endpoint option. Camel will create dynamic proxy
+over the interface you specify with the latter option and listen only to
+messages specified by the interface handler methods. The example of the
+listener interface with single method handling only `SpecificEvent`
+instances is demonstrated below.
+
+[source,java]
+------------------------------------------
+package com.example;
+
+public interface CustomListener {
+
+ @Subscribe
+ void eventReceived(SpecificEvent event);
+
+}
+------------------------------------------
+
+The listener presented above could be used in the endpoint definition as
+follows.
+
+[source,java]
+---------------------------------------------------------------------------------------------
+from("guava-eventbus:busName?listenerInterface=com.example.CustomListener").to("seda:queue");
+---------------------------------------------------------------------------------------------
+
+[[GuavaEventBus-Consumingmultipletypeofevents]]
+Consuming multiple type of events
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In order to define multiple type of events to be consumed by Guava
+EventBus consumer use `listenerInterface` endpoint option, as listener
+interface could provide multiple methods marked with the `@Subscribe`
+annotation.
+
+[source,java]
+------------------------------------------------
+package com.example;
+
+public interface MultipleEventsListener {
+
+ @Subscribe
+ void someEventReceived(SomeEvent event);
+
+ @Subscribe
+ void anotherEventReceived(AnotherEvent event);
+
+}
+------------------------------------------------
+
+The listener presented above could be used in the endpoint definition as
+follows.
+
+[source,java]
+-----------------------------------------------------------------------------------------------------
+from("guava-eventbus:busName?listenerInterface=com.example.MultipleEventsListener").to("seda:queue");
+-----------------------------------------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-guava-eventbus/src/main/docs/guava-eventbus.adoc
----------------------------------------------------------------------
diff --git a/components/camel-guava-eventbus/src/main/docs/guava-eventbus.adoc b/components/camel-guava-eventbus/src/main/docs/guava-eventbus.adoc
deleted file mode 100644
index dd943fe..0000000
--- a/components/camel-guava-eventbus/src/main/docs/guava-eventbus.adoc
+++ /dev/null
@@ -1,215 +0,0 @@
-[[GuavaEventBus-GuavaEventBusComponent]]
-Guava EventBus Component
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-*Available since Camel 2.10.0*
-
-The
-http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html[Google
-Guava EventBus] allows publish-subscribe-style communication between
-components without requiring the components to explicitly register with
-one another (and thus be aware of each other). The *guava-eventbus:*
-component provides integration bridge between Camel and
-http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/eventbus/package-summary.html[Google
-Guava EventBus] infrastructure. With the latter component, messages
-exchanged with the Guava `EventBus` can be transparently forwarded to
-the Camel routes. EventBus component allows also to route body of Camel
-exchanges to the Guava `EventBus`.
-
-Maven users will need to add the following dependency to their `pom.xml`
-for this component:
-
-[source,xml]
-------------------------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-guava-eventbus</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-------------------------------------------------------------
-
-[[GuavaEventBus-URIformat]]
-URI format
-^^^^^^^^^^
-
-[source,java]
---------------------------------
-guava-eventbus:busName[?options]
---------------------------------
-
-Where *busName* represents the name of the
-`com.google.common.eventbus.EventBus` instance located in the Camel
-registry.
-
-[[GuavaEventBus-Options]]
-Options
-^^^^^^^
-
-
-
-
-// component options: START
-The Guava EventBus component supports 2 options which are listed below.
-
-
-
-{% raw %}
-[width="100%",cols="2s,1m,8",options="header"]
-|=======================================================================
-| Name | Java Type | Description
-| eventBus | EventBus | To use the given Guava EventBus instance
-| listenerInterface | Class<?> | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option.
-|=======================================================================
-{% endraw %}
-// component options: END
-
-
-
-
-// endpoint options: START
-The Guava EventBus component supports 7 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| eventBusRef | common | | String | To lookup the Guava EventBus from the registry with the given name
-| eventClass | common | | Class<?> | If used on the consumer side of the route will filter events received from the EventBus to the instances of the class and superclasses of eventClass. Null value of this option is equal to setting it to the java.lang.Object i.e. the consumer will capture all messages incoming to the event bus. This option cannot be used together with listenerInterface option.
-| listenerInterface | common | | Class<?> | The interface with method(s) marked with the Subscribe annotation. Dynamic proxy will be created over the interface so it could be registered as the EventBus listener. Particularly useful when creating multi-event listeners and for handling DeadEvent properly. This option cannot be used together with eventClass option.
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-[[GuavaEventBus-Usage]]
-Usage
-^^^^^
-
-Using `guava-eventbus` component on the consumer side of the route will
-capture messages sent to the Guava `EventBus` and forward them to the
-Camel route. Guava EventBus consumer processes incoming messages
-http://camel.apache.org/asynchronous-routing-engine.html[asynchronously].
-
-[source,java]
--------------------------------------------------------
-SimpleRegistry registry = new SimpleRegistry();
-EventBus eventBus = new EventBus();
-registry.put("busName", eventBus);
-CamelContext camel = new DefaultCamelContext(registry);
-
-from("guava-eventbus:busName").to("seda:queue");
-
-eventBus.post("Send me to the SEDA queue.");
--------------------------------------------------------
-
-Using `guava-eventbus` component on the producer side of the route will
-forward body of the Camel exchanges to the Guava `EventBus` instance.
-
-[source,java]
-----------------------------------------------------------------------
-SimpleRegistry registry = new SimpleRegistry();
-EventBus eventBus = new EventBus();
-registry.put("busName", eventBus);
-CamelContext camel = new DefaultCamelContext(registry);
-
-from("direct:start").to("guava-eventbus:busName");
-
-ProducerTemplate producerTemplate = camel.createProducerTemplate();
-producer.sendBody("direct:start", "Send me to the Guava EventBus.");
-
-eventBus.register(new Object(){
- @Subscribe
- public void messageHander(String message) {
- System.out.println("Message received from the Camel: " + message);
- }
-});
-----------------------------------------------------------------------
-
-[[GuavaEventBus-DeadEventconsiderations]]
-DeadEvent considerations
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-Keep in mind that due to the limitations caused by the design of the
-Guava EventBus, you cannot specify event class to be received by the
-listener without creating class annotated with `@Subscribe` method. This
-limitation implies that endpoint with `eventClass` option specified
-actually listens to all possible events (`java.lang.Object`) and filter
-appropriate messages programmatically at runtime. The snipped below
-demonstrates an appropriate excerpt from the Camel code base.
-
-[source,java]
-----------------------------------------------------------------------------
-@Subscribe
-public void eventReceived(Object event) {
- if (eventClass == null || eventClass.isAssignableFrom(event.getClass())) {
- doEventReceived(event);
-...
-----------------------------------------------------------------------------
-
-This drawback of this approach is that `EventBus` instance used by Camel
-will never generate `com.google.common.eventbus.DeadEvent`
-notifications. If you want Camel to listen only to the precisely
-specified event (and therefore enable `DeadEvent` support), use
-`listenerInterface` endpoint option. Camel will create dynamic proxy
-over the interface you specify with the latter option and listen only to
-messages specified by the interface handler methods. The example of the
-listener interface with single method handling only `SpecificEvent`
-instances is demonstrated below.
-
-[source,java]
-------------------------------------------
-package com.example;
-
-public interface CustomListener {
-
- @Subscribe
- void eventReceived(SpecificEvent event);
-
-}
-------------------------------------------
-
-The listener presented above could be used in the endpoint definition as
-follows.
-
-[source,java]
----------------------------------------------------------------------------------------------
-from("guava-eventbus:busName?listenerInterface=com.example.CustomListener").to("seda:queue");
----------------------------------------------------------------------------------------------
-
-[[GuavaEventBus-Consumingmultipletypeofevents]]
-Consuming multiple type of events
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-In order to define multiple type of events to be consumed by Guava
-EventBus consumer use `listenerInterface` endpoint option, as listener
-interface could provide multiple methods marked with the `@Subscribe`
-annotation.
-
-[source,java]
-------------------------------------------------
-package com.example;
-
-public interface MultipleEventsListener {
-
- @Subscribe
- void someEventReceived(SomeEvent event);
-
- @Subscribe
- void anotherEventReceived(AnotherEvent event);
-
-}
-------------------------------------------------
-
-The listener presented above could be used in the endpoint definition as
-follows.
-
-[source,java]
------------------------------------------------------------------------------------------------------
-from("guava-eventbus:busName?listenerInterface=com.example.MultipleEventsListener").to("seda:queue");
------------------------------------------------------------------------------------------------------