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:04:15 UTC
[51/51] [partial] camel git commit: CAMEL-9541: Use -component as
suffix for component docs.
CAMEL-9541: Use -component as suffix for component docs.
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/9c0b7baf
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/9c0b7baf
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/9c0b7baf
Branch: refs/heads/master
Commit: 9c0b7baf33fd8614611c596adc3618e6ff93cff4
Parents: 10cf614
Author: Claus Ibsen <da...@apache.org>
Authored: Tue Aug 16 10:03:08 2016 +0200
Committer: Claus Ibsen <da...@apache.org>
Committed: Tue Aug 16 10:03:08 2016 +0200
----------------------------------------------------------------------
camel-core/src/main/docs/bean-component.adoc | 160 ++
camel-core/src/main/docs/bean.adoc | 160 --
camel-core/src/main/docs/binding-component.adoc | 124 ++
camel-core/src/main/docs/binding.adoc | 124 --
camel-core/src/main/docs/browse-component.adoc | 88 ++
camel-core/src/main/docs/browse.adoc | 88 --
camel-core/src/main/docs/class-component.adoc | 132 ++
camel-core/src/main/docs/class.adoc | 132 --
.../src/main/docs/controlbus-component.adoc | 211 +++
camel-core/src/main/docs/controlbus.adoc | 211 ---
.../src/main/docs/dataformat-component.adoc | 88 ++
camel-core/src/main/docs/dataformat.adoc | 88 --
camel-core/src/main/docs/dataset-component.adoc | 239 +++
camel-core/src/main/docs/dataset.adoc | 239 ---
camel-core/src/main/docs/direct-component.adoc | 119 ++
.../src/main/docs/direct-vm-component.adoc | 140 ++
camel-core/src/main/docs/direct-vm.adoc | 140 --
camel-core/src/main/docs/direct.adoc | 119 --
camel-core/src/main/docs/file-component.adoc | 1251 +++++++++++++++
camel-core/src/main/docs/file.adoc | 1251 ---------------
.../src/main/docs/language-component.adoc | 144 ++
camel-core/src/main/docs/language.adoc | 144 --
camel-core/src/main/docs/log-component.adoc | 302 ++++
camel-core/src/main/docs/log.adoc | 302 ----
camel-core/src/main/docs/mock-component.adoc | 515 +++++++
camel-core/src/main/docs/mock.adoc | 515 -------
.../src/main/docs/properties-component.adoc | 1045 +++++++++++++
camel-core/src/main/docs/properties.adoc | 1045 -------------
camel-core/src/main/docs/ref-component.adoc | 108 ++
camel-core/src/main/docs/ref.adoc | 108 --
.../src/main/docs/rest-api-component.adoc | 792 ++++++++++
camel-core/src/main/docs/rest-api.adoc | 792 ----------
camel-core/src/main/docs/rest-component.adoc | 124 ++
camel-core/src/main/docs/rest.adoc | 124 --
.../src/main/docs/scheduler-component.adoc | 181 +++
camel-core/src/main/docs/scheduler.adoc | 181 ---
camel-core/src/main/docs/seda-component.adoc | 260 ++++
camel-core/src/main/docs/seda.adoc | 260 ----
camel-core/src/main/docs/stub-component.adoc | 103 ++
camel-core/src/main/docs/stub.adoc | 103 --
camel-core/src/main/docs/test-component.adoc | 123 ++
camel-core/src/main/docs/test.adoc | 123 --
camel-core/src/main/docs/timer-component.adoc | 177 +++
camel-core/src/main/docs/timer.adoc | 177 ---
.../src/main/docs/validator-component.adoc | 129 ++
camel-core/src/main/docs/validator.adoc | 129 --
camel-core/src/main/docs/vm-component.adoc | 147 ++
camel-core/src/main/docs/vm.adoc | 147 --
camel-core/src/main/docs/xslt-component.adoc | 455 ++++++
camel-core/src/main/docs/xslt.adoc | 455 ------
.../src/main/docs/ahc-ws-component.adoc | 165 ++
.../camel-ahc-ws/src/main/docs/ahc-ws.adoc | 165 --
.../camel-ahc/src/main/docs/ahc-component.adoc | 467 ++++++
components/camel-ahc/src/main/docs/ahc.adoc | 467 ------
.../src/main/docs/amqp-component.adoc | 369 +++++
components/camel-amqp/src/main/docs/amqp.adoc | 369 -----
.../src/main/docs/apns-component.adoc | 313 ++++
components/camel-apns/src/main/docs/apns.adoc | 313 ----
.../src/main/docs/atmos-component.adoc | 72 +
components/camel-atmos/src/main/docs/atmos.adoc | 72 -
.../docs/atmosphere-websocket-component.adoc | 185 +++
.../src/main/docs/atmosphere-websocket.adoc | 185 ---
.../src/main/docs/atom-component.adoc | 148 ++
components/camel-atom/src/main/docs/atom.adoc | 148 --
.../src/main/docs/avro-component.adoc | 312 ++++
components/camel-avro/src/main/docs/avro.adoc | 312 ----
.../src/main/docs/aws-cw-component.adoc | 165 ++
components/camel-aws/src/main/docs/aws-cw.adoc | 165 --
.../src/main/docs/aws-ddb-component.adoc | 350 +++++
components/camel-aws/src/main/docs/aws-ddb.adoc | 350 -----
.../src/main/docs/aws-ddbstream-component.adoc | 197 +++
.../camel-aws/src/main/docs/aws-ddbstream.adoc | 197 ---
.../src/main/docs/aws-ec2-component.adoc | 129 ++
components/camel-aws/src/main/docs/aws-ec2.adoc | 129 --
.../src/main/docs/aws-kinesis-component.adoc | 211 +++
.../camel-aws/src/main/docs/aws-kinesis.adoc | 211 ---
.../src/main/docs/aws-s3-component.adoc | 299 ++++
components/camel-aws/src/main/docs/aws-s3.adoc | 299 ----
.../src/main/docs/aws-sdb-component.adoc | 237 +++
components/camel-aws/src/main/docs/aws-sdb.adoc | 237 ---
.../src/main/docs/aws-ses-component.adoc | 168 ++
components/camel-aws/src/main/docs/aws-ses.adoc | 168 --
.../src/main/docs/aws-sns-component.adoc | 162 ++
components/camel-aws/src/main/docs/aws-sns.adoc | 162 --
.../src/main/docs/aws-sqs-component.adoc | 245 +++
components/camel-aws/src/main/docs/aws-sqs.adoc | 245 ---
.../src/main/docs/aws-swf-component.adoc | 245 +++
components/camel-aws/src/main/docs/aws-swf.adoc | 245 ---
.../src/main/docs/bean-validator-component.adoc | 258 ++++
.../src/main/docs/bean-validator.adoc | 258 ----
.../src/main/docs/beanstalk-component.adoc | 231 +++
.../src/main/docs/beanstalk.adoc | 231 ---
.../camel-box/src/main/docs/box-component.adoc | 791 ++++++++++
components/camel-box/src/main/docs/box.adoc | 791 ----------
.../src/main/docs/braintree-component.adoc | 775 ++++++++++
.../src/main/docs/braintree.adoc | 775 ----------
.../src/main/docs/cache-component.adoc | 497 ++++++
components/camel-cache/src/main/docs/cache.adoc | 497 ------
.../src/main/docs/cql-component.adoc | 233 +++
.../camel-cassandraql/src/main/docs/cql.adoc | 233 ---
.../main/docs/chronicle-engine-component.adoc | 23 +
.../src/main/docs/chronicle-engine.adoc | 23 -
.../src/main/docs/chunk-component.adoc | 194 +++
components/camel-chunk/src/main/docs/chunk.adoc | 194 ---
.../src/main/docs/cm-sms-component.adoc | 66 +
.../camel-cm-sms/src/main/docs/cm-sms.adoc | 66 -
.../src/main/docs/cmis-component.adoc | 127 ++
components/camel-cmis/src/main/docs/cmis.adoc | 127 --
.../src/main/docs/coap-component.adoc | 54 +
components/camel-coap/src/main/docs/coap.adoc | 54 -
.../src/main/docs/cometd-component.adoc | 207 +++
.../camel-cometd/src/main/docs/cometd.adoc | 207 ---
.../src/main/docs/consul-component.adoc | 112 ++
.../camel-consul/src/main/docs/consul.adoc | 112 --
.../src/main/docs/context-component.adoc | 174 +++
.../camel-context/src/main/docs/context.adoc | 174 ---
.../src/main/docs/couchdb-component.adoc | 133 ++
.../camel-couchdb/src/main/docs/couchdb.adoc | 133 --
.../src/main/docs/crypto-component.adoc | 609 ++++++++
.../camel-crypto/src/main/docs/crypto.adoc | 609 --------
.../camel-cxf/src/main/docs/cxf-component.adoc | 934 ++++++++++++
components/camel-cxf/src/main/docs/cxf.adoc | 934 ------------
.../src/main/docs/cxfrs-component.adoc | 368 +++++
components/camel-cxf/src/main/docs/cxfrs.adoc | 368 -----
.../src/main/docs/disruptor-component.adoc | 323 ++++
.../src/main/docs/disruptor.adoc | 323 ----
.../camel-dns/src/main/docs/dns-component.adoc | 160 ++
components/camel-dns/src/main/docs/dns.adoc | 160 --
.../src/main/docs/docker-component.adoc | 210 +++
.../camel-docker/src/main/docs/docker.adoc | 210 ---
.../src/main/docs/dozer-component.adoc | 286 ++++
components/camel-dozer/src/main/docs/dozer.adoc | 286 ----
.../src/main/docs/dropbox-component.adoc | 385 +++++
.../camel-dropbox/src/main/docs/dropbox.adoc | 385 -----
.../src/main/docs/ehcache-component.adoc | 198 +++
.../camel-ehcache/src/main/docs/ehcache.adoc | 198 ---
.../camel-ejb/src/main/docs/ejb-component.adoc | 222 +++
components/camel-ejb/src/main/docs/ejb.adoc | 222 ---
.../src/main/docs/elasticsearch-component.adoc | 182 +++
.../src/main/docs/elasticsearch.adoc | 182 ---
.../src/main/docs/elsql-component.adoc | 247 +++
components/camel-elsql/src/main/docs/elsql.adoc | 247 ---
.../src/main/docs/etcd-component.adoc | 59 +
components/camel-etcd/src/main/docs/etcd.adoc | 59 -
.../src/main/docs/eventadmin-component.adoc | 76 +
.../src/main/docs/eventadmin.adoc | 76 -
.../src/main/docs/exec-component.adoc | 261 ++++
components/camel-exec/src/main/docs/exec.adoc | 261 ----
.../src/main/docs/facebook-component.adoc | 346 +++++
.../camel-facebook/src/main/docs/facebook.adoc | 346 -----
.../src/main/docs/flatpack-component.adoc | 298 ++++
.../camel-flatpack/src/main/docs/flatpack.adoc | 298 ----
.../src/main/docs/flink-component.adoc | 155 ++
components/camel-flink/src/main/docs/flink.adoc | 155 --
.../camel-fop/src/main/docs/fop-component.adoc | 171 +++
components/camel-fop/src/main/docs/fop.adoc | 171 ---
.../src/main/docs/freemarker-component.adoc | 247 +++
.../src/main/docs/freemarker.adoc | 247 ---
.../camel-ftp/src/main/docs/ftp-component.adoc | 842 ++++++++++
components/camel-ftp/src/main/docs/ftp.adoc | 842 ----------
.../src/main/docs/ganglia-component.adoc | 172 +++
.../camel-ganglia/src/main/docs/ganglia.adoc | 172 ---
.../src/main/docs/geocoder-component.adoc | 167 ++
.../camel-geocoder/src/main/docs/geocoder.adoc | 167 --
.../camel-git/src/main/docs/git-component.adoc | 118 ++
components/camel-git/src/main/docs/git.adoc | 118 --
.../src/main/docs/github-component.adoc | 122 ++
.../camel-github/src/main/docs/github.adoc | 122 --
.../main/docs/google-calendar-component.adoc | 174 +++
.../src/main/docs/google-calendar.adoc | 174 ---
.../src/main/docs/google-drive-component.adoc | 175 +++
.../src/main/docs/google-drive.adoc | 175 ---
.../src/main/docs/google-mail-component.adoc | 170 +++
.../src/main/docs/google-mail.adoc | 170 ---
.../src/main/docs/gora-component.adoc | 265 ++++
components/camel-gora/src/main/docs/gora.adoc | 265 ----
.../src/main/docs/grape-component.adoc | 250 +++
components/camel-grape/src/main/docs/grape.adoc | 250 ---
.../src/main/docs/guava-eventbus-component.adoc | 215 +++
.../src/main/docs/guava-eventbus.adoc | 215 ---
.../src/main/docs/hazelcast-component.adoc | 1402 +++++++++++++++++
.../src/main/docs/hazelcast.adoc | 1402 -----------------
.../src/main/docs/hbase-component.adoc | 519 +++++++
components/camel-hbase/src/main/docs/hbase.adoc | 519 -------
.../src/main/docs/hdfs-component.adoc | 248 +++
components/camel-hdfs/src/main/docs/hdfs.adoc | 248 ---
.../src/main/docs/hdfs2-component.adoc | 294 ++++
components/camel-hdfs2/src/main/docs/hdfs2.adoc | 294 ----
.../src/main/docs/hipchat-component.adoc | 204 +++
.../camel-hipchat/src/main/docs/hipchat.adoc | 204 ---
.../src/main/docs/http-component.adoc | 572 +++++++
components/camel-http/src/main/docs/http.adoc | 572 -------
.../src/main/docs/http4-component.adoc | 699 +++++++++
components/camel-http4/src/main/docs/http4.adoc | 699 ---------
.../src/main/docs/ibatis-component.adoc | 260 ++++
.../camel-ibatis/src/main/docs/ibatis.adoc | 260 ----
.../src/main/docs/infinispan-component.adoc | 191 +++
.../src/main/docs/infinispan.adoc | 191 ---
.../src/main/docs/influxdb-component.adoc | 117 ++
.../camel-influxdb/src/main/docs/influxdb.adoc | 117 --
.../camel-irc/src/main/docs/irc-component.adoc | 212 +++
components/camel-irc/src/main/docs/irc.adoc | 212 ---
.../src/main/docs/ironmq-component.adoc | 157 ++
.../camel-ironmq/src/main/docs/ironmq.adoc | 157 --
.../src/main/docs/javaspace-component.adoc | 151 ++
.../src/main/docs/javaspace.adoc | 151 --
.../src/main/docs/jbpm-component.adoc | 162 ++
components/camel-jbpm/src/main/docs/jbpm.adoc | 162 --
.../src/main/docs/jcache-component.adoc | 55 +
.../camel-jcache/src/main/docs/jcache.adoc | 55 -
.../src/main/docs/jclouds-component.adoc | 383 +++++
.../camel-jclouds/src/main/docs/jclouds.adoc | 383 -----
.../camel-jcr/src/main/docs/jcr-component.adoc | 130 ++
components/camel-jcr/src/main/docs/jcr.adoc | 130 --
.../src/main/docs/jdbc-component.adoc | 260 ++++
components/camel-jdbc/src/main/docs/jdbc.adoc | 260 ----
.../src/main/docs/jetty-component.adoc | 757 +++++++++
.../camel-jetty9/src/main/docs/jetty.adoc | 757 ---------
.../src/main/docs/jgroups-component.adoc | 284 ++++
.../camel-jgroups/src/main/docs/jgroups.adoc | 284 ----
.../src/main/docs/jing-component.adoc | 90 ++
components/camel-jing/src/main/docs/jing.adoc | 90 --
.../src/main/docs/jira-component.adoc | 112 ++
components/camel-jira/src/main/docs/jira.adoc | 112 --
.../camel-jms/src/main/docs/jms-component.adoc | 1437 ++++++++++++++++++
components/camel-jms/src/main/docs/jms.adoc | 1437 ------------------
.../camel-jmx/src/main/docs/jmx-component.adoc | 1065 +++++++++++++
components/camel-jmx/src/main/docs/jmx.adoc | 1065 -------------
.../src/main/docs/jolt-component.adoc | 127 ++
components/camel-jolt/src/main/docs/jolt.adoc | 127 --
.../camel-jpa/src/main/docs/jpa-component.adoc | 393 +++++
components/camel-jpa/src/main/docs/jpa.adoc | 393 -----
.../camel-jsch/src/main/docs/scp-component.adoc | 121 ++
components/camel-jsch/src/main/docs/scp.adoc | 121 --
.../src/main/docs/jt400-component.adoc | 217 +++
components/camel-jt400/src/main/docs/jt400.adoc | 217 ---
.../src/main/docs/kafka-component.adoc | 317 ++++
components/camel-kafka/src/main/docs/kafka.adoc | 317 ----
.../src/main/docs/kestrel-component.adoc | 287 ++++
.../camel-kestrel/src/main/docs/kestrel.adoc | 287 ----
.../src/main/docs/krati-component.adoc | 222 +++
components/camel-krati/src/main/docs/krati.adoc | 222 ---
.../src/main/docs/kubernetes-component.adoc | 179 +++
.../src/main/docs/kubernetes.adoc | 179 ---
.../src/main/docs/ldap-component.adoc | 349 +++++
components/camel-ldap/src/main/docs/ldap.adoc | 349 -----
.../src/main/docs/linkedin-component.adoc | 711 +++++++++
.../src/main/docs/linkedin.adoc | 711 ---------
.../src/main/docs/lucene-component.adoc | 254 ++++
.../camel-lucene/src/main/docs/lucene.adoc | 254 ----
.../src/main/docs/lumberjack-component.adoc | 109 ++
.../src/main/docs/lumberjack.adoc | 109 --
.../src/main/docs/imap-component.adoc | 142 ++
components/camel-mail/src/main/docs/imap.adoc | 142 --
.../src/main/docs/imaps-component.adoc | 142 ++
components/camel-mail/src/main/docs/imaps.adoc | 142 --
.../src/main/docs/pop3-component.adoc | 142 ++
components/camel-mail/src/main/docs/pop3.adoc | 142 --
.../src/main/docs/pop3s-component.adoc | 142 ++
components/camel-mail/src/main/docs/pop3s.adoc | 142 --
.../src/main/docs/smtp-component.adoc | 142 ++
components/camel-mail/src/main/docs/smtp.adoc | 142 --
.../src/main/docs/smtps-component.adoc | 142 ++
components/camel-mail/src/main/docs/smtps.adoc | 142 --
.../src/main/docs/metrics-component.adoc | 569 +++++++
.../camel-metrics/src/main/docs/metrics.adoc | 569 -------
.../src/main/docs/mina-component.adoc | 368 +++++
components/camel-mina/src/main/docs/mina.adoc | 368 -----
.../src/main/docs/mina2-component.adoc | 305 ++++
components/camel-mina2/src/main/docs/mina2.adoc | 305 ----
.../src/main/docs/mllp-component.adoc | 180 +++
components/camel-mllp/src/main/docs/mllp.adoc | 180 ---
.../src/main/docs/gridfs-component.adoc | 222 +++
.../src/main/docs/gridfs.adoc | 222 ---
.../src/main/docs/mongodb-component.adoc | 852 +++++++++++
.../camel-mongodb/src/main/docs/mongodb.adoc | 852 -----------
.../src/main/docs/mqtt-component.adoc | 168 ++
components/camel-mqtt/src/main/docs/mqtt.adoc | 168 --
.../camel-msv/src/main/docs/msv-component.adoc | 121 ++
components/camel-msv/src/main/docs/msv.adoc | 121 --
.../src/main/docs/mustache-component.adoc | 193 +++
.../camel-mustache/src/main/docs/mustache.adoc | 193 ---
.../src/main/docs/mvel-component.adoc | 185 +++
components/camel-mvel/src/main/docs/mvel.adoc | 185 ---
.../src/main/docs/mybatis-component.adoc | 430 ++++++
.../camel-mybatis/src/main/docs/mybatis.adoc | 430 ------
.../src/main/docs/nagios-component.adoc | 154 ++
.../camel-nagios/src/main/docs/nagios.adoc | 154 --
.../src/main/docs/nats-component.adoc | 105 ++
components/camel-nats/src/main/docs/nats.adoc | 105 --
.../src/main/docs/netty-http-component.adoc | 599 ++++++++
.../src/main/docs/netty-http.adoc | 599 --------
.../src/main/docs/netty-component.adoc | 714 +++++++++
components/camel-netty/src/main/docs/netty.adoc | 714 ---------
.../src/main/docs/netty4-http-component.adoc | 602 ++++++++
.../src/main/docs/netty4-http.adoc | 602 --------
.../src/main/docs/netty4-component.adoc | 780 ++++++++++
.../camel-netty4/src/main/docs/netty4.adoc | 780 ----------
.../src/main/docs/olingo2-component.adoc | 278 ++++
.../src/main/docs/olingo2.adoc | 278 ----
.../src/main/docs/openshift-component.adoc | 171 +++
.../src/main/docs/openshift.adoc | 171 ---
.../src/main/docs/optaplanner-component.adoc | 153 ++
.../src/main/docs/optaplanner.adoc | 153 --
.../src/main/docs/paho-component.adoc | 198 +++
components/camel-paho/src/main/docs/paho.adoc | 198 ---
.../src/main/docs/paxlogging-component.adoc | 102 ++
.../src/main/docs/paxlogging.adoc | 102 --
.../camel-pdf/src/main/docs/pdf-component.adoc | 103 ++
components/camel-pdf/src/main/docs/pdf.adoc | 103 --
.../src/main/docs/pgevent-component.adoc | 78 +
.../camel-pgevent/src/main/docs/pgevent.adoc | 78 -
.../src/main/docs/lpr-component.adoc | 151 ++
components/camel-printer/src/main/docs/lpr.adoc | 151 --
.../src/main/docs/quartz-component.adoc | 270 ++++
.../camel-quartz/src/main/docs/quartz.adoc | 270 ----
.../src/main/docs/quartz2-component.adoc | 339 +++++
.../camel-quartz2/src/main/docs/quartz2.adoc | 339 -----
.../src/main/docs/quickfix-component.adoc | 607 ++++++++
.../camel-quickfix/src/main/docs/quickfix.adoc | 607 --------
.../src/main/docs/rabbitmq-component.adoc | 258 ++++
.../camel-rabbitmq/src/main/docs/rabbitmq.adoc | 258 ----
.../src/main/docs/restlet-component.adoc | 396 +++++
.../camel-restlet/src/main/docs/restlet.adoc | 396 -----
.../camel-rmi/src/main/docs/rmi-component.adoc | 123 ++
components/camel-rmi/src/main/docs/rmi.adoc | 123 --
.../src/main/docs/routebox-component.adoc | 281 ++++
.../camel-routebox/src/main/docs/routebox.adoc | 281 ----
.../camel-rss/src/main/docs/rss-component.adoc | 167 ++
components/camel-rss/src/main/docs/rss.adoc | 167 --
.../src/main/docs/salesforce-component.adoc | 358 +++++
.../src/main/docs/salesforce.adoc | 358 -----
.../src/main/docs/sap-netweaver-component.adoc | 192 +++
.../src/main/docs/sap-netweaver.adoc | 192 ---
.../src/main/docs/xquery-component.adoc | 279 ++++
.../camel-saxon/src/main/docs/xquery.adoc | 279 ----
.../src/main/docs/schematron-component.adoc | 182 +++
.../src/main/docs/schematron.adoc | 182 ---
.../src/main/docs/servicenow-component.adoc | 156 ++
.../src/main/docs/servicenow.adoc | 156 --
.../src/main/docs/servlet-component.adoc | 248 +++
.../camel-servlet/src/main/docs/servlet.adoc | 248 ---
.../camel-sip/src/main/docs/sip-component.adoc | 213 +++
components/camel-sip/src/main/docs/sip.adoc | 213 ---
.../src/main/docs/sjms-batch-component.adoc | 177 +++
.../camel-sjms/src/main/docs/sjms-batch.adoc | 177 ---
.../src/main/docs/sjms-component.adoc | 585 +++++++
components/camel-sjms/src/main/docs/sjms.adoc | 585 -------
.../src/main/docs/slack-component.adoc | 134 ++
components/camel-slack/src/main/docs/slack.adoc | 134 --
.../src/main/docs/smpp-component.adoc | 672 ++++++++
components/camel-smpp/src/main/docs/smpp.adoc | 672 --------
.../src/main/docs/snmp-component.adoc | 189 +++
components/camel-snmp/src/main/docs/snmp.adoc | 189 ---
.../src/main/docs/solr-component.adoc | 217 +++
components/camel-solr/src/main/docs/solr.adoc | 217 ---
.../src/main/docs/spark-rest-component.adoc | 193 +++
.../src/main/docs/spark-rest.adoc | 193 ---
.../src/main/docs/spark-component.adoc | 413 +++++
components/camel-spark/src/main/docs/spark.adoc | 413 -----
.../src/main/docs/splunk-component.adoc | 249 +++
.../camel-splunk/src/main/docs/splunk.adoc | 249 ---
.../src/main/docs/spring-batch-component.adoc | 278 ++++
.../src/main/docs/spring-batch.adoc | 278 ----
.../main/docs/spring-integration-component.adoc | 114 ++
.../src/main/docs/spring-integration.adoc | 114 --
.../src/main/docs/spring-ldap-component.adoc | 113 ++
.../src/main/docs/spring-ldap.adoc | 113 --
.../src/main/docs/spring-redis-component.adoc | 376 +++++
.../src/main/docs/spring-redis.adoc | 376 -----
.../src/main/docs/spring-ws-component.adoc | 588 +++++++
.../src/main/docs/spring-ws.adoc | 588 -------
.../src/main/docs/spring-event-component.adoc | 71 +
.../src/main/docs/spring-event.adoc | 71 -
.../camel-sql/src/main/docs/sql-component.adoc | 765 ++++++++++
.../src/main/docs/sql-stored-component.adoc | 141 ++
.../camel-sql/src/main/docs/sql-stored.adoc | 141 --
components/camel-sql/src/main/docs/sql.adoc | 765 ----------
.../camel-ssh/src/main/docs/ssh-component.adoc | 209 +++
components/camel-ssh/src/main/docs/ssh.adoc | 209 ---
.../src/main/docs/stax-component.adoc | 219 +++
components/camel-stax/src/main/docs/stax.adoc | 219 ---
.../src/main/docs/stomp-component.adoc | 145 ++
components/camel-stomp/src/main/docs/stomp.adoc | 145 --
.../src/main/docs/stream-component.adoc | 150 ++
.../camel-stream/src/main/docs/stream.adoc | 150 --
.../src/main/docs/telegram-component.adoc | 272 ++++
.../camel-telegram/src/main/docs/telegram.adoc | 272 ----
.../src/main/docs/twitter-component.adoc | 321 ++++
.../camel-twitter/src/main/docs/twitter.adoc | 321 ----
.../src/main/docs/undertow-component.adoc | 180 +++
.../camel-undertow/src/main/docs/undertow.adoc | 180 ---
.../src/main/docs/velocity-component.adoc | 277 ++++
.../camel-velocity/src/main/docs/velocity.adoc | 277 ----
.../src/main/docs/vertx-component.adoc | 112 ++
components/camel-vertx/src/main/docs/vertx.adoc | 112 --
.../src/main/docs/weather-component.adoc | 177 +++
.../camel-weather/src/main/docs/weather.adoc | 177 ---
.../src/main/docs/websocket-component.adoc | 250 +++
.../src/main/docs/websocket.adoc | 250 ---
.../src/main/docs/xmlrpc-component.adoc | 187 +++
.../camel-xmlrpc/src/main/docs/xmlrpc.adoc | 187 ---
.../src/main/docs/xmlsecurity-component.adoc | 762 ++++++++++
.../src/main/docs/xmlsecurity.adoc | 762 ----------
.../src/main/docs/xmpp-component.adoc | 165 ++
components/camel-xmpp/src/main/docs/xmpp.adoc | 165 --
.../src/main/docs/yammer-component.adoc | 371 +++++
.../camel-yammer/src/main/docs/yammer.adoc | 371 -----
.../src/main/docs/zookeeper-component.adoc | 266 ++++
.../src/main/docs/zookeeper.adoc | 266 ----
docs/user-manual/en/SUMMARY.md | 358 ++---
.../maven/packaging/ReadmeComponentMojo.java | 2 +-
412 files changed, 59145 insertions(+), 59145 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/bean-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/bean-component.adoc b/camel-core/src/main/docs/bean-component.adoc
new file mode 100644
index 0000000..fc8d348
--- /dev/null
+++ b/camel-core/src/main/docs/bean-component.adoc
@@ -0,0 +1,160 @@
+[[Bean-BeanComponent]]
+Bean Component
+~~~~~~~~~~~~~~
+
+The *bean:* component binds beans to Camel message exchanges.
+
+[[Bean-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+---------------------
+bean:beanID[?options]
+---------------------
+
+Where *beanID* can be any string which is used to look up the bean in
+the link:registry.html[Registry]
+
+[[Bean-Options]]
+Options
+^^^^^^^
+
+
+// component options: START
+The Bean component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Bean 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
+| beanName | producer | | String | *Required* Sets the name of the bean to invoke
+| method | producer | | String | Sets the name of the method to invoke on the bean
+| cache | advanced | false | boolean | If enabled Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange.
+| multiParameterArray | advanced | false | boolean | How to treat the parameters which are passed from the message body; if it is true the message body should be an array of parameters. Note: This option is used internally by Camel and is not intended for end users to use.
+| parameters | advanced | | Map | Used for configuring additional properties on the bean
+| 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
+
+
+You can append query options to the URI in the following format,
+`?option=value&option=value&...`
+
+[[Bean-Using]]
+Using
+^^^^^
+
+The object instance that is used to consume messages must be explicitly
+registered with the link:registry.html[Registry]. For example, if you
+are using Spring you must define the bean in the Spring configuration,
+`spring.xml`; or if you don't use Spring, by registering the bean in
+JNDI.
+
+Error formatting macro: snippet: java.lang.IndexOutOfBoundsException:
+Index: 20, Size: 20
+
+Once an endpoint has been registered, you can build Camel routes that
+use it to process exchanges.
+
+A *bean:* endpoint cannot be defined as the input to the route; i.e. you
+cannot consume from it, you can only route from some inbound message
+link:endpoint.html[Endpoint] to the bean endpoint as output. So consider
+using a *direct:* or *queue:* endpoint as the input.
+
+You can use the `createProxy()` methods on
+http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/bean/ProxyHelper.html[ProxyHelper]
+to create a proxy that will generate BeanExchanges and send them to any
+endpoint:
+
+And the same route using Spring DSL:
+
+[source,xml]
+----------------------------
+<route>
+ <from uri="direct:hello">
+ <to uri="bean:bye"/>
+</route>
+----------------------------
+
+[[Bean-Beanasendpoint]]
+Bean as endpoint
+^^^^^^^^^^^^^^^^
+
+Camel also supports invoking link:bean.html[Bean] as an Endpoint. In the
+route below:
+
+What happens is that when the exchange is routed to the `myBean` Camel
+will use the link:bean-binding.html[Bean Binding] to invoke the bean. +
+ The source for the bean is just a plain POJO:
+
+Camel will use link:bean-binding.html[Bean Binding] to invoke the
+`sayHello` method, by converting the Exchange's In body to the `String`
+type and storing the output of the method on the Exchange Out body.
+
+[[Bean-JavaDSLbeansyntax]]
+Java DSL bean syntax
+^^^^^^^^^^^^^^^^^^^^
+
+Java DSL comes with syntactic sugar for the link:bean.html[Bean]
+component. Instead of specifying the bean explicitly as the endpoint
+(i.e. `to("bean:beanName")`) you can use the following syntax:
+
+[source,java]
+-------------------------------------------------------
+// Send message to the bean endpoint
+// and invoke method resolved using Bean Binding.
+from("direct:start").beanRef("beanName");
+
+// Send message to the bean endpoint
+// and invoke given method.
+from("direct:start").beanRef("beanName", "methodName");
+-------------------------------------------------------
+
+Instead of passing name of the reference to the bean (so that Camel will
+lookup for it in the registry), you can specify the bean itself:
+
+[source,java]
+---------------------------------------------------------------
+// Send message to the given bean instance.
+from("direct:start").bean(new ExampleBean());
+
+// Explicit selection of bean method to be invoked.
+from("direct:start").bean(new ExampleBean(), "methodName");
+
+// Camel will create the instance of bean and cache it for you.
+from("direct:start").bean(ExampleBean.class);
+---------------------------------------------------------------
+
+[[Bean-BeanBinding]]
+Bean Binding
+^^^^^^^^^^^^
+
+How bean methods to be invoked are chosen (if they are not specified
+explicitly through the *method* parameter) and how parameter values are
+constructed from the link:message.html[Message] are all defined by the
+link:bean-binding.html[Bean Binding] mechanism which is used throughout
+all of the various link:bean-integration.html[Bean Integration]
+mechanisms in Camel.
+
+[[Bean-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+
+* link:class.html[Class] component
+* link:bean-binding.html[Bean Binding]
+* link:bean-integration.html[Bean Integration]
+
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/bean.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/bean.adoc b/camel-core/src/main/docs/bean.adoc
deleted file mode 100644
index fc8d348..0000000
--- a/camel-core/src/main/docs/bean.adoc
+++ /dev/null
@@ -1,160 +0,0 @@
-[[Bean-BeanComponent]]
-Bean Component
-~~~~~~~~~~~~~~
-
-The *bean:* component binds beans to Camel message exchanges.
-
-[[Bean-URIformat]]
-URI format
-^^^^^^^^^^
-
-[source,java]
----------------------
-bean:beanID[?options]
----------------------
-
-Where *beanID* can be any string which is used to look up the bean in
-the link:registry.html[Registry]
-
-[[Bean-Options]]
-Options
-^^^^^^^
-
-
-// component options: START
-The Bean component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The Bean 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
-| beanName | producer | | String | *Required* Sets the name of the bean to invoke
-| method | producer | | String | Sets the name of the method to invoke on the bean
-| cache | advanced | false | boolean | If enabled Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange.
-| multiParameterArray | advanced | false | boolean | How to treat the parameters which are passed from the message body; if it is true the message body should be an array of parameters. Note: This option is used internally by Camel and is not intended for end users to use.
-| parameters | advanced | | Map | Used for configuring additional properties on the bean
-| 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
-
-
-You can append query options to the URI in the following format,
-`?option=value&option=value&...`
-
-[[Bean-Using]]
-Using
-^^^^^
-
-The object instance that is used to consume messages must be explicitly
-registered with the link:registry.html[Registry]. For example, if you
-are using Spring you must define the bean in the Spring configuration,
-`spring.xml`; or if you don't use Spring, by registering the bean in
-JNDI.
-
-Error formatting macro: snippet: java.lang.IndexOutOfBoundsException:
-Index: 20, Size: 20
-
-Once an endpoint has been registered, you can build Camel routes that
-use it to process exchanges.
-
-A *bean:* endpoint cannot be defined as the input to the route; i.e. you
-cannot consume from it, you can only route from some inbound message
-link:endpoint.html[Endpoint] to the bean endpoint as output. So consider
-using a *direct:* or *queue:* endpoint as the input.
-
-You can use the `createProxy()` methods on
-http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/component/bean/ProxyHelper.html[ProxyHelper]
-to create a proxy that will generate BeanExchanges and send them to any
-endpoint:
-
-And the same route using Spring DSL:
-
-[source,xml]
-----------------------------
-<route>
- <from uri="direct:hello">
- <to uri="bean:bye"/>
-</route>
-----------------------------
-
-[[Bean-Beanasendpoint]]
-Bean as endpoint
-^^^^^^^^^^^^^^^^
-
-Camel also supports invoking link:bean.html[Bean] as an Endpoint. In the
-route below:
-
-What happens is that when the exchange is routed to the `myBean` Camel
-will use the link:bean-binding.html[Bean Binding] to invoke the bean. +
- The source for the bean is just a plain POJO:
-
-Camel will use link:bean-binding.html[Bean Binding] to invoke the
-`sayHello` method, by converting the Exchange's In body to the `String`
-type and storing the output of the method on the Exchange Out body.
-
-[[Bean-JavaDSLbeansyntax]]
-Java DSL bean syntax
-^^^^^^^^^^^^^^^^^^^^
-
-Java DSL comes with syntactic sugar for the link:bean.html[Bean]
-component. Instead of specifying the bean explicitly as the endpoint
-(i.e. `to("bean:beanName")`) you can use the following syntax:
-
-[source,java]
--------------------------------------------------------
-// Send message to the bean endpoint
-// and invoke method resolved using Bean Binding.
-from("direct:start").beanRef("beanName");
-
-// Send message to the bean endpoint
-// and invoke given method.
-from("direct:start").beanRef("beanName", "methodName");
--------------------------------------------------------
-
-Instead of passing name of the reference to the bean (so that Camel will
-lookup for it in the registry), you can specify the bean itself:
-
-[source,java]
----------------------------------------------------------------
-// Send message to the given bean instance.
-from("direct:start").bean(new ExampleBean());
-
-// Explicit selection of bean method to be invoked.
-from("direct:start").bean(new ExampleBean(), "methodName");
-
-// Camel will create the instance of bean and cache it for you.
-from("direct:start").bean(ExampleBean.class);
----------------------------------------------------------------
-
-[[Bean-BeanBinding]]
-Bean Binding
-^^^^^^^^^^^^
-
-How bean methods to be invoked are chosen (if they are not specified
-explicitly through the *method* parameter) and how parameter values are
-constructed from the link:message.html[Message] are all defined by the
-link:bean-binding.html[Bean Binding] mechanism which is used throughout
-all of the various link:bean-integration.html[Bean Integration]
-mechanisms in Camel.
-
-[[Bean-SeeAlso]]
-See Also
-^^^^^^^^
-
-* link:configuring-camel.html[Configuring Camel]
-* link:component.html[Component]
-* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
-* link:class.html[Class] component
-* link:bean-binding.html[Bean Binding]
-* link:bean-integration.html[Bean Integration]
-
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/binding-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/binding-component.adoc b/camel-core/src/main/docs/binding-component.adoc
new file mode 100644
index 0000000..bb45104
--- /dev/null
+++ b/camel-core/src/main/docs/binding-component.adoc
@@ -0,0 +1,124 @@
+[[Binding-Binding]]
+Binding
+-------
+
+In Camel terms a _binding_ is a way of wrapping an
+link:endpoint.html[Endpoint] in a contract; such as a
+link:data-format.html[Data Format], a link:content-enricher.html[Content
+Enricher] or validation step. Bindings are completely optional and you
+can choose to use them on any link:components.html[camel endpoint].
+
+Bindings are inspired by the work of
+http://www.jboss.org/switchyard[SwitchYard project] adding service
+contracts to various technologies like Camel and many others. But rather
+than the SwitchYard approach of wrapping Camel in SCA, _Camel Bindings_
+provide a way of wrapping Camel endpoints with contracts inside the
+Camel framework itself; so you can use them easily inside any Camel
+route.
+
+[[Binding-Options]]
+Options
+^^^^^^^
+
+
+// component options: START
+The Binding component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Binding component supports 6 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| bindingName | common | | String | *Required* Name of the binding to lookup in the Camel registry.
+| delegateUri | common | | String | *Required* Uri of the delegate endpoint.
+| 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
+
+
+[[Binding-UsingBindings]]
+Using Bindings
+~~~~~~~~~~~~~~
+
+A Binding is currently a bean which defines the contract (though we'll
+hopefully add bindings to the Camel DSL).
+
+There are a few approaches to defining a bound endpoint (i.e. an
+endpoint bound with a Binding).
+
+[[Binding-UsingthebindingURI]]
+Using the binding URI
+^^^^^^^^^^^^^^^^^^^^^
+
+You can prefix any endpoint URI with *binding:nameOfBinding:* where
+_nameOfBinding_ is the name of the Binding bean in your registry.
+
+[source,java]
+------------------------------------------------------------------------------
+from("binding:jaxb:activemq:myQueue").to("binding:jaxb:activemq:anotherQueue")
+------------------------------------------------------------------------------
+
+Here we are using the "jaxb" binding which may, for example, use the
+JAXB link:data-format.html[Data Format] to marshal and unmarshal
+messages.
+
+[[Binding-UsingaBindingComponent]]
+Using a BindingComponent
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+There is a link:component.html[Component] called BindingComponent which
+can be configured in your link:registry.html[Registry] by dependency
+injection which allows the creation of endpoints which are already bound
+to some binding.
+
+For example if you registered a new component called "jsonmq" in your
+registry using code like this
+
+[source,java]
+-----------------------------------------------------------------------------------------------------
+ JacksonDataFormat format = new JacksonDataFormat(MyBean.class);
+ context.bind("jsonmq", new BindingComponent(new DataFormatBinding(format), "activemq:foo."));
+-----------------------------------------------------------------------------------------------------
+
+Then you could use the endpoint as if it were any other endpoint.
+
+[source,java]
+------------------------------------------------
+from("jsonmq:myQueue").to("jsonmq:anotherQueue")
+------------------------------------------------
+
+which would be using the queueus "foo.myQueue" and "foo.anotherQueue"
+and would use the given Jackson link:data-format.html[Data Format] to
+marshal on and off the queue.
+
+[[Binding-WhentouseBindings]]
+When to use Bindings
+~~~~~~~~~~~~~~~~~~~~
+
+If you only use an endpoint once in a single route; a binding may
+actually be more complex and more work than just using the 'raw'
+endpoint directly and using explicit marshalling and validation in the
+camel route as normal.
+
+However bindings can help when you are composing many routes together;
+or using a single route as a 'template' that is configured input and
+output endpoints; bindings then provide a nice way to wrap up a contract
+and endpoint together.
+
+Another good use case for bindings is when you are using many endpoints
+which use the same binding; rather than always having to mention a
+specific data format or validation rule, you can just use the
+BindingComponent to wrap the endpoints in the binding of your choice.
+
+So bindings are a composition tool really; only use them when they make
+sense - the extra complexity may not be worth it unless you have lots of
+routes or endpoints.
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/binding.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/binding.adoc b/camel-core/src/main/docs/binding.adoc
deleted file mode 100644
index bb45104..0000000
--- a/camel-core/src/main/docs/binding.adoc
+++ /dev/null
@@ -1,124 +0,0 @@
-[[Binding-Binding]]
-Binding
--------
-
-In Camel terms a _binding_ is a way of wrapping an
-link:endpoint.html[Endpoint] in a contract; such as a
-link:data-format.html[Data Format], a link:content-enricher.html[Content
-Enricher] or validation step. Bindings are completely optional and you
-can choose to use them on any link:components.html[camel endpoint].
-
-Bindings are inspired by the work of
-http://www.jboss.org/switchyard[SwitchYard project] adding service
-contracts to various technologies like Camel and many others. But rather
-than the SwitchYard approach of wrapping Camel in SCA, _Camel Bindings_
-provide a way of wrapping Camel endpoints with contracts inside the
-Camel framework itself; so you can use them easily inside any Camel
-route.
-
-[[Binding-Options]]
-Options
-^^^^^^^
-
-
-// component options: START
-The Binding component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The Binding component supports 6 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| bindingName | common | | String | *Required* Name of the binding to lookup in the Camel registry.
-| delegateUri | common | | String | *Required* Uri of the delegate endpoint.
-| 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
-
-
-[[Binding-UsingBindings]]
-Using Bindings
-~~~~~~~~~~~~~~
-
-A Binding is currently a bean which defines the contract (though we'll
-hopefully add bindings to the Camel DSL).
-
-There are a few approaches to defining a bound endpoint (i.e. an
-endpoint bound with a Binding).
-
-[[Binding-UsingthebindingURI]]
-Using the binding URI
-^^^^^^^^^^^^^^^^^^^^^
-
-You can prefix any endpoint URI with *binding:nameOfBinding:* where
-_nameOfBinding_ is the name of the Binding bean in your registry.
-
-[source,java]
-------------------------------------------------------------------------------
-from("binding:jaxb:activemq:myQueue").to("binding:jaxb:activemq:anotherQueue")
-------------------------------------------------------------------------------
-
-Here we are using the "jaxb" binding which may, for example, use the
-JAXB link:data-format.html[Data Format] to marshal and unmarshal
-messages.
-
-[[Binding-UsingaBindingComponent]]
-Using a BindingComponent
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-There is a link:component.html[Component] called BindingComponent which
-can be configured in your link:registry.html[Registry] by dependency
-injection which allows the creation of endpoints which are already bound
-to some binding.
-
-For example if you registered a new component called "jsonmq" in your
-registry using code like this
-
-[source,java]
------------------------------------------------------------------------------------------------------
- JacksonDataFormat format = new JacksonDataFormat(MyBean.class);
- context.bind("jsonmq", new BindingComponent(new DataFormatBinding(format), "activemq:foo."));
------------------------------------------------------------------------------------------------------
-
-Then you could use the endpoint as if it were any other endpoint.
-
-[source,java]
-------------------------------------------------
-from("jsonmq:myQueue").to("jsonmq:anotherQueue")
-------------------------------------------------
-
-which would be using the queueus "foo.myQueue" and "foo.anotherQueue"
-and would use the given Jackson link:data-format.html[Data Format] to
-marshal on and off the queue.
-
-[[Binding-WhentouseBindings]]
-When to use Bindings
-~~~~~~~~~~~~~~~~~~~~
-
-If you only use an endpoint once in a single route; a binding may
-actually be more complex and more work than just using the 'raw'
-endpoint directly and using explicit marshalling and validation in the
-camel route as normal.
-
-However bindings can help when you are composing many routes together;
-or using a single route as a 'template' that is configured input and
-output endpoints; bindings then provide a nice way to wrap up a contract
-and endpoint together.
-
-Another good use case for bindings is when you are using many endpoints
-which use the same binding; rather than always having to mention a
-specific data format or validation rule, you can just use the
-BindingComponent to wrap the endpoints in the binding of your choice.
-
-So bindings are a composition tool really; only use them when they make
-sense - the extra complexity may not be worth it unless you have lots of
-routes or endpoints.
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/browse-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/browse-component.adoc b/camel-core/src/main/docs/browse-component.adoc
new file mode 100644
index 0000000..d2c3e6a
--- /dev/null
+++ b/camel-core/src/main/docs/browse-component.adoc
@@ -0,0 +1,88 @@
+[[Browse-BrowseComponent]]
+Browse Component
+~~~~~~~~~~~~~~~~
+
+The Browse component provides a simple
+link:browsableendpoint.html[BrowsableEndpoint] which can be useful for
+testing, visualisation tools or debugging. The exchanges sent to the
+endpoint are all available to be browsed.
+
+[[Browse-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+-------------------------
+browse:someName[?options]
+-------------------------
+
+Where *someName* can be any string to uniquely identify the endpoint.
+
+
+[[Gora-Options]]
+Options
+~~~~~~~
+
+
+// component options: START
+The Browse component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Browse component supports 5 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* A name which can be any string to uniquely identify the endpoint
+| 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
+
+
+[[Browse-Sample]]
+Sample
+^^^^^^
+
+In the route below, we insert a `browse:` component to be able to browse
+the Exchanges that are passing through:
+
+[source,java]
+-------------------------------------------------------------------------------
+ from("activemq:order.in").to("browse:orderReceived").to("bean:processOrder");
+-------------------------------------------------------------------------------
+
+We can now inspect the received exchanges from within the Java code:
+
+[source,java]
+--------------------------------------------------------------------------------------------------------
+ private CamelContext context;
+
+ public void inspectRecievedOrders() {
+ BrowsableEndpoint browse = context.getEndpoint("browse:orderReceived", BrowsableEndpoint.class);
+ List<Exchange> exchanges = browse.getExchanges();
+ ...
+ // then we can inspect the list of received exchanges from Java
+ for (Exchange exchange : exchanges) {
+ String payload = exchange.getIn().getBody();
+ ...
+ }
+ }
+--------------------------------------------------------------------------------------------------------
+
+[[Browse-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/camel-core/src/main/docs/browse.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/browse.adoc b/camel-core/src/main/docs/browse.adoc
deleted file mode 100644
index d2c3e6a..0000000
--- a/camel-core/src/main/docs/browse.adoc
+++ /dev/null
@@ -1,88 +0,0 @@
-[[Browse-BrowseComponent]]
-Browse Component
-~~~~~~~~~~~~~~~~
-
-The Browse component provides a simple
-link:browsableendpoint.html[BrowsableEndpoint] which can be useful for
-testing, visualisation tools or debugging. The exchanges sent to the
-endpoint are all available to be browsed.
-
-[[Browse-URIformat]]
-URI format
-^^^^^^^^^^
-
-[source,java]
--------------------------
-browse:someName[?options]
--------------------------
-
-Where *someName* can be any string to uniquely identify the endpoint.
-
-
-[[Gora-Options]]
-Options
-~~~~~~~
-
-
-// component options: START
-The Browse component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The Browse component supports 5 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* A name which can be any string to uniquely identify the endpoint
-| 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
-
-
-[[Browse-Sample]]
-Sample
-^^^^^^
-
-In the route below, we insert a `browse:` component to be able to browse
-the Exchanges that are passing through:
-
-[source,java]
--------------------------------------------------------------------------------
- from("activemq:order.in").to("browse:orderReceived").to("bean:processOrder");
--------------------------------------------------------------------------------
-
-We can now inspect the received exchanges from within the Java code:
-
-[source,java]
---------------------------------------------------------------------------------------------------------
- private CamelContext context;
-
- public void inspectRecievedOrders() {
- BrowsableEndpoint browse = context.getEndpoint("browse:orderReceived", BrowsableEndpoint.class);
- List<Exchange> exchanges = browse.getExchanges();
- ...
- // then we can inspect the list of received exchanges from Java
- for (Exchange exchange : exchanges) {
- String payload = exchange.getIn().getBody();
- ...
- }
- }
---------------------------------------------------------------------------------------------------------
-
-[[Browse-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/camel-core/src/main/docs/class-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/class-component.adoc b/camel-core/src/main/docs/class-component.adoc
new file mode 100644
index 0000000..47f2562
--- /dev/null
+++ b/camel-core/src/main/docs/class-component.adoc
@@ -0,0 +1,132 @@
+[[Class-ClassComponent]]
+Class Component
+~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.4*
+
+The *class:* component binds beans to Camel message exchanges. It works
+in the same way as the link:bean.html[Bean] component but instead of
+looking up beans from a link:registry.html[Registry] it creates the bean
+based on the class name.
+
+[[Class-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,java]
+-------------------------
+class:className[?options]
+-------------------------
+
+Where *className* is the fully qualified class name to create and use as
+bean.
+
+[[Class-Options]]
+Options
+^^^^^^^
+
+
+// component options: START
+The Class component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Class component supports 9 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| beanName | common | | String | *Required* Sets the name of the bean to invoke
+| method | common | | String | Sets the name of the method to invoke on the bean
+| 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.
+| cache | advanced | false | boolean | If enabled Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange.
+| multiParameterArray | advanced | false | boolean | How to treat the parameters which are passed from the message body; if it is true the message body should be an array of parameters. Note: This option is used internally by Camel and is not intended for end users to use.
+| parameters | advanced | | Map | Used for configuring additional properties on the bean
+| 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
+
+
+[[Class-Using]]
+Using
+^^^^^
+
+You simply use the *class* component just as the link:bean.html[Bean]
+component but by specifying the fully qualified classname instead. +
+ For example to use the `MyFooBean` you have to do as follows:
+
+[source,java]
+-------------------------------------------------------------------------------------------------
+ from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
+-------------------------------------------------------------------------------------------------
+
+You can also specify which method to invoke on the `MyFooBean`, for
+example `hello`:
+
+[source,java]
+--------------------------------------------------------------------------------------------------------------
+ from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
+--------------------------------------------------------------------------------------------------------------
+
+[[Class-Settingpropertiesonthecreatedinstance]]
+Setting properties on the created instance
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In the endpoint uri you can specify properties to set on the created
+instance, for example if it has a `setPrefix` method:
+
+[source,java]
+---------------------------------------------------------------------------------
+ // Camel 2.17 onwards
+ from("direct:start")
+ .to("class:org.apache.camel.component.bean.MyPrefixBean?bean.prefix=Bye")
+ .to("mock:result");
+�
+ // Camel 2.16 and older�
+ from("direct:start")
+ .to("class:org.apache.camel.component.bean.MyPrefixBean?prefix=Bye")
+ .to("mock:result");
+---------------------------------------------------------------------------------
+
+And you can also use the `#` syntax to refer to properties to be looked
+up in the link:registry.html[Registry].
+
+[source,java]
+--------------------------------------------------------------------------------
+ // Camel 2.17 onwards
+ from("direct:start")
+ .to("class:org.apache.camel.component.bean.MyPrefixBean?bean.cool=#foo")
+ .to("mock:result");
+
+ // Camel 2.16 and older
+ from("direct:start")
+ .to("class:org.apache.camel.component.bean.MyPrefixBean?cool=#foo")
+ .to("mock:result");
+--------------------------------------------------------------------------------
+
+Which will lookup a bean from the link:registry.html[Registry] with the
+id `foo` and invoke the `setCool` method on the created instance of the
+`MyPrefixBean` class.
+
+TIP:See more details at the link:bean.html[Bean] component as the *class*
+component works in much the same way.
+
+[[Class-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+
+* link:bean.html[Bean]
+* link:bean-binding.html[Bean Binding]
+* link:bean-integration.html[Bean Integration]
+
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/class.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/class.adoc b/camel-core/src/main/docs/class.adoc
deleted file mode 100644
index 47f2562..0000000
--- a/camel-core/src/main/docs/class.adoc
+++ /dev/null
@@ -1,132 +0,0 @@
-[[Class-ClassComponent]]
-Class Component
-~~~~~~~~~~~~~~~
-
-*Available as of Camel 2.4*
-
-The *class:* component binds beans to Camel message exchanges. It works
-in the same way as the link:bean.html[Bean] component but instead of
-looking up beans from a link:registry.html[Registry] it creates the bean
-based on the class name.
-
-[[Class-URIformat]]
-URI format
-^^^^^^^^^^
-
-[source,java]
--------------------------
-class:className[?options]
--------------------------
-
-Where *className* is the fully qualified class name to create and use as
-bean.
-
-[[Class-Options]]
-Options
-^^^^^^^
-
-
-// component options: START
-The Class component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The Class component supports 9 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| beanName | common | | String | *Required* Sets the name of the bean to invoke
-| method | common | | String | Sets the name of the method to invoke on the bean
-| 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.
-| cache | advanced | false | boolean | If enabled Camel will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange.
-| multiParameterArray | advanced | false | boolean | How to treat the parameters which are passed from the message body; if it is true the message body should be an array of parameters. Note: This option is used internally by Camel and is not intended for end users to use.
-| parameters | advanced | | Map | Used for configuring additional properties on the bean
-| 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
-
-
-[[Class-Using]]
-Using
-^^^^^
-
-You simply use the *class* component just as the link:bean.html[Bean]
-component but by specifying the fully qualified classname instead. +
- For example to use the `MyFooBean` you have to do as follows:
-
-[source,java]
--------------------------------------------------------------------------------------------------
- from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
--------------------------------------------------------------------------------------------------
-
-You can also specify which method to invoke on the `MyFooBean`, for
-example `hello`:
-
-[source,java]
---------------------------------------------------------------------------------------------------------------
- from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
---------------------------------------------------------------------------------------------------------------
-
-[[Class-Settingpropertiesonthecreatedinstance]]
-Setting properties on the created instance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In the endpoint uri you can specify properties to set on the created
-instance, for example if it has a `setPrefix` method:
-
-[source,java]
----------------------------------------------------------------------------------
- // Camel 2.17 onwards
- from("direct:start")
- .to("class:org.apache.camel.component.bean.MyPrefixBean?bean.prefix=Bye")
- .to("mock:result");
-�
- // Camel 2.16 and older�
- from("direct:start")
- .to("class:org.apache.camel.component.bean.MyPrefixBean?prefix=Bye")
- .to("mock:result");
----------------------------------------------------------------------------------
-
-And you can also use the `#` syntax to refer to properties to be looked
-up in the link:registry.html[Registry].
-
-[source,java]
---------------------------------------------------------------------------------
- // Camel 2.17 onwards
- from("direct:start")
- .to("class:org.apache.camel.component.bean.MyPrefixBean?bean.cool=#foo")
- .to("mock:result");
-
- // Camel 2.16 and older
- from("direct:start")
- .to("class:org.apache.camel.component.bean.MyPrefixBean?cool=#foo")
- .to("mock:result");
---------------------------------------------------------------------------------
-
-Which will lookup a bean from the link:registry.html[Registry] with the
-id `foo` and invoke the `setCool` method on the created instance of the
-`MyPrefixBean` class.
-
-TIP:See more details at the link:bean.html[Bean] component as the *class*
-component works in much the same way.
-
-[[Class-SeeAlso]]
-See Also
-^^^^^^^^
-
-* link:configuring-camel.html[Configuring Camel]
-* link:component.html[Component]
-* link:endpoint.html[Endpoint]
-* link:getting-started.html[Getting Started]
-
-* link:bean.html[Bean]
-* link:bean-binding.html[Bean Binding]
-* link:bean-integration.html[Bean Integration]
-
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/camel-core/src/main/docs/controlbus-component.adoc
----------------------------------------------------------------------
diff --git a/camel-core/src/main/docs/controlbus-component.adoc b/camel-core/src/main/docs/controlbus-component.adoc
new file mode 100644
index 0000000..5aa3cea
--- /dev/null
+++ b/camel-core/src/main/docs/controlbus-component.adoc
@@ -0,0 +1,211 @@
+[[ControlBus-ControlBus]]
+ControlBus
+^^^^^^^^^^
+
+The http://www.eaipatterns.com/ControlBus.html[Control Bus] from the
+link:enterprise-integration-patterns.html[EIP patterns] allows for the
+integration system to be monitored and managed from within the
+framework.
+
+image:http://www.eaipatterns.com/img/ControlBus.gif[image]
+
+Use a Control Bus to manage an enterprise integration system. The
+Control Bus uses the same messaging mechanism used by the application
+data, but uses separate channels to transmit data that is relevant to
+the management of components involved in the message flow.
+
+In Camel you can manage and monitor using link:camel-jmx.html[JMX], or
+by using a Java API from the `CamelContext`, or from the
+`org.apache.camel.api.management` package, +
+ or use the event notifier which has an example
+link:eventnotifier-to-log-details-about-all-sent-exchanges.html[here].
+
+From Camel 2.11 onwards we have introduced a new
+link:controlbus-component.html[ControlBus Component] that allows you to
+send messages to a control bus link:endpoint.html[Endpoint] that reacts
+accordingly.
+
+[[ControlBus-ControlBusComponent]]
+ControlBus Component
+~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.11*
+
+The *controlbus:* component provides easy management of Camel
+applications based on the link:controlbus.html[Control Bus] EIP
+pattern.
+For example, by sending a message to an link:endpoint.html[Endpoint]
+you can control the lifecycle of routes, or gather performance
+statistics.
+
+[source,java]
+----------------------------
+controlbus:command[?options]
+----------------------------
+
+Where *command* can be any string to identify which type of command to
+use.
+
+[[ControlBus-Commands]]
+Commands
+^^^^^^^^
+
+[width="100%",cols="10%,90%",options="header",]
+|=======================================================================
+|Command |Description
+
+|`route` |To control routes using the `routeId` and `action` parameter.
+
+|`language` |Allows you to specify a link:language.html[Language] to use for
+evaluating the message body. If there is any result from the evaluation,
+then the result is put in the message body.
+|=======================================================================
+
+[[ControlBus-Options]]
+Options
+^^^^^^^
+
+
+// component options: START
+The Control Bus component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The Control Bus component supports 8 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| command | producer | | String | *Required* Command can be either route or language
+| language | producer | | Language | Allows you to specify the name of a Language to use for evaluating the message body. If there is any result from the evaluation then the result is put in the message body.
+| action | producer | | String | To denote an action that can be either: start stop or status. To either start or stop a route or to get the status of the route as output in the message body. You can use suspend and resume from Camel 2.11.1 onwards to either suspend or resume a route. And from Camel 2.11.1 onwards you can use stats to get performance statics returned in XML format; the routeId option can be used to define which route to get the performance stats for if routeId is not defined then you get statistics for the entire CamelContext.
+| async | producer | false | boolean | Whether to execute the control bus task asynchronously. Important: If this option is enabled then any result from the task is not set on the Exchange. This is only possible if executing tasks synchronously.
+| loggingLevel | producer | INFO | LoggingLevel | Logging level used for logging when task is done or if any exceptions occurred during processing the task.
+| routeId | producer | | String | To specify a route by its id. The special keyword current indicates the current route.
+| 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
+
+
+You can append query options to the URI in the following format,
+`?option=value&option=value&...`
+
+[[ControlBus-Samples]]
+Samples
+^^^^^^^
+
+[[ControlBus-Usingroutecommand]]
+Using route command
++++++++++++++++++++
+
+The route command allows you to do common tasks on a given route very
+easily, for example to start a route, you can send an empty message to
+this endpoint:
+
+[source,java]
+---------------------------------------------------------------------
+template.sendBody("controlbus:route?routeId=foo&action=start", null);
+---------------------------------------------------------------------
+
+To get the status of the route, you can do:
+
+[source,java]
+-------------------------------------------------------------------------------------------------------
+String status = template.requestBody("controlbus:route?routeId=foo&action=status", null, String.class);
+-------------------------------------------------------------------------------------------------------
+
+[[ControlBus-Gettingperformancestatistics]]
+Getting performance statistics
+
+*Available as of Camel 2.11.1*
+
+This requires JMX to be enabled (is by default) then you can get the
+performance statics per route, or for the
+link:camelcontext.html[CamelContext]. For example to get the statics for
+a route named foo, we can do:
+
+[source,java]
+---------------------------------------------------------------------------------------------------
+String xml = template.requestBody("controlbus:route?routeId=foo&action=stats", null, String.class);
+---------------------------------------------------------------------------------------------------
+
+The returned statics is in XML format. Its the same data you can get
+from JMX with the `dumpRouteStatsAsXml` operation on the
+`ManagedRouteMBean`.
+
+To get statics for the entire link:camelcontext.html[CamelContext] you
+just omit the routeId parameter as shown below:
+
+[source,java]
+---------------------------------------------------------------------------------------
+String xml = template.requestBody("controlbus:route?action=stats", null, String.class);
+---------------------------------------------------------------------------------------
+
+[[ControlBus-Usinglanguage]]
+Using link:simple.html[Simple] language
++++++++++++++++++++++++++++++++++++++++
+
+You can use the link:simple.html[Simple] language with the control bus,
+for example to stop a specific route, you can send a message to the
+`"controlbus:language:simple"` endpoint containing the following
+message:
+
+[source,java]
+----------------------------------------------------------------------------------------
+template.sendBody("controlbus:language:simple", "${camelContext.stopRoute('myRoute')}");
+----------------------------------------------------------------------------------------
+
+As this is a void operation, no result is returned. However, if you want
+the route status you can do:
+
+[source,java]
+------------------------------------------------------------------------------------------------------------------------------
+String status = template.requestBody("controlbus:language:simple", "${camelContext.getRouteStatus('myRoute')}", String.class);
+------------------------------------------------------------------------------------------------------------------------------
+
+*Notice:* its easier to use the `route` command to control lifecycle of
+routes. The `language` command allows you to execute a language script
+that has stronger powers such as link:groovy.html[Groovy] or to some
+extend the link:simple.html[Simple] language.
+
+For example to shutdown Camel itself you can do:
+
+[source,java]
+-------------------------------------------------------------------------------------
+template.sendBody("controlbus:language:simple?async=true", "${camelContext.stop()}");
+-------------------------------------------------------------------------------------
+
+Notice we use `async=true` to stop Camel asynchronously as otherwise we
+would be trying to stop Camel while it was in-flight processing the
+message we sent to the control bus component.
+
+TIP:You can also use other languages such as link:groovy.html[Groovy], etc.
+
+[[ControlBus-SeeAlso]]
+See Also
+^^^^^^^^
+
+* link:configuring-camel.html[Configuring Camel]
+* link:component.html[Component]
+* link:endpoint.html[Endpoint]
+* link:getting-started.html[Getting Started]
+
+* link:controlbus.html[ControlBus] EIP
+* link:jmx.html[JMX] Component
+* Using link:camel-jmx.html[JMX] with Camel
+
+[[ControlBus-UsingThisPattern]]
+Using This Pattern
+++++++++++++++++++
+
+If you would like to use this EIP Pattern then please read the
+link:getting-started.html[Getting Started], you may also find the
+link:architecture.html[Architecture] useful particularly the description
+of link:endpoint.html[Endpoint] and link:uris.html[URIs]. Then you could
+try out some of the link:examples.html[Examples] first before trying
+this pattern out.