You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2016/06/08 13:48:37 UTC
[1/3] camel git commit: Added camel-stax docs to Gitbook
Repository: camel
Updated Branches:
refs/heads/master 7602c20ea -> 60e042ae7
Added camel-stax docs to Gitbook
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/8a4dc407
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/8a4dc407
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/8a4dc407
Branch: refs/heads/master
Commit: 8a4dc407f872c9bb7066be855c3ee97bc9717568
Parents: 7602c20
Author: Andrea Cosentino <an...@gmail.com>
Authored: Wed Jun 8 15:32:34 2016 +0200
Committer: Andrea Cosentino <an...@gmail.com>
Committed: Wed Jun 8 15:32:34 2016 +0200
----------------------------------------------------------------------
components/camel-stax/src/main/docs/stax.adoc | 219 +++++++++++++++++++++
docs/user-manual/en/SUMMARY.md | 1 +
2 files changed, 220 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/8a4dc407/components/camel-stax/src/main/docs/stax.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stax/src/main/docs/stax.adoc b/components/camel-stax/src/main/docs/stax.adoc
new file mode 100644
index 0000000..4467f38
--- /dev/null
+++ b/components/camel-stax/src/main/docs/stax.adoc
@@ -0,0 +1,219 @@
+[[StAX-StAXComponent]]
+StAX Component
+~~~~~~~~~~~~~~
+
+*Available as of Camel 2.9*
+
+The StAX component allows messages to be process through a SAX
+http://download.oracle.com/javase/6/docs/api/org/xml/sax/ContentHandler.html[ContentHandler]. +
+Another feature of this component is to allow to iterate over JAXB
+records using StAX, for example using the link:splitter.html[Splitter]
+EIP.
+
+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-stax</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+[[StAX-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+--------------------------
+stax:content-handler-class
+--------------------------
+
+example:
+
+[source,java]
+-----------------------------------
+stax:org.superbiz.FooContentHandler
+-----------------------------------
+
+From *Camel 2.11.1* onwards you can lookup a
+`org.xml.sax.ContentHandler` bean from the link:registry.html[Registry]
+using the # syntax as shown:
+
+[source,java]
+---------------
+stax:#myHandler
+---------------
+
+[[Stax-Options]]
+Options
+~~~~~~~
+
+
+// component options: START
+The StAX component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The StAX 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
+| contentHandlerClass | producer | | String | *Required* The FQN class name for the ContentHandler implementation to use.
+| 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
+
+
+[[StAX-UsageofacontenthandlerasStAXparser]]
+Usage of a content handler as StAX parser
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The message body after the handling is the handler itself.
+
+Here an example:
+
+[source,java]
+--------------------------------------------------------------------------------------------------------
+from("file:target/in")
+ .to("stax:org.superbiz.handler.CountingHandler")
+ // CountingHandler implements org.xml.sax.ContentHandler or extends org.xml.sax.helpers.DefaultHandler
+ .process(new Processor() {
+ @Override
+ public void process(Exchange exchange) throws Exception {
+ CountingHandler handler = exchange.getIn().getBody(CountingHandler.class);
+ // do some great work with the handler
+ }
+ });
+--------------------------------------------------------------------------------------------------------
+
+[[StAX-IterateoveracollectionusingJAXBandStAX]]
+Iterate over a collection using JAXB and StAX
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+First we suppose you have JAXB objects.
+
+For instance a list of records in a wrapper object:
+
+[source,java]
+-------------------------------------------------
+import java.util.ArrayList;
+import java.util.List;
+import javax.xml.bind.annotation.XmlAccessType;
+import javax.xml.bind.annotation.XmlAccessorType;
+import javax.xml.bind.annotation.XmlElement;
+import javax.xml.bind.annotation.XmlRootElement;
+
+@XmlAccessorType(XmlAccessType.FIELD)
+@XmlRootElement(name = "records")
+public class Records {
+ @XmlElement(required = true)
+ protected List<Record> record;
+
+ public List<Record> getRecord() {
+ if (record == null) {
+ record = new ArrayList<Record>();
+ }
+ return record;
+ }
+}
+-------------------------------------------------
+
+and
+
+[source,java]
+---------------------------------------------------------
+import javax.xml.bind.annotation.XmlAccessType;
+import javax.xml.bind.annotation.XmlAccessorType;
+import javax.xml.bind.annotation.XmlAttribute;
+import javax.xml.bind.annotation.XmlType;
+
+@XmlAccessorType(XmlAccessType.FIELD)
+@XmlType(name = "record", propOrder = { "key", "value" })
+public class Record {
+ @XmlAttribute(required = true)
+ protected String key;
+
+ @XmlAttribute(required = true)
+ protected String value;
+
+ public String getKey() {
+ return key;
+ }
+
+ public void setKey(String key) {
+ this.key = key;
+ }
+
+ public String getValue() {
+ return value;
+ }
+
+ public void setValue(String value) {
+ this.value = value;
+ }
+}
+---------------------------------------------------------
+
+Then you get a XML file to process:
+
+[source,xml]
+-------------------------------------------------------
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<records>
+ <record value="v0" key="0"/>
+ <record value="v1" key="1"/>
+ <record value="v2" key="2"/>
+ <record value="v3" key="3"/>
+ <record value="v4" key="4"/>
+ <record value="v5" key="5"/>
+</record>
+-------------------------------------------------------
+
+The StAX component provides an `StAXBuilder` which can be used when
+iterating XML elements with the Camel link:splitter.html[Splitter]
+
+[source,java]
+------------------------------------------
+from("file:target/in")
+ .split(stax(Record.class)).streaming()
+ .to("mock:records");
+------------------------------------------
+
+Where `stax` is a static method on
+`org.apache.camel.component.stax.StAXBuilder` which you can static
+import in the Java code. The stax builder is by default namespace aware
+on the XMLReader it uses. From *Camel 2.11.1* onwards you can turn this
+off by setting the boolean parameter to false, as shown below:
+
+[source,java]
+-------------------------------------------------
+from("file:target/in")
+ .split(stax(Record.class, false)).streaming()
+ .to("mock:records");
+-------------------------------------------------
+
+[[StAX-ThepreviousexamplewithXMLDSL]]
+The previous example with XML DSL
++++++++++++++++++++++++++++++++++
+
+The example above could be implemented as follows in XML DSL
+
+[[StAX-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/8a4dc407/docs/user-manual/en/SUMMARY.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index 6f2d196..c1c2329 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -258,6 +258,7 @@
* [SQL](sql.adoc)
* [SQL-Stored](sql-stored.adoc)
* [SSH](ssh.adoc)
+ * [StAX](stax.adoc)
* [Telegram](telegram.adoc)
* [Twitter](twitter.adoc)
* [Websocket](websocket.adoc)
[2/3] camel git commit: Added camel-stomp docs to Gitbook
Posted by ac...@apache.org.
Added camel-stomp docs to Gitbook
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/ca0215d4
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/ca0215d4
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/ca0215d4
Branch: refs/heads/master
Commit: ca0215d487560a1b47b77ca27346cc18ceb329cd
Parents: 8a4dc40
Author: Andrea Cosentino <an...@gmail.com>
Authored: Wed Jun 8 15:40:36 2016 +0200
Committer: Andrea Cosentino <an...@gmail.com>
Committed: Wed Jun 8 15:40:36 2016 +0200
----------------------------------------------------------------------
components/camel-stomp/src/main/docs/stomp.adoc | 143 +++++++++++++++++++
docs/user-manual/en/SUMMARY.md | 1 +
2 files changed, 144 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/ca0215d4/components/camel-stomp/src/main/docs/stomp.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stomp/src/main/docs/stomp.adoc b/components/camel-stomp/src/main/docs/stomp.adoc
new file mode 100644
index 0000000..7278411
--- /dev/null
+++ b/components/camel-stomp/src/main/docs/stomp.adoc
@@ -0,0 +1,143 @@
+[[Stomp-StompComponent]]
+Stomp Component
+~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.12*
+
+The *stomp:* component is used for communicating with
+http://stomp.github.io/[Stomp] compliant message brokers, like
+http://activemq.apache.org[Apache ActiveMQ] or
+http://activemq.apache.org/apollo/[ActiveMQ Apollo]
+
+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-stomp</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+[[Stomp-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+---------------------------------
+stomp:queue:destination[?options]
+---------------------------------
+
+Where *destination* is the name of the queue.
+
+[[Stomp-Options]]
+Options
+^^^^^^^
+
+
+// component options: START
+The Stomp component supports 5 options which are listed below.
+
+
+
+{% raw %}
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| configuration | StompConfiguration | To use the shared stomp configuration
+| brokerURL | String | The URI of the Stomp broker to connect to
+| login | String | The username
+| passcode | String | The password
+| host | String | The virtual host
+|=======================================================================
+{% endraw %}
+// component options: END
+
+
+
+// endpoint options: START
+The Stomp component supports 10 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| destination | common | | String | *Required* Name of the queue
+| brokerURL | common | tcp://localhost:61613 | String | *Required* The URI of the Stomp broker to connect to
+| host | common | | String | The virtual host name
+| login | common | | String | The username
+| passcode | common | | String | The password
+| 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).
+| sslContextParameters | security | | SSLContextParameters | To configure security using SSLContextParameters
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+You can append query options to the URI in the following format,
+`?option=value&option=value&...`
+
+[[Stomp-Samples]]
+Samples
+^^^^^^^
+
+Sending messages:
+
+[source,java]
+------------------------------------------
+from("direct:foo").to("stomp:queue:test");
+------------------------------------------
+
+Consuming messages:
+
+[source,java]
+------------------------------------------------------------------------------
+from("stomp:queue:test").transform(body().convertToString()).to("mock:result")
+------------------------------------------------------------------------------
+
+[[Stomp-Endpoints]]
+Endpoints
+~~~~~~~~~
+
+Camel supports the link:message-endpoint.html[Message Endpoint] pattern
+using the
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html[Endpoint]
+interface. Endpoints are usually created by a
+link:component.html[Component] and Endpoints are usually referred to in
+the link:dsl.html[DSL] via their link:uris.html[URIs].
+
+From an Endpoint you can use the following methods
+
+*
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()[createProducer()]
+will create a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Producer.html[Producer]
+for sending message exchanges to the endpoint
+*
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createConsumer(org.apache.camel.Processor)[createConsumer()]
+implements the link:event-driven-consumer.html[Event Driven Consumer]
+pattern for consuming message exchanges from the endpoint via a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html[Processor]
+when creating a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Consumer.html[Consumer]
+*
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createPollingConsumer()[createPollingConsumer()]
+implements the link:polling-consumer.html[Polling Consumer] pattern for
+consuming message exchanges from the endpoint via a
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/PollingConsumer.html[PollingConsumer]
+
+[[Stomp-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:message-endpoint.html[Message Endpoint] pattern
+* link:uris.html[URIs]
+* link:writing-components.html[Writing Components]
+
http://git-wip-us.apache.org/repos/asf/camel/blob/ca0215d4/docs/user-manual/en/SUMMARY.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index c1c2329..2d0a2d1 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -259,6 +259,7 @@
* [SQL-Stored](sql-stored.adoc)
* [SSH](ssh.adoc)
* [StAX](stax.adoc)
+ * [Stomp](stomp.adoc)
* [Telegram](telegram.adoc)
* [Twitter](twitter.adoc)
* [Websocket](websocket.adoc)
[3/3] camel git commit: Added camel-stream docs to Gitbook
Posted by ac...@apache.org.
Added camel-stream docs to Gitbook
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/60e042ae
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/60e042ae
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/60e042ae
Branch: refs/heads/master
Commit: 60e042ae7d961bf9105bcffb901270703f1d87d5
Parents: ca0215d
Author: Andrea Cosentino <an...@gmail.com>
Authored: Wed Jun 8 15:48:01 2016 +0200
Committer: Andrea Cosentino <an...@gmail.com>
Committed: Wed Jun 8 15:48:01 2016 +0200
----------------------------------------------------------------------
.../camel-stream/src/main/docs/stream.adoc | 150 +++++++++++++++++++
docs/user-manual/en/SUMMARY.md | 1 +
2 files changed, 151 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/60e042ae/components/camel-stream/src/main/docs/stream.adoc
----------------------------------------------------------------------
diff --git a/components/camel-stream/src/main/docs/stream.adoc b/components/camel-stream/src/main/docs/stream.adoc
new file mode 100644
index 0000000..8a6d563
--- /dev/null
+++ b/components/camel-stream/src/main/docs/stream.adoc
@@ -0,0 +1,150 @@
+[[Stream-StreamComponent]]
+Stream Component
+~~~~~~~~~~~~~~~~
+
+The *stream:* component provides access to the `System.in`, `System.out`
+and `System.err` streams as well as allowing streaming of file and URL.
+
+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-stream</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+[[Stream-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+-----------------------
+stream:in[?options]
+stream:out[?options]
+stream:err[?options]
+stream:header[?options]
+-----------------------
+
+In addition, the `file` and `url` endpoint URIs are supported:
+
+[source,java]
+---------------------------------
+stream:file?fileName=/foo/bar.txt
+stream:url[?options]
+---------------------------------
+
+If the `stream:header` URI is specified, the `stream` header is used to
+find the stream to write to. This option is available only for stream
+producers (that is, it cannot appear in `from()`).
+
+You can append query options to the URI in the following format,
+`?option=value&option=value&...`
+
+[[Stream-Options]]
+Options
+^^^^^^^
+
+
+// component options: START
+The Stream component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Stream component supports 18 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| url | common | | String | *Required* When using the stream:url URI format this option specifies the URL to stream to/from. The input/output stream will be opened using the JDK URLConnection facility.
+| encoding | common | | String | You can configure the encoding (is a charset name) to use text-based streams (for example message body is a String object). If not provided Camel uses the JVM default Charset.
+| fileName | common | | String | When using the stream:file URI format this option specifies the filename to stream to/from.
+| 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.
+| groupLines | consumer | | int | To group X number of lines in the consumer. For example to group 10 lines and therefore only spit out an Exchange with 10 lines instead of 1 Exchange per line.
+| groupStrategy | consumer | | GroupStrategy | Allows to use a custom GroupStrategy to control how to group lines.
+| initialPromptDelay | consumer | 2000 | long | Initial delay in milliseconds before showing the message prompt. This delay occurs only once. Can be used during system startup to avoid message prompts being written while other logging is done to the system out.
+| promptDelay | consumer | | long | Optional delay in milliseconds before showing the message prompt.
+| promptMessage | consumer | | String | Message prompt to use when reading from stream:in; for example you could set this to Enter a command:
+| retry | consumer | false | boolean | Will retry opening the file if it's overwritten somewhat like tail --retry
+| scanStream | consumer | false | boolean | To be used for continuously reading a stream such as the unix tail command.
+| scanStreamDelay | consumer | | long | Delay in milliseconds between read attempts when using scanStream.
+| 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.
+| autoCloseCount | producer | | int | Number of messages to process before closing stream on Producer side. Never close stream by default (only when Producer is stopped). If more messages are sent the stream is reopened for another autoCloseCount batch.
+| closeOnDone | producer | false | boolean | This option is used in combination with Splitter and streaming to the same file. The idea is to keep the stream open and only close when the Splitter is done to improve performance. Mind this requires that you only stream to the same file and not 2 or more files.
+| delay | producer | | long | Initial delay in milliseconds before producing the stream.
+| 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
+
+
+[[Stream-Messagecontent]]
+Message content
+^^^^^^^^^^^^^^^
+
+The *stream:* component supports either `String` or `byte[]` for writing
+to streams. Just add either `String` or `byte[]` content to the
+`message.in.body`. Messages sent to the *stream:* producer in binary
+mode are not followed by the newline character (as opposed to the
+`String` messages). Message with `null` body will not be appended to the
+output stream. +
+ The special `stream:header` URI is used for custom output streams. Just
+add a `java.io.OutputStream` object to `message.in.header` in the key
+`header`. +
+ See samples for an example.
+
+[[Stream-Samples]]
+Samples
+^^^^^^^
+
+In the following sample we route messages from the `direct:in` endpoint
+to the `System.out` stream:
+
+[source,java]
+---------------------------------------------------------------
+// Route messages to the standard output.
+from("direct:in").to("stream:out");
+
+// Send String payload to the standard output.
+// Message will be followed by the newline.
+template.sendBody("direct:in", "Hello Text World");
+
+// Send byte[] payload to the standard output.
+// No newline will be added after the message.
+template.sendBody("direct:in", "Hello Bytes World".getBytes());
+---------------------------------------------------------------
+
+The following sample demonstrates how the header type can be used to
+determine which stream to use. In the sample we use our own output
+stream, `MyOutputStream`.
+
+The following sample demonstrates how to continuously read a file stream
+(analogous to the UNIX `tail` command):
+
+[source,java]
+------------------------------------------------------------------------------------------------------------------------------------
+from("stream:file?fileName=/server/logs/server.log&scanStream=true&scanStreamDelay=1000").to("bean:logService?method=parseLogLine");
+------------------------------------------------------------------------------------------------------------------------------------
+
+One gotcha with scanStream (pre Camel 2.7) or scanStream + retry is the
+file will be re-opened and scanned with each iteration of
+scanStreamDelay. Until NIO2 is available we cannot reliably detect when
+a file is deleted/recreated.
+
+[[Stream-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/60e042ae/docs/user-manual/en/SUMMARY.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index 2d0a2d1..bec8f80 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -260,6 +260,7 @@
* [SSH](ssh.adoc)
* [StAX](stax.adoc)
* [Stomp](stomp.adoc)
+ * [Stream](stream.adoc)
* [Telegram](telegram.adoc)
* [Twitter](twitter.adoc)
* [Websocket](websocket.adoc)