You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by gi...@apache.org on 2018/02/14 07:00:42 UTC
[camel-website] branch asf-site updated (1f980eb -> 7039a3e)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/camel-website.git.
discard 1f980eb Updated the website to b19baea
new 7039a3e Updated the website to b19baea
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1f980eb)
\
N -- N -- N refs/heads/asf-site (7039a3e)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
git-site-role@apache.org.
[camel-website] 01/01: Updated the website to b19baea
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 7039a3e6f73e760b6f98a5b3d3322af5e3c58528
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Feb 14 07:00:39 2018 +0000
Updated the website to b19baea
---
404.html | 1 +
about/index.html | 169 +
apple-touch-icon.png | Bin 0 -> 3959 bytes
browserconfig.xml | 12 +
components/2.20.0/ahc-component/index.html | 867 ++++
components/2.20.0/ahc-ws-component/index.html | 561 +++
components/2.20.0/amqp-component/index.html | 1435 +++++++
components/2.20.0/apns-component/index.html | 706 +++
components/2.20.0/asterisk-component/index.html | 361 ++
components/2.20.0/atmos-component/index.html | 471 ++
.../atmosphere-websocket-component/index.html | 674 +++
components/2.20.0/atom-component/index.html | 570 +++
components/2.20.0/atomix-map-component/index.html | 627 +++
.../2.20.0/atomix-messaging-component/index.html | 449 ++
.../2.20.0/atomix-multimap-component/index.html | 443 ++
.../2.20.0/atomix-queue-component/index.html | 431 ++
components/2.20.0/atomix-set-component/index.html | 437 ++
.../2.20.0/atomix-value-component/index.html | 437 ++
components/2.20.0/avro-component/index.html | 645 +++
components/2.20.0/avro-dataformat/index.html | 369 ++
components/2.20.0/aws-cw-component/index.html | 506 +++
components/2.20.0/aws-ddb-component/index.html | 913 ++++
.../2.20.0/aws-ddbstream-component/index.html | 562 +++
components/2.20.0/aws-ec2-component/index.html | 463 ++
components/2.20.0/aws-kinesis-component/index.html | 637 +++
.../aws-kinesis-firehose-component/index.html | 422 ++
components/2.20.0/aws-s3-component/index.html | 877 ++++
components/2.20.0/aws-sdb-component/index.html | 666 +++
components/2.20.0/aws-ses-component/index.html | 518 +++
components/2.20.0/aws-sns-component/index.html | 494 +++
components/2.20.0/aws-sqs-component/index.html | 760 ++++
components/2.20.0/aws-swf-component/index.html | 748 ++++
components/2.20.0/aws/index.html | 293 ++
components/2.20.0/azure-blob-component/index.html | 558 +++
components/2.20.0/azure-queue-component/index.html | 492 +++
components/2.20.0/azure/index.html | 238 ++
components/2.20.0/bam-example/index.html | 331 ++
components/2.20.0/bam/index.html | 276 ++
components/2.20.0/barcode-dataformat/index.html | 405 ++
components/2.20.0/base64-dataformat/index.html | 355 ++
.../2.20.0/bean-validator-component/index.html | 549 +++
components/2.20.0/beanio-dataformat/index.html | 343 ++
components/2.20.0/beanstalk-component/index.html | 680 +++
components/2.20.0/bindy-dataformat/index.html | 2703 ++++++++++++
components/2.20.0/blueprint/index.html | 258 ++
components/2.20.0/bonita-component/index.html | 376 ++
components/2.20.0/boon-dataformat/index.html | 292 ++
components/2.20.0/box-component/index.html | 1871 ++++++++
components/2.20.0/braintree-component/index.html | 1651 ++++++++
components/2.20.0/cache-component/index.html | 912 ++++
.../2.20.0/caffeine-cache-component/index.html | 426 ++
.../2.20.0/caffeine-loadcache-component/index.html | 426 ++
components/2.20.0/castor-dataformat/index.html | 390 ++
components/2.20.0/cdi/index.html | 1600 +++++++
.../2.20.0/chronicle-engine-component/index.html | 357 ++
components/2.20.0/chunk-component/index.html | 523 +++
components/2.20.0/cm-sms-component/index.html | 333 ++
components/2.20.0/cmis-component/index.html | 524 +++
components/2.20.0/coap-component/index.html | 312 ++
components/2.20.0/cometd-component/index.html | 598 +++
components/2.20.0/consul-component/index.html | 498 +++
components/2.20.0/context-component/index.html | 441 ++
components/2.20.0/couchbase-component/index.html | 585 +++
components/2.20.0/couchdb-component/index.html | 499 +++
components/2.20.0/cql-component/index.html | 664 +++
components/2.20.0/crypto-component/index.html | 656 +++
components/2.20.0/crypto-dataformat/index.html | 576 +++
components/2.20.0/csv-dataformat/index.html | 753 ++++
components/2.20.0/cxf-component/index.html | 1590 +++++++
components/2.20.0/cxf-transport/index.html | 484 +++
components/2.20.0/cxfrs-component/index.html | 825 ++++
.../2.20.0/digitalocean-component/index.html | 582 +++
components/2.20.0/disruptor-component/index.html | 719 ++++
components/2.20.0/dns-component/index.html | 463 ++
components/2.20.0/docker-component/index.html | 505 +++
components/2.20.0/dozer-component/index.html | 578 +++
components/2.20.0/drill-component/index.html | 349 ++
components/2.20.0/dropbox-component/index.html | 934 ++++
components/2.20.0/eclipse/index.html | 262 ++
components/2.20.0/ehcache-component/index.html | 624 +++
components/2.20.0/ejb-component/index.html | 531 +++
components/2.20.0/el-language/index.html | 347 ++
.../2.20.0/elasticsearch-component/index.html | 540 +++
.../2.20.0/elasticsearch5-component/index.html | 494 +++
components/2.20.0/elsql-component/index.html | 796 ++++
components/2.20.0/etcd-component/index.html | 521 +++
components/2.20.0/eventadmin-component/index.html | 394 ++
components/2.20.0/exec-component/index.html | 611 +++
components/2.20.0/facebook-component/index.html | 1093 +++++
components/2.20.0/flatpack-component/index.html | 780 ++++
components/2.20.0/flatpack-dataformat/index.html | 362 ++
components/2.20.0/flink-component/index.html | 459 ++
components/2.20.0/fop-component/index.html | 527 +++
components/2.20.0/freemarker-component/index.html | 594 +++
components/2.20.0/ftp-component/index.html | 1661 ++++++++
components/2.20.0/ftps-component/index.html | 992 +++++
components/2.20.0/ganglia-component/index.html | 474 +++
components/2.20.0/geocoder-component/index.html | 509 +++
components/2.20.0/git-component/index.html | 472 +++
components/2.20.0/github-component/index.html | 474 +++
.../2.20.0/google-calendar-component/index.html | 514 +++
.../2.20.0/google-drive-component/index.html | 518 +++
components/2.20.0/google-mail-component/index.html | 497 +++
.../2.20.0/google-pubsub-component/index.html | 535 +++
components/2.20.0/gora-component/index.html | 653 +++
components/2.20.0/grape-component/index.html | 525 +++
components/2.20.0/groovy-dsl/index.html | 616 +++
components/2.20.0/groovy-language/index.html | 460 ++
components/2.20.0/grpc-component/index.html | 616 +++
.../2.20.0/guava-eventbus-component/index.html | 508 +++
components/2.20.0/guice/index.html | 377 ++
components/2.20.0/hawtdb/index.html | 482 +++
.../hazelcast-atomicvalue-component/index.html | 560 +++
.../2.20.0/hazelcast-instance-component/index.html | 458 ++
.../2.20.0/hazelcast-list-component/index.html | 464 ++
.../2.20.0/hazelcast-map-component/index.html | 784 ++++
.../2.20.0/hazelcast-multimap-component/index.html | 627 +++
.../2.20.0/hazelcast-queue-component/index.html | 478 +++
.../hazelcast-replicatedmap-component/index.html | 594 +++
.../hazelcast-ringbuffer-component/index.html | 450 ++
.../2.20.0/hazelcast-seda-component/index.html | 436 ++
.../2.20.0/hazelcast-set-component/index.html | 383 ++
.../2.20.0/hazelcast-topic-component/index.html | 418 ++
components/2.20.0/hazelcast/index.html | 364 ++
components/2.20.0/hbase-component/index.html | 957 +++++
components/2.20.0/hdfs-component/index.html | 757 ++++
components/2.20.0/hdfs2-component/index.html | 818 ++++
components/2.20.0/headersmap/index.html | 240 ++
components/2.20.0/hessian-dataformat/index.html | 267 ++
components/2.20.0/hipchat-component/index.html | 615 +++
components/2.20.0/hl7-dataformat/index.html | 990 +++++
components/2.20.0/http-component/index.html | 1151 +++++
components/2.20.0/http4-component/index.html | 1395 ++++++
components/2.20.0/hystrix/index.html | 221 +
components/2.20.0/ibatis-component/index.html | 699 +++
components/2.20.0/ical-dataformat/index.html | 312 ++
.../2.20.0/ignite-cache-component/index.html | 477 +++
.../2.20.0/ignite-compute-component/index.html | 468 ++
.../2.20.0/ignite-events-component/index.html | 361 ++
.../2.20.0/ignite-idgen-component/index.html | 352 ++
.../2.20.0/ignite-messaging-component/index.html | 405 ++
.../2.20.0/ignite-queue-component/index.html | 408 ++
components/2.20.0/ignite-set-component/index.html | 378 ++
components/2.20.0/ignite/index.html | 419 ++
components/2.20.0/infinispan-component/index.html | 681 +++
components/2.20.0/influxdb-component/index.html | 400 ++
components/2.20.0/irc-component/index.html | 611 +++
components/2.20.0/ironmq-component/index.html | 580 +++
components/2.20.0/jacksonxml-dataformat/index.html | 692 +++
components/2.20.0/jasypt/index.html | 542 +++
components/2.20.0/javascript-language/index.html | 449 ++
components/2.20.0/javaspace-component/index.html | 443 ++
components/2.20.0/jaxb-dataformat/index.html | 684 +++
components/2.20.0/jbpm-component/index.html | 614 +++
components/2.20.0/jcache-component/index.html | 459 ++
components/2.20.0/jclouds-component/index.html | 747 ++++
components/2.20.0/jcr-component/index.html | 451 ++
components/2.20.0/jdbc-component/index.html | 622 +++
components/2.20.0/jetty-component/index.html | 1524 +++++++
components/2.20.0/jgroups-component/index.html | 610 +++
components/2.20.0/jibx-dataformat/index.html | 318 ++
components/2.20.0/jing-component/index.html | 357 ++
components/2.20.0/jira-component/index.html | 407 ++
components/2.20.0/jms-component/index.html | 2877 +++++++++++++
components/2.20.0/jmx-component/index.html | 1833 ++++++++
components/2.20.0/jolt-component/index.html | 412 ++
components/2.20.0/jpa-component/index.html | 989 +++++
.../2.20.0/json-fastjson-dataformat/index.html | 362 ++
components/2.20.0/json-gson-dataformat/index.html | 362 ++
.../2.20.0/json-jackson-dataformat/index.html | 362 ++
.../2.20.0/json-johnzon-dataformat/index.html | 362 ++
.../2.20.0/json-xstream-dataformat/index.html | 454 ++
components/2.20.0/jsonpath-language/index.html | 580 +++
components/2.20.0/jt400-component/index.html | 643 +++
components/2.20.0/jxpath-language/index.html | 418 ++
components/2.20.0/kafka-component/index.html | 1266 ++++++
components/2.20.0/kestrel-component/index.html | 606 +++
components/2.20.0/krati-component/index.html | 615 +++
.../kubernetes-build-configs-component/index.html | 383 ++
.../2.20.0/kubernetes-builds-component/index.html | 383 ++
components/2.20.0/kubernetes-component/index.html | 835 ++++
.../kubernetes-config-maps-component/index.html | 383 ++
.../kubernetes-namespaces-component/index.html | 430 ++
.../2.20.0/kubernetes-nodes-component/index.html | 430 ++
.../index.html | 381 ++
.../index.html | 383 ++
.../2.20.0/kubernetes-pods-component/index.html | 431 ++
.../index.html | 430 ++
.../index.html | 383 ++
.../2.20.0/kubernetes-secrets-component/index.html | 383 ++
.../kubernetes-services-component/index.html | 430 ++
components/2.20.0/kubernetes/index.html | 527 +++
components/2.20.0/kura/index.html | 523 +++
components/2.20.0/ldap-component/index.html | 634 +++
components/2.20.0/leveldb/index.html | 447 ++
components/2.20.0/linkedin-component/index.html | 1641 +++++++
components/2.20.0/lpr-component/index.html | 448 ++
components/2.20.0/lucene-component/index.html | 553 +++
components/2.20.0/lumberjack-component/index.html | 395 ++
components/2.20.0/lzf-dataformat/index.html | 290 ++
components/2.20.0/mail-component/index.html | 1366 ++++++
components/2.20.0/metrics-component/index.html | 1213 ++++++
components/2.20.0/milo-client-component/index.html | 591 +++
components/2.20.0/milo-server-component/index.html | 474 +++
.../2.20.0/mime-multipart-dataformat/index.html | 494 +++
components/2.20.0/mina-component/index.html | 764 ++++
components/2.20.0/mina2-component/index.html | 713 ++++
components/2.20.0/mllp-component/index.html | 649 +++
components/2.20.0/mongodb-component/index.html | 1511 +++++++
.../2.20.0/mongodb-gridfs-component/index.html | 543 +++
components/2.20.0/mongodb3-component/index.html | 1444 +++++++
components/2.20.0/mqtt-component/index.html | 647 +++
components/2.20.0/msv-component/index.html | 446 ++
components/2.20.0/mustache-component/index.html | 529 +++
components/2.20.0/mvel-component/index.html | 502 +++
components/2.20.0/mvel-language/index.html | 385 ++
components/2.20.0/mybatis-component/index.html | 884 ++++
components/2.20.0/nagios-component/index.html | 445 ++
components/2.20.0/nats-component/index.html | 501 +++
components/2.20.0/netty-component/index.html | 1401 ++++++
components/2.20.0/netty-http-component/index.html | 1338 ++++++
components/2.20.0/netty4-component/index.html | 1451 +++++++
components/2.20.0/netty4-http-component/index.html | 1334 ++++++
components/2.20.0/ognl-language/index.html | 390 ++
components/2.20.0/olingo2-component/index.html | 675 +++
components/2.20.0/olingo4-component/index.html | 654 +++
components/2.20.0/openshift-component/index.html | 599 +++
.../2.20.0/openstack-cinder-component/index.html | 589 +++
.../2.20.0/openstack-glance-component/index.html | 498 +++
.../2.20.0/openstack-keystone-component/index.html | 837 ++++
.../2.20.0/openstack-neutron-component/index.html | 777 ++++
.../2.20.0/openstack-nova-component/index.html | 660 +++
.../2.20.0/openstack-swift-component/index.html | 598 +++
components/2.20.0/openstack/index.html | 266 ++
components/2.20.0/opentracing/index.html | 295 ++
components/2.20.0/optaplanner-component/index.html | 472 +++
components/2.20.0/paho-component/index.html | 544 +++
components/2.20.0/paxlogging-component/index.html | 381 ++
components/2.20.0/pdf-component/index.html | 415 ++
components/2.20.0/pgevent-component/index.html | 381 ++
components/2.20.0/pgp-dataformat/index.html | 725 ++++
components/2.20.0/php-language/index.html | 412 ++
components/2.20.0/protobuf-dataformat/index.html | 472 +++
components/2.20.0/pubnub-component/index.html | 567 +++
components/2.20.0/python-language/index.html | 448 ++
components/2.20.0/quartz-component/index.html | 694 +++
components/2.20.0/quartz2-component/index.html | 839 ++++
components/2.20.0/quickfix-component/index.html | 1104 +++++
components/2.20.0/rabbitmq-component/index.html | 883 ++++
.../2.20.0/reactive-streams-component/index.html | 801 ++++
components/2.20.0/reactor-component/index.html | 211 +
.../2.20.0/rest-swagger-component/index.html | 562 +++
components/2.20.0/restlet-component/index.html | 964 +++++
components/2.20.0/ribbon/index.html | 292 ++
components/2.20.0/rmi-component/index.html | 416 ++
components/2.20.0/routebox-component/index.html | 658 +++
components/2.20.0/rss-component/index.html | 609 +++
components/2.20.0/rss-dataformat/index.html | 271 ++
components/2.20.0/ruby-language/index.html | 448 ++
components/2.20.0/ruby/index.html | 412 ++
components/2.20.0/rx/index.html | 420 ++
components/2.20.0/salesforce-component/index.html | 1440 +++++++
.../2.20.0/sap-netweaver-component/index.html | 495 +++
components/2.20.0/scala-eip/index.html | 490 +++
components/2.20.0/scala-getting-started/index.html | 263 ++
.../2.20.0/scala-supported-languages/index.html | 221 +
components/2.20.0/scala/index.html | 286 ++
components/2.20.0/schematron-component/index.html | 467 ++
components/2.20.0/scp-component/index.html | 485 +++
components/2.20.0/scr/index.html | 898 ++++
components/2.20.0/script/index.html | 289 ++
components/2.20.0/securexml-dataformat/index.html | 537 +++
components/2.20.0/servicenow-component/index.html | 1692 ++++++++
components/2.20.0/servlet-component/index.html | 755 ++++
components/2.20.0/servletlistener/index.html | 645 +++
components/2.20.0/sftp-component/index.html | 956 +++++
components/2.20.0/shiro/index.html | 562 +++
components/2.20.0/sip-component/index.html | 705 +++
components/2.20.0/sjms-batch-component/index.html | 630 +++
components/2.20.0/sjms-component/index.html | 1137 +++++
components/2.20.0/sjms2-component/index.html | 1171 +++++
components/2.20.0/slack-component/index.html | 426 ++
components/2.20.0/smpp-component/index.html | 1330 ++++++
components/2.20.0/snmp-component/index.html | 630 +++
components/2.20.0/soapjaxb-dataformat/index.html | 588 +++
components/2.20.0/solr-component/index.html | 582 +++
components/2.20.0/spark-component/index.html | 740 ++++
components/2.20.0/spark-rest-component/index.html | 576 +++
components/2.20.0/spel-language/index.html | 449 ++
components/2.20.0/splunk-component/index.html | 758 ++++
.../2.20.0/spring-batch-component/index.html | 573 +++
components/2.20.0/spring-boot/index.html | 672 +++
components/2.20.0/spring-cloud-netflix/index.html | 245 ++
components/2.20.0/spring-cloud/index.html | 236 ++
components/2.20.0/spring-dm/index.html | 201 +
.../2.20.0/spring-event-component/index.html | 326 ++
.../2.20.0/spring-integration-component/index.html | 400 ++
components/2.20.0/spring-javaconfig/index.html | 295 ++
components/2.20.0/spring-ldap-component/index.html | 410 ++
.../2.20.0/spring-redis-component/index.html | 1165 +++++
components/2.20.0/spring-security/index.html | 457 ++
components/2.20.0/spring-ws-component/index.html | 1088 +++++
components/2.20.0/spring/index.html | 698 +++
components/2.20.0/sql-component/index.html | 1438 +++++++
components/2.20.0/sql-language/index.html | 306 ++
components/2.20.0/sql-stored-component/index.html | 563 +++
components/2.20.0/ssh-component/index.html | 679 +++
components/2.20.0/stax-component/index.html | 478 +++
components/2.20.0/stomp-component/index.html | 496 +++
components/2.20.0/stream-component/index.html | 494 +++
.../2.20.0/string-template-component/index.html | 414 ++
components/2.20.0/swagger-java/index.html | 547 +++
components/2.20.0/swagger/index.html | 526 +++
components/2.20.0/syslog-dataformat/index.html | 400 ++
components/2.20.0/tarfile-dataformat/index.html | 400 ++
components/2.20.0/telegram-component/index.html | 758 ++++
components/2.20.0/terser-language/index.html | 259 ++
components/2.20.0/test-blueprint/index.html | 395 ++
components/2.20.0/test-cdi/index.html | 1022 +++++
components/2.20.0/test-karaf/index.html | 211 +
components/2.20.0/test-spring/index.html | 976 +++++
components/2.20.0/test/index.html | 335 ++
components/2.20.0/testng/index.html | 205 +
components/2.20.0/thrift-component/index.html | 460 ++
components/2.20.0/thrift-dataformat/index.html | 401 ++
components/2.20.0/tidymarkup-dataformat/index.html | 312 ++
components/2.20.0/tika-component/index.html | 388 ++
components/2.20.0/twilio-component/index.html | 655 +++
components/2.20.0/twitter-component/index.html | 963 +++++
.../twitter-directmessage-component/index.html | 598 +++
.../2.20.0/twitter-search-component/index.html | 600 +++
.../2.20.0/twitter-streaming-component/index.html | 606 +++
.../2.20.0/twitter-timeline-component/index.html | 596 +++
components/2.20.0/twitter/index.html | 480 +++
components/2.20.0/undertow-component/index.html | 554 +++
.../2.20.0/univocity-csv-dataformat/index.html | 517 +++
.../2.20.0/univocity-fixed-dataformat/index.html | 511 +++
.../2.20.0/univocity-tsv-dataformat/index.html | 499 +++
components/2.20.0/urlrewrite/index.html | 476 +++
components/2.20.0/velocity-component/index.html | 636 +++
components/2.20.0/vertx-component/index.html | 435 ++
components/2.20.0/weather-component/index.html | 644 +++
components/2.20.0/websocket-component/index.html | 684 +++
components/2.20.0/xmlbeans-dataformat/index.html | 270 ++
components/2.20.0/xmljson-dataformat/index.html | 596 +++
components/2.20.0/xmlrpc-component/index.html | 527 +++
components/2.20.0/xmlrpc-dataformat/index.html | 268 ++
components/2.20.0/xmlsecurity-component/index.html | 1251 ++++++
components/2.20.0/xmpp-component/index.html | 520 +++
components/2.20.0/xquery-component/index.html | 747 ++++
components/2.20.0/xquery-language/index.html | 496 +++
components/2.20.0/xstream-dataformat/index.html | 412 ++
.../2.20.0/yaml-snakeyaml-dataformat/index.html | 440 ++
components/2.20.0/yammer-component/index.html | 829 ++++
components/2.20.0/zendesk-component/index.html | 422 ++
components/2.20.0/zipfile-dataformat/index.html | 404 ++
components/2.20.0/zipkin/index.html | 560 +++
components/2.20.0/zookeeper-component/index.html | 688 +++
.../2.20.0/zookeeper-master-component/index.html | 478 +++
components/index.html | 445 ++
components/index.xml | 4445 +++++++++++++++++++
components/page/1/index.html | 1 +
components/page/10/index.html | 461 ++
components/page/11/index.html | 461 ++
components/page/12/index.html | 461 ++
components/page/13/index.html | 461 ++
components/page/14/index.html | 461 ++
components/page/15/index.html | 461 ++
components/page/16/index.html | 461 ++
components/page/17/index.html | 461 ++
components/page/18/index.html | 461 ++
components/page/19/index.html | 461 ++
components/page/2/index.html | 457 ++
components/page/20/index.html | 461 ++
components/page/21/index.html | 461 ++
components/page/22/index.html | 461 ++
components/page/23/index.html | 461 ++
components/page/24/index.html | 461 ++
components/page/25/index.html | 461 ++
components/page/26/index.html | 461 ++
components/page/27/index.html | 461 ++
components/page/28/index.html | 461 ++
components/page/29/index.html | 461 ++
components/page/3/index.html | 458 ++
components/page/30/index.html | 461 ++
components/page/31/index.html | 461 ++
components/page/32/index.html | 461 ++
components/page/33/index.html | 461 ++
components/page/34/index.html | 458 ++
components/page/35/index.html | 457 ++
components/page/36/index.html | 370 ++
components/page/4/index.html | 461 ++
components/page/5/index.html | 461 ++
components/page/6/index.html | 461 ++
components/page/7/index.html | 461 ++
components/page/8/index.html | 461 ++
components/page/9/index.html | 461 ++
css/site.142da777720723dd4ecadc8e70926967.css | 1 +
favicon.ico | Bin 0 -> 766 bytes
humans.txt | 3 +
index.html | 120 +
index.xml | 4475 ++++++++++++++++++++
js/site.36395d52b78f93dc7cc7.js | 1 +
robots.txt | 5 +
sitemap.xml | 1447 +++++++
tile-wide.png | Bin 0 -> 1854 bytes
tile.png | Bin 0 -> 3482 bytes
versions/index.html | 114 +
versions/index.xml | 14 +
409 files changed, 244742 insertions(+)
diff --git a/404.html b/404.html
new file mode 100644
index 0000000..fce07b2
--- /dev/null
+++ b/404.html
@@ -0,0 +1 @@
+404 :)
diff --git a/about/index.html b/about/index.html
new file mode 100644
index 0000000..1dbe967
--- /dev/null
+++ b/about/index.html
@@ -0,0 +1,169 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='About Camel '>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='About Camel '>
+<meta property='og:url' content='https://camel.apache.org/about/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content=''>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/about/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect3">
+<h4 id="_about_camel">About Camel</h4>
+
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/apple-touch-icon.png b/apple-touch-icon.png
new file mode 100644
index 0000000..600738f
Binary files /dev/null and b/apple-touch-icon.png differ
diff --git a/browserconfig.xml b/browserconfig.xml
new file mode 100644
index 0000000..46de5d3
--- /dev/null
+++ b/browserconfig.xml
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Please read: http://msdn.microsoft.com/en-us/library/ie/dn455106.aspx -->
+<browserconfig>
+ <msapplication>
+ <tile>
+ <square70x70logo src="tile.png"/>
+ <square150x150logo src="tile.png"/>
+ <wide310x150logo src="tile-wide.png"/>
+ <square310x310logo src="tile.png"/>
+ </tile>
+ </msapplication>
+</browserconfig>
diff --git a/components/2.20.0/ahc-component/index.html b/components/2.20.0/ahc-component/index.html
new file mode 100644
index 0000000..d001384
--- /dev/null
+++ b/components/2.20.0/ahc-component/index.html
@@ -0,0 +1,867 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='AHC Component Available as of Camel version 2.8
+ The ahc: component provides HTTP based endpoints for consuming external HTTP resources (as a client to call external servers using HTTP).
+The component uses the Async Http Client library.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-ahc</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format ahc:http://hostname[:port][/resourceUri][?'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='AHC Component Available as of Camel version 2.8
+ The ahc: component provides HTTP based endpoints for consuming external HTTP resources (as a client to call external servers using HTTP).
+The component uses the Async Http Client library.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-ahc</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format ahc:http://hostname[:port][/resourceUri][?'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/ahc-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/ahc-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_ahc_component">AHC Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.8</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>ahc:</strong> component provides HTTP based <a href="endpoint.html">endpoints</a>
+for consuming external HTTP resources (as a client to call external
+servers using HTTP).<br>
+ The component uses the
+<a href="https://github.com/AsyncHttpClient/async-http-client">Async Http Client</a>
+library.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-ahc</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">ahc:http://hostname[:port][/resourceUri][?options]
+ahc:https://hostname[:port][/resourceUri][?options]</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Will by default use port 80 for HTTP and 443 for HTTPS.</p>
+</div>
+<div class="paragraph">
+<p>You can append query options to the URI in the following format,
+<code>?option=value&option=value&…​</code></p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ahcendpoint_options">AhcEndpoint Options</h3>
+<div class="paragraph">
+<p>The AHC endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>ahc:httpUri</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpUri</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The URI to use such as <a href="http://hostname:port/path" class="bare">http://hostname:port/path</a></p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">URI</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_13_parameters">Query Parameters (13 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeEndpoint</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If the option is true then the Exchange.HTTP_URI header is ignored and use the endpoint’s URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bufferSize</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The initial in-memory buffer size used when transferring data between Camel and AHC Client.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">4096</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>connectionClose</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cookieHandler</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configure a cookie handler to maintain a HTTP session</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CookieHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>throwExceptionOnFailure</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferException</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and an Exchange failed processing on the consumer side and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>binding</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom AhcBinding which allows to control how to bind between AHC and Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AhcBinding</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncHttpClientConfig</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfigOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClientConfig using the key/values from the Map.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfigRealmOptions</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClientConfig Realm using the key/values from the Map.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sslContextParameters</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SSLContextParameters</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ahccomponent_options">AhcComponent Options</h3>
+<div class="paragraph">
+<p>The AHC component supports 8 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>client</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom AsyncHttpClient</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncHttpClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>binding</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom AhcBinding which allows to control how to bind between AHC and Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AhcBinding</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncHttpClientConfig</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sslContextParameters</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SSLContextParameters</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowJavaSerialized Object</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useGlobalSslContext Parameters</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Enable usage of global SSL context parameters.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (filter)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>Notice that setting any of the options on the <code>AhcComponent</code> will
+propagate those options to
+<code>AhcEndpoints</code> being created. However the <code>AhcEndpoint</code> can also
+configure/override a custom option. Options set on endpoints will always
+take precedence over options from the <code>AhcComponent</code>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_message_headers">Message Headers</h3>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 10%;">
+<col style="width: 10%;">
+<col style="width: 80%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Type</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.HTTP_URI</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>String</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">URI to call. Will override existing URI set directly on the endpoint.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.HTTP_PATH</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>String</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Request URI’s path, the header will be used to build the request URI
+with the HTTP_URI. If the path is start with "/", http producer will try
+to find the relative path based on the Exchange.HTTP_BASE_URI header or
+the <code>exchange.getFromEndpoint().getEndpointUri();</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.HTTP_QUERY</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>String</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Camel 2.11 onwards:</strong> URI parameters. Will override existing URI
+parameters set directly on the endpoint.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.HTTP_RESPONSE_CODE</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>int</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The HTTP response code from the external server. Is 200 for OK.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.HTTP_CHARACTER_ENCODING</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>String</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Character encoding.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.CONTENT_TYPE</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>String</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The HTTP content type. Is set on both the IN and OUT message to provide
+a content type, such as <code>text/html</code>.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>Exchange.CONTENT_ENCODING</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>String</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The HTTP content encoding. Is set on both the IN and OUT message to
+provide a content encoding, such as <code>gzip</code>.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_message_body">Message Body</h3>
+<div class="paragraph">
+<p>Camel will store the HTTP response from the external server on the OUT
+body. All headers from the IN message will be copied to the OUT message,
+so headers are preserved during routing. Additionally Camel will add the
+HTTP response headers as well to the OUT message headers.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_response_code">Response code</h3>
+<div class="paragraph">
+<p>Camel will handle according to the HTTP response code:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Response code is in the range 100..299, Camel regards it as a success
+response.</p>
+</li>
+<li>
+<p>Response code is in the range 300..399, Camel regards it as a
+redirection response and will throw a <code>AhcOperationFailedException</code> with
+the information.</p>
+</li>
+<li>
+<p>Response code is 400+, Camel regards it as an external server failure
+and will throw a <code>AhcOperationFailedException</code> with the information.</p>
+<div class="paragraph">
+<p>throwExceptionOnFailure</p>
+</div>
+<div class="paragraph">
+<p>The option, <code>throwExceptionOnFailure</code>, can be set to <code>false</code> to prevent
+the <code>AhcOperationFailedException</code> from being thrown for failed response
+codes. This allows you to get any response from the remote server.</p>
+</div>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ahcoperationfailedexception">AhcOperationFailedException</h3>
+<div class="paragraph">
+<p>This exception contains the following information:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The HTTP status code</p>
+</li>
+<li>
+<p>The HTTP status line (text of the status code)</p>
+</li>
+<li>
+<p>Redirect location, if server returned a redirect</p>
+</li>
+<li>
+<p>Response body as a <code>java.lang.String</code>, if server provided a body as
+response</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_calling_using_get_or_post">Calling using GET or POST</h3>
+<div class="paragraph">
+<p>The following algorithm is used to determine if either <code>GET</code> or <code>POST</code>
+HTTP method should be used:<br>
+ 1. Use method provided in header.<br>
+ 2. <code>GET</code> if query string is provided in header.<br>
+ 3. <code>GET</code> if endpoint is configured with a query string.<br>
+ 4. <code>POST</code> if there is data to send (body is not null).<br>
+ 5. <code>GET</code> otherwise.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_uri_to_call">Configuring URI to call</h3>
+<div class="paragraph">
+<p>You can set the HTTP producer’s URI directly form the endpoint URI. In
+the route below, Camel will call out to the external server, <code>oldhost</code>,
+using HTTP.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .to("ahc:http://oldhost");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And the equivalent Spring sample:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
+ <route>
+ <from uri="direct:start"/>
+ <to uri="ahc:http://oldhost"/>
+ </route>
+</camelContext></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>You can override the HTTP endpoint URI by adding a header with the key,
+<code>Exchange.HTTP_URI</code>, on the message.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .setHeader(Exchange.HTTP_URI, constant("http://newhost"))
+ .to("ahc:http://oldhost");</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_uri_parameters">Configuring URI Parameters</h3>
+<div class="paragraph">
+<p>The <strong>ahc</strong> producer supports URI parameters to be sent to the HTTP
+server. The URI parameters can either be set directly on the endpoint
+URI or as a header with the key <code>Exchange.HTTP_QUERY</code> on the message.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .to("ahc:http://oldhost?order=123&detail=short");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Or options provided in a header:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .setHeader(Exchange.HTTP_QUERY, constant("order=123&detail=short"))
+ .to("ahc:http://oldhost");</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_how_to_set_the_http_method_to_the_http_producer">How to set the http method to the HTTP producer</h3>
+<div class="paragraph">
+<p>The HTTP component provides a way to set the HTTP request method by
+setting the message header. Here is an example;</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .setHeader(Exchange.HTTP_METHOD, constant("POST"))
+ .to("ahc:http://www.google.com")
+ .to("mock:results");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And the equivalent Spring sample:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
+ <route>
+ <from uri="direct:start"/>
+ <setHeader headerName="CamelHttpMethod">
+ <constant>POST</constant>
+ </setHeader>
+ <to uri="ahc:http://www.google.com"/>
+ <to uri="mock:results"/>
+ </route>
+</camelContext></code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_charset">Configuring charset</h3>
+<div class="paragraph">
+<p>If you are using <code>POST</code> to send data you can configure the <code>charset</code>
+using the <code>Exchange</code> property:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">exchange.setProperty(Exchange.CHARSET_NAME, "iso-8859-1");</code></pre>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_uri_parameters_from_the_endpoint_uri">URI Parameters from the endpoint URI</h4>
+<div class="paragraph">
+<p>In this sample we have the complete URI endpoint that is just what you
+would have typed in a web browser. Multiple URI parameters can of course
+be set using the <code>&</code> character as separator, just as you would in the
+web browser. Camel does no tricks here.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">// we query for Camel at the Google page
+template.sendBody("ahc:http://www.google.com/search?q=Camel", null);</code></pre>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_uri_parameters_from_the_message">URI Parameters from the Message</h4>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">Map headers = new HashMap();
+headers.put(Exchange.HTTP_QUERY, "q=Camel&lr=lang_en");
+// we query for Camel and English language at Google
+template.sendBody("ahc:http://www.google.com/search", null, headers);</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the header value above notice that it should <strong>not</strong> be prefixed with
+<code>?</code> and you can separate parameters as usual with the <code>&</code> char.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_getting_the_response_code">Getting the Response Code</h4>
+<div class="paragraph">
+<p>You can get the HTTP response code from the AHC component by getting the
+value from the Out message header with <code>Exchange.HTTP_RESPONSE_CODE</code>.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">Exchange exchange = template.send("ahc:http://www.google.com/search", new Processor() {
+ public void process(Exchange exchange) throws Exception {
+ exchange.getIn().setHeader(Exchange.HTTP_QUERY, constant("hl=en&q=activemq"));
+ }
+ });
+ Message out = exchange.getOut();
+ int responseCode = out.getHeader(Exchange.HTTP_RESPONSE_CODE, Integer.class);</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_asynchttpclient">Configuring AsyncHttpClient</h3>
+<div class="paragraph">
+<p>The <code>AsyncHttpClient</code> client uses a <code>AsyncHttpClientConfig</code> to configure
+the client. See the documentation at<br>
+ <a href="http://github.com/sonatype/async-http-client">Async Http Client</a> for
+more details.</p>
+</div>
+<div class="paragraph">
+<p>In Camel <strong>2.8</strong>, configuration is limited to using the builder pattern
+provided by <code>AsyncHttpClientConfig.Builder</code>. In Camel 2.8, the
+<code>AsyncHttpClientConfig</code> doesn’t support getters/setters so its not easy
+to create/configure using a Spring bean style (eg the <bean> tag in the
+XML file).</p>
+</div>
+<div class="paragraph">
+<p>The example below shows how to use a builder to create the
+<code>AsyncHttpClientConfig</code> which we configure on the <code>AhcComponent</code>.</p>
+</div>
+<div class="paragraph">
+<p>In Camel <strong>2.9</strong>, the AHC component uses Async HTTP library 1.6.4. This
+newer version provides added support for plain bean style configuration.
+The <code>AsyncHttpClientConfigBean</code> class provides getters and setters for
+the configuration options available in <code>AsyncHttpClientConfig</code>. An
+instance of <code>AsyncHttpClientConfigBean</code> may be passed directly to the
+AHC component or referenced in an endpoint URI using the <code>clientConfig</code>
+URI parameter.</p>
+</div>
+<div class="paragraph">
+<p>Also available in Camel <strong>2.9</strong> is the ability to set configuration
+options directly in the URI. URI parameters starting with
+"clientConfig." can be used to set the various configurable properties
+of <code>AsyncHttpClientConfig</code>. The properties specified in the endpoint URI
+are merged with those specified in the configuration referenced by the
+"clientConfig" URI parameter with those being set using the
+"clientConfig." parameter taking priority. The <code>AsyncHttpClientConfig</code>
+instance referenced is always copied for each endpoint such that
+settings on one endpoint will remain independent of settings on any
+previously created endpoints. The example below shows how to configure
+the AHC component using the "clientConfig." type URI parameters.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .to("ahc:http://localhost:8080/foo?clientConfig.maxRequestRetry=3&clientConfig.followRedirects=true")</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ssl_support_https">SSL Support (HTTPS)</h3>
+<div id="AHC-UsingtheJSSEConfigurationUtility" class="paragraph">
+<p>Using the JSSE Configuration Utility</p>
+</div>
+<div class="paragraph">
+<p>As of Camel 2.9, the AHC component supports SSL/TLS configuration
+through the <a href="camel-configuration-utilities.html">Camel JSSE
+Configuration Utility</a>. This utility greatly decreases the amount of
+component specific code you need to write and is configurable at the
+endpoint and component levels. The following examples demonstrate how
+to use the utility with the AHC component.</p>
+</div>
+<div id="AHC-Programmaticconfigurationofthecomponent" class="paragraph">
+<p>Programmatic configuration of the component</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">KeyStoreParameters ksp = new KeyStoreParameters();
+ksp.setResource("/users/home/server/keystore.jks");
+ksp.setPassword("keystorePassword");
+
+KeyManagersParameters kmp = new KeyManagersParameters();
+kmp.setKeyStore(ksp);
+kmp.setKeyPassword("keyPassword");
+
+SSLContextParameters scp = new SSLContextParameters();
+scp.setKeyManagers(kmp);
+
+AhcComponent component = context.getComponent("ahc", AhcComponent.class);
+component.setSslContextParameters(scp));</code></pre>
+</div>
+</div>
+<div id="AHC-SpringDSLbasedconfigurationofendpoint" class="paragraph">
+<p>Spring DSL based configuration of endpoint</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml">...
+ <camel:sslContextParameters
+ id="sslContextParameters">
+ <camel:keyManagers
+ keyPassword="keyPassword">
+ <camel:keyStore
+ resource="/users/home/server/keystore.jks"
+ password="keystorePassword"/>
+ </camel:keyManagers>
+ </camel:sslContextParameters>...
+...
+ <to uri="ahc:https://localhost/foo?sslContextParameters=#sslContextParameters"/>
+...</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="configuring-camel.html">Configuring Camel</a></p>
+</li>
+<li>
+<p><a href="component.html">Component</a></p>
+</li>
+<li>
+<p><a href="endpoint.html">Endpoint</a></p>
+</li>
+<li>
+<p><a href="getting-started.html">Getting Started</a></p>
+</li>
+<li>
+<p><a href="jetty.html">Jetty</a></p>
+</li>
+<li>
+<p><a href="http.html">HTTP</a></p>
+</li>
+<li>
+<p><a href="http4.html">HTTP4</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/ahc-ws-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/ahc-ws-component/index.html b/components/2.20.0/ahc-ws-component/index.html
new file mode 100644
index 0000000..31fc174
--- /dev/null
+++ b/components/2.20.0/ahc-ws-component/index.html
@@ -0,0 +1,561 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='AHC Websocket Component Available as of Camel version 2.14
+ The ahc-ws component provides Websocket based endpoints for a client communicating with external servers over Websocket (as a client opening a websocket connection to an external server).
+The component uses the AHC component that in turn uses the https://github.com/AsyncHttpClient/async-http-client[Async Http Client] library.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='AHC Websocket Component Available as of Camel version 2.14
+ The ahc-ws component provides Websocket based endpoints for a client communicating with external servers over Websocket (as a client opening a websocket connection to an external server).
+The component uses the AHC component that in turn uses the https://github.com/AsyncHttpClient/async-http-client[Async Http Client] library.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/ahc-ws-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/ahc-ws-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_ahc_websocket_component">AHC Websocket Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.14</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>ahc-ws</strong> component provides Websocket
+based <a href="endpoint.html">endpoints</a> for a client communicating with
+external servers over Websocket (as a client opening a websocket
+connection to an external server).<br>
+The component uses the <a href="ahc.html">AHC</a> component that in turn uses
+the https://github.com/AsyncHttpClient/async-http-client[Async Http
+Client] library.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to
+their <code>pom.xml</code> for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-ahc-ws</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI Format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">ahc-ws://hostname[:port][/resourceUri][?options]
+ahc-wss://hostname[:port][/resourceUri][?options]</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Will by default use port 80 for ahc-ws and 443 for ahc-wss.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ahc_ws_options">AHC-WS Options</h3>
+<div class="paragraph">
+<p>As the AHC-WS component is based on the AHC component, you can use the
+various configuration options of the AHC component.</p>
+</div>
+<div class="paragraph">
+<p>The AHC Websocket component supports 8 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>client</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom AsyncHttpClient</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncHttpClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>binding</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom AhcBinding which allows to control how to bind between AHC and Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AhcBinding</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncHttpClientConfig</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sslContextParameters</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SSLContextParameters</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowJavaSerialized Object</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useGlobalSslContext Parameters</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Enable usage of global SSL context parameters.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (filter)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The AHC Websocket endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>ahc-ws:httpUri</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpUri</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The URI to use such as <a href="http://hostname:port/path" class="bare">http://hostname:port/path</a></p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">URI</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_18_parameters">Query Parameters (18 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeEndpoint</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If the option is true then the Exchange.HTTP_URI header is ignored and use the endpoint’s URI for request. You may also set the throwExceptionOnFailure to be false to let the AhcProducer send all the fault response back.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bufferSize</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The initial in-memory buffer size used when transferring data between Camel and AHC Client.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">4096</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>throwExceptionOnFailure</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Option to disable throwing the AhcOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferException</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and an Exchange failed processing on the consumer side and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type (for example using Jetty or Servlet Camel components). On the producer side the exception will be deserialized and thrown as is instead of the AhcOperationFailedException. The caused exception is required to be serialized. This is by [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sendMessageOnError</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to send an message if the web-socket listener received an error.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>connectionClose</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Define if the Connection Close header has to be added to HTTP Request. This parameter is false by default</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cookieHandler</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configure a cookie handler to maintain a HTTP session</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CookieHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useStreaming</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To enable streaming to send data as multiple text fragments.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>binding</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom AhcBinding which allows to control how to bind between AHC and Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AhcBinding</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsyncHttpClientConfig</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfigOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClientConfig using the key/values from the Map.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientConfigRealmOptions</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure the AsyncHttpClientConfig Realm using the key/values from the Map.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sslContextParameters</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility. Note that configuring this option will override any SSL/TLS configuration options provided through the clientConfig option at the endpoint or component level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SSLContextParameters</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_writing_and_reading_data_over_websocket">Writing and Reading Data over Websocket</h3>
+<div class="paragraph">
+<p>An ahc-ws endpoint can either write data to the socket or read from the
+socket, depending on whether the endpoint is configured as the producer
+or the consumer, respectively.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_uri_to_write_or_read_data">Configuring URI to Write or Read Data</h3>
+<div class="paragraph">
+<p>In the route below, Camel will write to the specified websocket
+connection.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+ .to("ahc-ws://targethost");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And the equivalent Spring sample:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><camelContext xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="direct:start"/>
+ <to uri="ahc-ws://targethost"/>
+ </route>
+</camelContext></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the route below, Camel will read from the specified websocket
+connection.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("ahc-ws://targethost")
+ .to("direct:next");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And the equivalent Spring sample:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><camelContext xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="ahc-ws://targethost"/>
+ <to uri="direct:next"/>
+ </route>
+</camelContext></code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="configuring-camel.html">Configuring Camel</a></p>
+</li>
+<li>
+<p><a href="component.html">Component</a></p>
+</li>
+<li>
+<p><a href="endpoint.html">Endpoint</a></p>
+</li>
+<li>
+<p><a href="getting-started.html">Getting Started</a></p>
+</li>
+<li>
+<p><a href="../../../../camel-ahc/src/main/docs/readme.html">AHC</a></p>
+</li>
+<li>
+<p><a href="atmosphere-websocket.html">Atmosphere-Websocket</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/amqp-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/ahc-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/amqp-component/index.html b/components/2.20.0/amqp-component/index.html
new file mode 100644
index 0000000..bd7f2a1
--- /dev/null
+++ b/components/2.20.0/amqp-component/index.html
@@ -0,0 +1,1435 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='AMQP Component Available as of Camel version 1.2
+ The amqp: component supports the AMQP 1.0 protocol using the JMS Client API of the Qpid project. In case you want to use AMQP 0.9 (in particular RabbitMQ) you might also be interested in the Camel RabbitMQ component. Please keep in mind that prior to the Camel 2.17.0 AMQP component supported AMQP 0.9 and above, however since Camel 2.17.0 it supports only AMQP 1.'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='AMQP Component Available as of Camel version 1.2
+ The amqp: component supports the AMQP 1.0 protocol using the JMS Client API of the Qpid project. In case you want to use AMQP 0.9 (in particular RabbitMQ) you might also be interested in the Camel RabbitMQ component. Please keep in mind that prior to the Camel 2.17.0 AMQP component supported AMQP 0.9 and above, however since Camel 2.17.0 it supports only AMQP 1.'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/amqp-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/amqp-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_amqp_component">AMQP Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 1.2</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>amqp:</strong> component supports the <a href="http://www.amqp.org/">AMQP 1.0
+protocol</a> using the JMS Client API of the <a href="http://qpid.apache.org/">Qpid</a>
+project. In case you want to use AMQP 0.9 (in particular RabbitMQ) you
+might also be interested in the <a href="rabbitmq.html">Camel RabbitMQ</a>
+component. Please keep in mind that prior to the Camel 2.17.0 AMQP
+component supported AMQP 0.9 and above, however since Camel 2.17.0 it
+supports only AMQP 1.0.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-amqp</artifactId>
+ <version>${camel.version}</version> <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">amqp:[queue:|topic:]destinationName[?options]</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_amqp_options">AMQP Options</h3>
+<div class="paragraph">
+<p>You can specify all of the various configuration options of the
+<a href="../../../../camel-jms/src/main/docs/readme.html">JMS</a> component after the destination name.</p>
+</div>
+<div class="paragraph">
+<p>The AMQP component supports 75 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a shared JMS configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">JmsConfiguration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>acceptMessagesWhile Stopping</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option if you start and stop JMS routes at runtime while there are still messages enqueued on the queue. If this option is false and you stop the JMS route then messages may be rejected and the JMS broker would have to attempt redeliveries which yet again may be rejected and eventually the message may be moved at a dead le [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowReplyManagerQuick Stop</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfigurationisAcceptMessagesWhileStopping is enabled and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enabl [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>acknowledgementMode</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The JMS acknowledgement mode defined as an Integer. Allows you to set vendor-specific extensions to the acknowledgment mode.For the regular modes it is preferable to use the acknowledgementModeName instead.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>eagerLoadingOf Properties</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Enables eager loading of JMS properties as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>acknowledgementModeName</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The JMS acknowledgement name which is one of: SESSION_TRANSACTED CLIENT_ACKNOWLEDGE AUTO_ACKNOWLEDGE DUPS_OK_ACKNOWLEDGE</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">AUTO_ ACKNOWLEDGE</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>autoStartup</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether the consumer container should auto-startup.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cacheLevel</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cacheLevelName</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO CACHE_CONNECTION CACHE_CONSUMER CACHE_NONE and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">CACHE_AUTO</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToCacheLevelName</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If usin [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientId</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the JMS client ID to use. Note that this value if specified must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>concurrentConsumers</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToConcurrent Consumers</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>connectionFactory</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The connection factory to be use. A connection factory must be configured either on the component or endpoint.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ConnectionFactory</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>username</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>password</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>deliveryPersistent</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether persistent delivery is used by default.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>deliveryMode</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Integer</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>durableSubscriptionName</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionListener</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionListener</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>errorHandler</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure than h [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ErrorHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>errorHandlerLogging Level</strong> (logging)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows to configure the default errorHandler logging level for logging uncaught exceptions.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">WARN</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">LoggingLevel</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>errorHandlerLogStack Trace</strong> (logging)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows to control whether stacktraces should be logged or not by the default errorHandler.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>explicitQosEnabled</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Set if the deliveryMode priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring’s JmsTemplate. The deliveryMode priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option which operates at message granularity reading QoS properties exclusively from the Camel In message headers.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exposeListenerSession</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether the listener session should be exposed when consuming messages.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>idleTaskExecutionLimit</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the limit for idle executions of a receive task not having received any message within its execution. If this limit is reached the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>idleConsumerLimit</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specify the limit for the number of consumers that are allowed to be idle at any given time.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>maxConcurrentConsumers</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToMaxConcurrent Consumers</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyOnTimeoutToMax ConcurrentConsumers</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>maxMessagesPerTask</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max) then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageConverter</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MessageConverter</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>mapJmsMessage</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether Camel should auto map the received JMS message to a suited payload type such as javax.jms.TextMessage to a String etc.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageIdEnabled</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When sending specifies whether message IDs should be added. This is just an hint to the JMS broker.If the JMS provider accepts this hint these messages must have the message ID set to null; if the provider ignores the hint the message ID must be set to its normal unique value</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageTimestampEnabled</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker.If the JMS provider accepts this hint these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>alwaysCopyMessage</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If true Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations such as when a replyToDestinationSelectorName is set (incidentally Camel will set the alwaysCopyMessage option to true if a replyToDestinationSelectorName is set)</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useMessageIDAs CorrelationID</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>priority</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">4</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>pubSubNoLocal</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to inhibit the delivery of messages published by its own connection.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>receiveTimeout</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The timeout for receiving messages (in milliseconds).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>recoveryInterval</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the interval between recovery attempts i.e. when a connection is being refreshed in milliseconds. The default is 5000 ms that is 5 seconds.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">5000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>subscriptionDurable</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Deprecated: Enabled by default if you specify a durableSubscriptionName and a clientId.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>taskExecutor</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows you to specify a custom task executor for consuming messages.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TaskExecutor</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>timeToLive</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When sending messages specifies the time-to-live of the message (in milliseconds).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transacted</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to use transacted mode</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>lazyCreateTransaction Manager</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If true Camel will create a JmsTransactionManager if there is no transactionManager injected when option transacted=true.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transactionManager</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Spring transaction manager to use.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">PlatformTransaction Manager</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transactionName</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The name of the transaction to use.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transactionTimeout</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The timeout value of the transaction (in seconds) if using transacted mode.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>testConnectionOn Startup</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>asyncStartListener</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to startup the JmsConsumer message listener asynchronously when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true you will let routes startup while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>asyncStopListener</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to stop the JmsConsumer message listener asynchronously when stopping a route.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>forceSendOriginal Message</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>requestTimeout</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">20000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>requestTimeoutChecker Interval</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs then you can lower this interval to check more frequently. The timeout is determined by the option requestTimeout.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferExchange</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body Out body Fault body In headers Out headers Fault headers exchange properties exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side so Camel [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferException</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example using persistent queues to enable robust routing. Notice that if you also have transferExchange ena [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferFault</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and you are using Request Reply messaging (InOut) and an Exchange failed with a SOAP fault (not exception) on the consumer side then the fault flag on MessageisFault() will be send back in the response as a JMS header with the key org.apache.camel.component.jms.JmsConstantsJMS_TRANSFER_FAULTJMS_TRANSFER_FAULT. If the client is Camel the returned fault flag will be set on the link org.apache.camel.MessagesetFau [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>jmsOperations</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows you to use your own implementation of the org.springframework.jms.core.JmsOperations interface. Camel uses JmsTemplate as default. Can be used for testing purpose but not used much as stated in the spring API docs.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">JmsOperations</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>destinationResolver</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example to lookup the real destination in a JNDI registry).</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">DestinationResolver</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToType</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary Shared or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details and especially the notes [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReplyToType</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>preserveMessageQos</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Set to true if you want to send message using the QoS settings specified on the message instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority JMSDeliveryMode and JMSExpiration. You can provide all or only some of them. If not provided Camel will fall back to use the values from the endpoint instead. So when using this option the headers override the values from the endpoi [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>asyncConsumer</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100 strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowNullBody</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to allow sending messages with no body. If this option is false and the message body is null then an JMSException is thrown.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>includeSentJMS MessageID</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>includeAllJMSX Properties</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultTaskExecutor Type</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring’s SimpleAsyncTaskExecutor) or ThreadPool (uses Spring’s ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set it defaults to the previous behaviour which uses a cached thread pool [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">DefaultTaskExecutor Type</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>jmsKeyFormatStrategy</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own im [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">JmsKeyFormatStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>queueBrowseStrategy</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom QueueBrowseStrategy when browsing queues</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">QueueBrowseStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageCreatedStrategy</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MessageCreatedStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>waitForProvision CorrelationToBeUpdated Counter</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">50</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>waitForProvision CorrelationToBeUpdated ThreadSleepingTime</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Interval in millis to sleep each time while waiting for provisional correlation id to be updated.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">100</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>correlationProperty</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Use this JMS property to correlate messages in InOut exchange pattern (request-reply) instead of JMSCorrelationID property. This allows you to exchange messages with systems that do not correlate messages using JMSCorrelationID JMS property. If used JMSCorrelationID will not be used or set by Camel. The value of here named property will be generated if not supplied in the header of the message under the same name.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (filter)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The AMQP endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>amqp:destinationType:destinationName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_2_parameters">Path Parameters (2 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>destinationType</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The kind of destination to use</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">queue</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>destinationName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Name of the queue or topic to use as destination</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_85_parameters">Query Parameters (85 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>clientId</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the JMS client ID to use. Note that this value if specified must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>connectionFactory</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The connection factory to be use. A connection factory must be configured either on the component or endpoint.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ConnectionFactory</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>disableReplyTo</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If true a producer will behave like a InOnly exchange with the exception that JMSReplyTo header is sent out and not be suppressed like in the case of InOnly. Like InOnly the producer will not wait for a reply. A consumer with this flag will behave like InOnly. This feature can be used to bridge InOut requests to another queue so that a route on the other queue will send its response directly back to the original JMSReply [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>durableSubscriptionName</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>jmsMessageType</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes Map Object Stream Text. By default Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">JmsMessageType</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>testConnectionOnStartup</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>acknowledgementModeName</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The JMS acknowledgement name which is one of: SESSION_TRANSACTED CLIENT_ACKNOWLEDGE AUTO_ACKNOWLEDGE DUPS_OK_ACKNOWLEDGE</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">AUTO_ ACKNOWLEDGE</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>asyncConsumer</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100 strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>autoStartup</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether the consumer container should auto-startup.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cacheLevel</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cacheLevelName</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO CACHE_CONNECTION CACHE_CONSUMER CACHE_NONE and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">CACHE_AUTO</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>concurrentConsumers</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>maxConcurrentConsumers</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyTo</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Provides an explicit ReplyTo destination which overrides any incoming value of Message.getJMSReplyTo().</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToDeliveryPersistent</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to use persistent delivery by default for replies.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>selector</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the JMS selector to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>acceptMessagesWhileStopping</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option if you start and stop JMS routes at runtime while there are still messages enqueued on the queue. If this option is false and you stop the JMS route then messages may be rejected and the JMS broker would have to attempt redeliveries which yet again may be rejected and eventually the message may be moved at a dead le [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowReplyManagerQuickStop</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfigurationisAcceptMessagesWhileStopping is enabled and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enabl [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>consumerType</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The consumer type to use which can be one of: Simple Default or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determ [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">Default</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ConsumerType</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultTaskExecutorType</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring’s SimpleAsyncTaskExecutor) or ThreadPool (uses Spring’s ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set it defaults to the previous behaviour which uses a cached thread pool [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">DefaultTaskExecutor Type</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>eagerLoadingOfProperties</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Enables eager loading of JMS properties as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exposeListenerSession</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether the listener session should be exposed when consuming messages.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToSameDestination Allowed</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>taskExecutor</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows you to specify a custom task executor for consuming messages.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TaskExecutor</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>deliveryMode</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT = 1 and PERSISTENT = 2.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Integer</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>deliveryPersistent</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether persistent delivery is used by default.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>explicitQosEnabled</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Set if the deliveryMode priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring’s JmsTemplate. The deliveryMode priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option which operates at message granularity reading QoS properties exclusively from the Camel In message headers.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>preserveMessageQos</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Set to true if you want to send message using the QoS settings specified on the message instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority JMSDeliveryMode and JMSExpiration. You can provide all or only some of them. If not provided Camel will fall back to use the values from the endpoint instead. So when using this option the headers override the values from the endpoi [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>priority</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">4</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToConcurrentConsumers</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToMaxConcurrent Consumers</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToOnTimeoutMax ConcurrentConsumers</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToOverride</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Provides an explicit ReplyTo destination in the JMS message which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToType</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary Shared or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details and especially the notes [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReplyToType</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>requestTimeout</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">20000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>timeToLive</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When sending messages specifies the time-to-live of the message (in milliseconds).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowNullBody</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to allow sending messages with no body. If this option is false and the message body is null then an JMSException is thrown.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>alwaysCopyMessage</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If true Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations such as when a replyToDestinationSelectorName is set (incidentally Camel will set the alwaysCopyMessage option to true if a replyToDestinationSelectorName is set)</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>correlationProperty</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>disableTimeToLive</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Use this option to force disabling time to live. For example when you do request/reply over JMS then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive=true to not set a time to live value on the s [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>forceSendOriginalMessage</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When using mapJmsMessage=false Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>includeSentJMSMessageID</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToCacheLevelName</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName=CACHE_NONE to work. Note: If usin [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>replyToDestinationSelector Name</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is if you are not using a temporary reply queue).</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowSerializedHeaders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>asyncStartListener</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to startup the JmsConsumer message listener asynchronously when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true you will let routes startup while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>asyncStopListener</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to stop the JmsConsumer message listener asynchronously when stopping a route.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>destinationResolver</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example to lookup the real destination in a JNDI registry).</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">DestinationResolver</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>errorHandler</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure than h [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ErrorHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionListener</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionListener</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>idleConsumerLimit</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specify the limit for the number of consumers that are allowed to be idle at any given time.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>idleTaskExecutionLimit</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the limit for idle executions of a receive task not having received any message within its execution. If this limit is reached the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>includeAllJMSXProperties</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>jmsKeyFormatStrategy</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own im [...]
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>mapJmsMessage</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether Camel should auto map the received JMS message to a suited payload type such as javax.jms.TextMessage to a String etc.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>maxMessagesPerTask</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max) then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageConverter</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MessageConverter</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageCreatedStrategy</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MessageCreatedStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageIdEnabled</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When sending specifies whether message IDs should be added. This is just an hint to the JMS broker.If the JMS provider accepts this hint these messages must have the message ID set to null; if the provider ignores the hint the message ID must be set to its normal unique value</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageListenerContainer Factory</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MessageListener ContainerFactory</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageTimestampEnabled</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker.If the JMS provider accepts this hint these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>pubSubNoLocal</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to inhibit the delivery of messages published by its own connection.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>receiveTimeout</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The timeout for receiving messages (in milliseconds).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>recoveryInterval</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies the interval between recovery attempts i.e. when a connection is being refreshed in milliseconds. The default is 5000 ms that is 5 seconds.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">5000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>requestTimeoutChecker Interval</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs then you can lower this interval to check more frequently. The timeout is determined by the option requestTimeout.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferException</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example using persistent queues to enable robust routing. Notice that if you also have transferExchange ena [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferExchange</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body Out body Fault body In headers Out headers Fault headers exchange properties exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side so Camel [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferFault</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and you are using Request Reply messaging (InOut) and an Exchange failed with a SOAP fault (not exception) on the consumer side then the fault flag on MessageisFault() will be send back in the response as a JMS header with the key org.apache.camel.component.jms.JmsConstantsJMS_TRANSFER_FAULTJMS_TRANSFER_FAULT. If the client is Camel the returned fault flag will be set on the link org.apache.camel.MessagesetFau [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useMessageIDAsCorrelation ID</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>waitForProvisionCorrelation ToBeUpdatedCounter</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">50</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>waitForProvisionCorrelation ToBeUpdatedThreadSleeping Time</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Interval in millis to sleep each time while waiting for provisional correlation id to be updated.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">100</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>errorHandlerLoggingLevel</strong> (logging)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows to configure the default errorHandler logging level for logging uncaught exceptions.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">WARN</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">LoggingLevel</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>errorHandlerLogStackTrace</strong> (logging)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows to control whether stacktraces should be logged or not by the default errorHandler.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>password</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>username</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transacted</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to use transacted mode</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>lazyCreateTransaction Manager</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If true Camel will create a JmsTransactionManager if there is no transactionManager injected when option transacted=true.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transactionManager</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Spring transaction manager to use.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">PlatformTransaction Manager</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transactionName</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The name of the transaction to use.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transactionTimeout</strong> (transaction)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The timeout value of the transaction (in seconds) if using transacted mode.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">-1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_usage">Usage</h3>
+<div class="paragraph">
+<p>As AMQP component is inherited from JMS component, the usage of the
+former is almost identical to the latter:</p>
+</div>
+<div class="paragraph">
+<p><strong>Using AMQP component</strong></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">// Consuming from AMQP queue
+from("amqp:queue:incoming").
+ to(...);
+
+// Sending message to the AMQP topic
+from(...).
+ to("amqp:topic:notify");</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_amqp_component">Configuring AMQP component</h3>
+<div class="paragraph">
+<p>Starting from the Camel 2.16.1 you can also use the
+<code>AMQPComponent#amqp10Component(String connectionURI)</code> factory method to
+return the AMQP 1.0 component with the pre-configured topic prefix:</p>
+</div>
+<div class="paragraph">
+<p><strong>Creating AMQP 1.0 component</strong></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> AMQPComponent amqp = AMQPComponent.amqp10Component("amqp://guest:guest@localhost:5672");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Keep in mind that starting from the
+Camel 2.17 the <code>AMQPComponent#amqp10Component(String connectionURI)</code> factory
+method has been deprecated on the behalf of the
+<code>AMQPComponent#amqpComponent(String connectionURI)</code>:</p>
+</div>
+<div class="paragraph">
+<p><strong>Creating AMQP 1.0 component</strong></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">AMQPComponent amqp = AMQPComponent.amqpComponent("amqp://localhost:5672");
+
+AMQPComponent authorizedAmqp = AMQPComponent.amqpComponent("amqp://localhost:5672", "user", "password");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Starting from Camel 2.17, in order to automatically configure the AMQP
+component, you can also add an instance
+of <code>org.apache.camel.component.amqp.AMQPConnectionDetails</code> to the
+registry. For example for Spring Boot you just have to define bean:</p>
+</div>
+<div class="paragraph">
+<p><strong>AMQP connection details auto-configuration</strong></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">@Bean
+AMQPConnectionDetails amqpConnection() {
+ return new AMQPConnectionDetails("amqp://localhost:5672");
+}
+
+@Bean
+AMQPConnectionDetails securedAmqpConnection() {
+ return new AMQPConnectionDetails("amqp://lcoalhost:5672", "username", "password");
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Likewise, you can also use CDI producer methods when using Camel-CDI</p>
+</div>
+<div class="paragraph">
+<p><strong>AMQP connection details auto-configuration for CDI</strong></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">@Produces
+AMQPConnectionDetails amqpConnection() {
+ return new AMQPConnectionDetails("amqp://localhost:5672");
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>You can also rely on the <a href="properties.html">Camel properties</a> to read
+the AMQP connection details. Factory
+method <code>AMQPConnectionDetails.discoverAMQP()</code> attempts to read Camel
+properties in a Kubernetes-like convention, just as demonstrated on the
+snippet below:</p>
+</div>
+<div class="paragraph">
+<p><strong>AMQP connection details auto-configuration</strong></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">export AMQP_SERVICE_HOST = "mybroker.com"
+export AMQP_SERVICE_PORT = "6666"
+export AMQP_SERVICE_USERNAME = "username"
+export AMQP_SERVICE_PASSWORD = "password"
+
+...
+
+@Bean
+AMQPConnectionDetails amqpConnection() {
+ return AMQPConnectionDetails.discoverAMQP();
+}</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_topics">Using topics</h3>
+<div class="paragraph">
+<p>To have using topics working with <code>camel-amqp</code> you need to configure the
+component to use <code>topic://</code> as topic prefix, as shown below:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <bean id="amqp" class="org.apache.camel.component.amqp.AmqpComponent">
+ <property name="connectionFactory">
+ <bean class="org.apache.qpid.jms.JmsConnectionFactory" factory-method="createFromURL">
+ <property name="remoteURI" value="amqp://localhost:5672" />
+ <property name="topicPrefix" value="topic://" /> <!-- only necessary when connecting to ActiveMQ over AMQP 1.0 -->
+ </bean>
+ </property>
+ </bean></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Keep in mind that both <code>AMQPComponent#amqpComponent()</code> methods and
+<code>AMQPConnectionDetails</code> pre-configure the component with the topic
+prefix, so you don’t have to configure it explicitly.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="configuring-camel.html">Configuring Camel</a></p>
+</li>
+<li>
+<p><a href="component.html">Component</a></p>
+</li>
+<li>
+<p><a href="endpoint.html">Endpoint</a></p>
+</li>
+<li>
+<p><a href="getting-started.html">Getting Started</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/apns-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/ahc-ws-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/apns-component/index.html b/components/2.20.0/apns-component/index.html
new file mode 100644
index 0000000..f74d613
--- /dev/null
+++ b/components/2.20.0/apns-component/index.html
@@ -0,0 +1,706 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='APNS Component Available as of Camel version 2.8
+ The apns component is used for sending notifications to iOS devices. The apns components use javapns library.
+The component supports sending notifications to Apple Push Notification Servers (APNS) and consuming feedback from the servers.
+ The consumer is configured with 3600 seconds for polling by default because it is a best practice to consume feedback stream from Apple Push Notification Servers only from time to time.'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='APNS Component Available as of Camel version 2.8
+ The apns component is used for sending notifications to iOS devices. The apns components use javapns library.
+The component supports sending notifications to Apple Push Notification Servers (APNS) and consuming feedback from the servers.
+ The consumer is configured with 3600 seconds for polling by default because it is a best practice to consume feedback stream from Apple Push Notification Servers only from time to time.'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/apns-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/apns-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_apns_component">APNS Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.8</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>apns</strong> component is used for sending notifications to iOS devices.
+The apns components use <a href="https://github.com/notnoop/java-apns">javapns</a>
+library.<br>
+ The component supports sending notifications to Apple Push Notification
+Servers (APNS) and consuming feedback from the servers.</p>
+</div>
+<div class="paragraph">
+<p>The consumer is configured with 3600 seconds for polling by default
+because it is a best practice to consume feedback stream from Apple Push
+Notification Servers only from time to time. For example: every 1 hour
+to avoid flooding the servers.</p>
+</div>
+<div class="paragraph">
+<p>The feedback stream gives informations about inactive devices. You only
+need to get this informations every some hours if your mobile
+application is not a heavily used one.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-apns</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="paragraph">
+<p>To send notifications:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">apns:notify[?options]</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>To consume feedback:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">apns:consumer[?options]</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_options">Options</h3>
+<div class="paragraph">
+<p>The APNS component supports 2 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>apnsService</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The ApnsService to use. The org.apache.camel.component.apns.factory.ApnsServiceFactory can be used to build a ApnsService</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ApnsService</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The APNS endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>apns:name</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>name</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Name of the endpoint</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_20_parameters">Query Parameters (20 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>tokens</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configure this property in case you want to statically declare tokens related to devices you want to notify. Tokens are separated by comma.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sendEmptyMessageWhenIdle</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If the polling consumer did not poll any files you can enable this option to send an empty message (no body) instead.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>pollStrategy</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">PollingConsumerPoll Strategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>backoffErrorThreshold</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>backoffIdleThreshold</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>backoffMultiplier</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>delay</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Milliseconds before the next poll. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">500</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>greedy</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If greedy is enabled then the ScheduledPollConsumer will run immediately again if the previous run polled 1 or more messages.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>initialDelay</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Milliseconds before the first poll starts. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>runLoggingLevel</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">TRACE</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">LoggingLevel</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>scheduledExecutorService</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ScheduledExecutor Service</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>scheduler</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a cron scheduler from either camel-spring or camel-quartz2 component</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">none</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ScheduledPollConsumer Scheduler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>schedulerProperties</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure additional properties when using a custom scheduler or any of the Quartz2 Spring based scheduler.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>startScheduler</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the scheduler should be auto started.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>timeUnit</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Time unit for initialDelay and delay options.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">MILLISECONDS</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TimeUnit</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useFixedDelay</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>You can append query options to the URI in the following format,
+<code>?option=value&option=value&…​</code></p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_component">Component</h4>
+<div class="paragraph">
+<p>The <code>ApnsComponent</code> must be configured with a
+<code>com.notnoop.apns.ApnsService</code>. The service can be created and
+configured using the
+<code>org.apache.camel.component.apns.factory.ApnsServiceFactory</code>. See
+further below for an example. And as well in the
+<a href="https://github.com/apache/camel/tree/master/components/camel-apns">test
+source code</a>.</p>
+</div>
+<div class="sect4">
+<h5 id="_ssl_setting">SSL Setting</h5>
+<div class="paragraph">
+<p>In order to use secure connection, an instance of <code>org.apache.camel.util.jsse.SSLContextParameters</code>
+ should be injected to <code>org.apache.camel.component.apns.factory.ApnsServiceFactory</code> which is
+ used to configure the component. See the test resources for an example.
+ <a href="https://github.com/apache/camel/blob/master/components/camel-apns/src/test/resources/org/apache/camel/component/apns/spring/SpringApnsConsumerTest-context.xml">ssl example</a></p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_exchange_data_format">Exchange data format</h3>
+<div class="paragraph">
+<p>When Camel will fetch feedback data corresponding to inactive devices,
+it will retrieve a List of InactiveDevice objects. Each InactiveDevice
+object of the retrieved list will be setted as the In body, and then
+processed by the consumer endpoint.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_message_headers">Message Headers</h3>
+<div class="paragraph">
+<p>Camel Apns uses these headers.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 10%;">
+<col style="width: 10%;">
+<col style="width: 80%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Property</th>
+<th class="tableblock halign-left valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>CamelApnsTokens</code></p></td>
+<td class="tableblock halign-left valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Empty by default.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>CamelApnsMessageType</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>STRING, PAYLOAD, APNS_NOTIFICATION</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">In case you choose PAYLOAD for the message type, then the message will
+be considered as a APNS payload and sent as is. In case you choose
+STRING, message will be converted as a APNS payload. From <strong>Camel 2.16</strong>
+onwards APNS_NOTIFICATION is used for sending message body as
+com.notnoop.apns.ApnsNotification types.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_apnsservicefactory_builder_callback">ApnsServiceFactory builder callback</h3>
+<div class="paragraph">
+<p><code>ApnsServiceFactory</code> comes with the empty callback method that could be
+used to configure (or even replace) the default <code>ApnsServiceBuilder</code>
+instance. The signature of the method could look as follows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder serviceBuilder);</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And could be used like as follows:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
+
+ @Override
+ protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder serviceBuilder) {
+ return serviceBuilder.withSocksProxy("my.proxy.com", 6666);
+ }
+
+};</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_samples">Samples</h3>
+<div class="sect3">
+<h4 id="_camel_xml_route">Camel Xml route</h4>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><beans xmlns="http://www.springframework.org/schema/beans"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:camel="http://camel.apache.org/schema/spring"
+ xsi:schemaLocation="
+ http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
+ http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd">
+
+ <!-- Replace by desired values -->
+ <bean id="apnsServiceFactory" class="org.apache.camel.component.apns.factory.ApnsServiceFactory">
+
+ <!-- Optional configuration of feedback host and port -->
+ <!-- <property name="feedbackHost" value="localhost" /> -->
+ <!-- <property name="feedbackPort" value="7843" /> -->
+
+ <!-- Optional configuration of gateway host and port -->
+ <!-- <property name="gatewayHost" value="localhost" /> -->
+ <!-- <property name="gatewayPort" value="7654" /> -->
+
+ <!-- Declaration of certificate used -->
+ <!-- from Camel 2.11 onwards you can use prefix: classpath:, file: to refer to load the certificate from classpath or file. Default it classpath -->
+ <property name="certificatePath" value="certificate.p12" />
+ <property name="certificatePassword" value="MyCertPassword" />
+
+ <!-- Optional connection strategy - By Default: No need to configure -->
+ <!-- Possible options: NON_BLOCKING, QUEUE, POOL or Nothing -->
+ <!-- <property name="connectionStrategy" value="POOL" /> -->
+ <!-- Optional pool size -->
+ <!-- <property name="poolSize" value="15" /> -->
+
+ <!-- Optional connection strategy - By Default: No need to configure -->
+ <!-- Possible options: EVERY_HALF_HOUR, EVERY_NOTIFICATION or Nothing (Corresponds to NEVER javapns option) -->
+ <!-- <property name="reconnectionPolicy" value="EVERY_HALF_HOUR" /> -->
+ </bean>
+
+ <bean id="apnsService" factory-bean="apnsServiceFactory" factory-method="getApnsService" />
+
+ <!-- Replace this declaration by wanted configuration -->
+ <bean id="apns" class="org.apache.camel.component.apns.ApnsComponent">
+ <property name="apnsService" ref="apnsService" />
+ </bean>
+
+ <camelContext id="camel-apns-test" xmlns="http://camel.apache.org/schema/spring">
+ <route id="apns-test">
+ <from uri="apns:consumer?initialDelay=10&amp;delay=3600&amp;timeUnit=SECONDS" />
+ <to uri="log:org.apache.camel.component.apns?showAll=true&amp;multiline=true" />
+ <to uri="mock:result" />
+ </route>
+ </camelContext>
+
+</beans></code></pre>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_camel_java_route">Camel Java route</h4>
+<div id="APNS-Createcamelcontextanddeclareapnscomponentprogrammatically" class="paragraph">
+<p>Create camel context and declare apns component programmatically</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> protected CamelContext createCamelContext() throws Exception {
+ CamelContext camelContext = super.createCamelContext();
+
+ ApnsServiceFactory apnsServiceFactory = new ApnsServiceFactory();
+ apnsServiceFactory.setCertificatePath("classpath:/certificate.p12");
+ apnsServiceFactory.setCertificatePassword("MyCertPassword");
+
+ ApnsService apnsService = apnsServiceFactory.getApnsService(camelContext);
+
+ ApnsComponent apnsComponent = new ApnsComponent(apnsService);
+ camelContext.addComponent("apns", apnsComponent);
+
+ return camelContext;
+ }</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>[[APNS-ApnsProducer-iOStargetdevicedynamicallyconfiguredviaheader:"CamelApnsTokens"]]
+ApnsProducer - iOS target device dynamically configured via header:
+<code>"CamelApnsTokens"</code></p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> protected RouteBuilder createRouteBuilder() throws Exception {
+ return new RouteBuilder() {
+ public void configure() throws Exception {
+ from("direct:test")
+ .setHeader(ApnsConstants.HEADER_TOKENS, constant(IOS_DEVICE_TOKEN))
+ .to("apns:notify");
+ }
+ }
+ }</code></pre>
+</div>
+</div>
+<div id="APNS-ApnsProducer-iOStargetdevicestaticallyconfiguredviauri" class="paragraph">
+<p>ApnsProducer - iOS target device statically configured via uri</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> protected RouteBuilder createRouteBuilder() throws Exception {
+ return new RouteBuilder() {
+ public void configure() throws Exception {
+ from("direct:test").
+ to("apns:notify?tokens=" + IOS_DEVICE_TOKEN);
+ }
+ };
+ }</code></pre>
+</div>
+</div>
+<div id="APNS-ApnsConsumer" class="paragraph">
+<p>ApnsConsumer</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("apns:consumer?initialDelay=10&delay=3600&timeUnit=SECONDS")
+ .to("log:com.apache.camel.component.apns?showAll=true&multiline=true")
+ .to("mock:result");</code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="http://camel.apache.org/component.html">Component</a></p>
+</li>
+<li>
+<p><a href="http://camel.apache.org/endpoint.html">Endpoint</a>
+*
+<a href="http://blog.xebia.fr/2010/09/30/creer-un-composant-apache-camel-de-connexion-a-lapns-1-sur-3/">Blog
+about using APNS (in french)</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/asterisk-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/amqp-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/asterisk-component/index.html b/components/2.20.0/asterisk-component/index.html
new file mode 100644
index 0000000..1297f10
--- /dev/null
+++ b/components/2.20.0/asterisk-component/index.html
@@ -0,0 +1,361 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Asterisk Component Available as of Camel version 2.18
+ The asterisk: component allows you to work easily with an Asterisk PBX Server http://www.asterisk.org/ using asterisk-java
+ This component help to interface with Asterisk Manager Interface
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-asterisk</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format asterisk:name[?'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Asterisk Component Available as of Camel version 2.18
+ The asterisk: component allows you to work easily with an Asterisk PBX Server http://www.asterisk.org/ using asterisk-java
+ This component help to interface with Asterisk Manager Interface
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-asterisk</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format asterisk:name[?'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/asterisk-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/asterisk-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_asterisk_component">Asterisk Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.18</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>asterisk:</strong> component allows you to work easily with an Asterisk PBX Server <a href="http://www.asterisk.org/" class="bare">http://www.asterisk.org/</a> using <a href="https://asterisk-java.org/">asterisk-java</a></p>
+</div>
+<div class="paragraph">
+<p>This component help to interface with <a href="http://www.voip-info.org/wiki-Asterisk+manager+API">Asterisk Manager Interface</a></p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-asterisk</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">asterisk:name[?options]</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_options">Options</h3>
+<div class="paragraph">
+<p>The Asterisk component has no options.</p>
+</div>
+<div class="paragraph">
+<p>The Asterisk endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>asterisk:name</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>name</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Logical name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_8_parameters">Query Parameters (8 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>hostname</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The hostname of the asterisk server</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>password</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Login password</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>username</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Login username</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>action</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">What action to perform such as getting queue status sip peers or extension state.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AsteriskAction</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_action">Action</h3>
+<div class="paragraph">
+<p>Supported actions are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>QUEUE_STATUS, Queue Status</p>
+</li>
+<li>
+<p>SIP_PEERS, List SIP Peers</p>
+</li>
+<li>
+<p>EXTENSION_STATE, Check Extension Status</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atmos-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/apns-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atmos-component/index.html b/components/2.20.0/atmos-component/index.html
new file mode 100644
index 0000000..91832e1
--- /dev/null
+++ b/components/2.20.0/atmos-component/index.html
@@ -0,0 +1,471 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atmos Component Available as of Camel version 2.15
+ Camel-Atmos is an Apache Camel component that allows you to work with ViPR object data services using the Atmos Client.
+ from("atmos:foo/get?remotePath=/path").to("mock:test"); Options The Atmos component has no options.
+ The Atmos endpoint is configured using URI syntax:
+ atmos:name/operation with the following path and query parameters:
+ Path Parameters (2 parameters): Name Description Default Type name'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atmos Component Available as of Camel version 2.15
+ Camel-Atmos is an Apache Camel component that allows you to work with ViPR object data services using the Atmos Client.
+ from("atmos:foo/get?remotePath=/path").to("mock:test"); Options The Atmos component has no options.
+ The Atmos endpoint is configured using URI syntax:
+ atmos:name/operation with the following path and query parameters:
+ Path Parameters (2 parameters): Name Description Default Type name'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atmos-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atmos-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atmos_component">Atmos Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.15</strong></p>
+</div>
+<div class="paragraph">
+<p><strong>Camel-Atmos</strong> is an <a href="http://camel.apache.org/">Apache Camel</a> component that
+allows you to work with ViPR object data services using the
+<a href="https://github.com/emcvipr/dataservices-sdk-java">Atmos Client</a>.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("atmos:foo/get?remotePath=/path").to("mock:test");</code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_options">Options</h3>
+<div class="paragraph">
+<p>The Atmos component has no options.</p>
+</div>
+<div class="paragraph">
+<p>The Atmos endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atmos:name/operation</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_2_parameters">Path Parameters (2 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>name</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atmos name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>operation</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Operation to perform</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtmosOperation</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_12_parameters">Query Parameters (12 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>enableSslValidation</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atmos SSL validation</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>fullTokenId</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atmos client fullTokenId</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>localPath</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local path to put files</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>newRemotePath</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">New path on Atmos when moving files</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>query</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Search query on Atmos</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>remotePath</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Where to put files on Atmos</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>secretKey</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atmos shared secret</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>uri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomos server uri</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_dependencies">Dependencies</h3>
+<div class="paragraph">
+<p>To use Atmos in your camel routes you need to add the dependency
+on <strong>camel-atmos</strong> which implements this data format.</p>
+</div>
+<div class="paragraph">
+<p>If you use maven you could just add the following to your pom.xml,
+substituting the version number for the latest & greatest release (see
+<a href="download.html">the download page for the latest versions</a>).</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atmos</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="Atmos-Integrations">Integrations</h3>
+<div class="paragraph">
+<p>When you look at atmos integrations, there is one type of consumer,
+GetConsumer, which is a type of ScheduledPollConsumer.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>Get</code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Whereas there are 4 types of producers which are</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>Get</code></p>
+</li>
+<li>
+<p><code>Del</code></p>
+</li>
+<li>
+<p><code>Move</code></p>
+</li>
+<li>
+<p><code>Put</code></p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_examples">Examples</h3>
+<div class="paragraph">
+<p>These example are taken from tests:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("atmos:foo/get?remotePath=/path").to("mock:test");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Here, this is a consumer example.
+<code>remotePath</code> represents the path from where the data will
+be read and passes the camel exchange to regarding producer
+Underneath, this component uses atmos client API for this and
+every other operations.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:start")
+.to("atmos://get?remotePath=/dummy/dummy.txt")
+.to("mock:result");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Here, this a producer sample.
+<code>remotePath</code> represents the path where the operations occur
+on ViPR object data service. In producers, operations(<code>Get</code>,<code>Del</code>,
+<code>Move</code>,<code>Put</code>) run on ViPR object data services and results are set
+on headers of camel exchange.</p>
+</div>
+<div class="paragraph">
+<p>Regarding the operations, the following headers are set on camel
+exhange</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">DOWNLOADED_FILE, DOWNLOADED_FILES, UPLOADED_FILE, UPLOADED_FILES, FOUND_FILES, DELETED_PATH, MOVED_PATH;</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="configuring-camel.html">Configuring Camel</a></p>
+</li>
+<li>
+<p><a href="component.html">Component</a></p>
+</li>
+<li>
+<p><a href="endpoint.html">Endpoint</a></p>
+</li>
+<li>
+<p><a href="getting-started.html">Getting Started</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atmosphere-websocket-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/asterisk-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atmosphere-websocket-component/index.html b/components/2.20.0/atmosphere-websocket-component/index.html
new file mode 100644
index 0000000..a566e40
--- /dev/null
+++ b/components/2.20.0/atmosphere-websocket-component/index.html
@@ -0,0 +1,674 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atmosphere Websocket Component Available as of Camel version 2.14
+ The atmosphere-websocket: component provides Websocket based endpoints for a servlet communicating with external clients over Websocket (as a servlet accepting websocket connections from external clients).
+The component uses the SERVLET component and uses the https://github.com/Atmosphere/atmosphere[Atmosphere] library to support the Websocket transport in various Servlet containers (e..g., Jetty, Tomcat, …​).
+ Unlike the Websocket component that starts the embedded Jetty server, this component uses the servlet provider of the container.'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atmosphere Websocket Component Available as of Camel version 2.14
+ The atmosphere-websocket: component provides Websocket based endpoints for a servlet communicating with external clients over Websocket (as a servlet accepting websocket connections from external clients).
+The component uses the SERVLET component and uses the https://github.com/Atmosphere/atmosphere[Atmosphere] library to support the Websocket transport in various Servlet containers (e..g., Jetty, Tomcat, …​).
+ Unlike the Websocket component that starts the embedded Jetty server, this component uses the servlet provider of the container.'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atmosphere-websocket-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atmosphere-websocket-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atmosphere_websocket_component">Atmosphere Websocket Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.14</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>atmosphere-websocket:</strong> component provides Websocket
+based <a href="endpoint.html">endpoints</a> for a servlet communicating with
+external clients over Websocket (as a servlet accepting websocket
+connections from external clients).<br>
+The component uses the <a href="servlet.html">SERVLET</a> component and uses
+the https://github.com/Atmosphere/atmosphere[Atmosphere] library to
+support the Websocket transport in various Servlet containers (e..g.,
+Jetty, Tomcat, …​).</p>
+</div>
+<div class="paragraph">
+<p>Unlike the
+<a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39621544">Websocket</a>
+component that starts the embedded Jetty server, this component uses the
+servlet provider of the container.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to
+their <code>pom.xml</code> for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atmosphere-websocket</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_atmosphere_websocket_options">Atmosphere-Websocket Options</h3>
+<div class="paragraph">
+<p>The Atmosphere Websocket component supports 8 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>servletName</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Default name of servlet to use. The default name is CamelServlet.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpRegistry</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom org.apache.camel.component.servlet.HttpRegistry.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HttpRegistry</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>attachmentMultipart Binding</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet’s.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpBinding</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom HttpBinding to control the mapping between Camel message and HttpClient.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HttpBinding</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpConfiguration</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use the shared HttpConfiguration as base configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HttpConfiguration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>allowJavaSerialized Object</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to allow java serialization when a request uses context-type=application/x-java-serialized-object. This is by default turned off. If you enable this then be aware that Java will deserialize the incoming data from the request to Java and that can be a potential security risk.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (filter)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atmosphere Websocket endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atmosphere-websocket:servicePath</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>servicePath</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Name of websocket endpoint</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_37_parameters">Query Parameters (37 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>chunked</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If this option is false the Servlet will disable the HTTP streaming and set the content-length header on the response</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>disableStreamCache</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Determines whether or not the raw input stream from Servlet is cached or not (Camel will read the stream into a in memory/overflow to file Stream caching) cache. By default Camel will cache the Servlet input stream to support reading it multiple times to ensure it Camel can retrieve all data from the stream. However you can set this option to true when you for example need to access the raw stream such as streaming it di [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>headerFilterStrategy</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom HeaderFilterStrategy to filter header to and from Camel message.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HeaderFilterStrategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sendToAll</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to send to all (broadcast) or send to a single receiver.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transferException</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If enabled and an Exchange failed processing on the consumer side and if the caused Exception was send back serialized in the response as a application/x-java-serialized-object content type. On the producer side the exception will be deserialized and thrown as is instead of the HttpOperationFailedException. The caused exception is required to be serialized. This is by default turned off. If you enable this then be aware [...]
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useStreaming</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To enable streaming to send data as multiple text fragments.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpBinding</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom HttpBinding to control the mapping between Camel message and HttpClient.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HttpBinding</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>async</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configure the consumer to work in async mode</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpMethodRestrict</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Used to only allow consuming if the HttpMethod matches such as GET/POST/PUT etc. Multiple methods can be specified separated by comma.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>matchOnUriPrefix</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether or not the consumer should try to find a target consumer by matching the URI prefix if no exact match is found.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>responseBufferSize</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a custom buffer size on the javax.servlet.ServletResponse.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Integer</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>servletName</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Name of the servlet to use</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">CamelServlet</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>attachmentMultipartBinding</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to automatic bind multipart/form-data as attachments on the Camel Exchange. The options attachmentMultipartBinding=true and disableStreamCache=false cannot work together. Remove disableStreamCache to use AttachmentMultipartBinding. This is turn off by default as this may require servlet specific configuration to enable this when using Servlet’s.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>eagerCheckContentAvailable</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether to eager check whether the HTTP requests has content if the content-length header is 0 or not present. This can be turned on in case HTTP clients do not send streamed data.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>optionsEnabled</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to enable HTTP OPTIONS for this Servlet consumer. By default OPTIONS is turned off.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>traceEnabled</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether to enable HTTP TRACE for this Servlet consumer. By default TRACE is turned off.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeEndpoint</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If the option is true HttpProducer will ignore the Exchange.HTTP_URI header and use the endpoint’s URI for request. You may also set the option throwExceptionOnFailure to be false to let the HttpProducer send all the fault response back.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>connectionClose</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specifies whether a Connection Close header must be added to HTTP Request. By default connectionClose is false.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>copyHeaders</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If this option is true then IN exchange headers will be copied to OUT exchange headers according to copy strategy. Setting this to false allows to only include the headers from the HTTP response (not propagating IN headers).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>httpMethod</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configure the HTTP method to use. The HttpMethod header cannot override this option if set.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">HttpMethods</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ignoreResponseBody</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If this option is true The http producer won’t read response body and cache the input stream</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>preserveHostHeader</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If the option is true HttpProducer will set the Host header to the value contained in the current exchange Host header useful in reverse proxy applications where you want the Host header received by the downstream server to reflect the URL called by the upstream client this allows applications which use the Host header to generate accurate URL’s for a proxied service</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>throwExceptionOnFailure</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Option to disable throwing the HttpOperationFailedException in case of failed responses from the remote server. This allows you to get all responses regardless of the HTTP status code.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>cookieHandler</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Configure a cookie handler to maintain a HTTP session</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CookieHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>okStatusCodeRange</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The status codes which is considered a success response. The values are inclusive. The range must be defined as from-to with the dash included.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">200-299</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>urlRewrite</strong> (producer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Refers to a custom org.apache.camel.component.http.UrlRewrite which allows you to rewrite urls when you bridge/proxy endpoints. See more details at <a href="http://camel.apache.org/urlrewrite.html" class="bare">http://camel.apache.org/urlrewrite.html</a></p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">UrlRewrite</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>mapHttpMessageBody</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If this option is true then IN exchange Body of the exchange will be mapped to HTTP body. Setting this to false will avoid the HTTP mapping.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>mapHttpMessageFormUrl EncodedBody</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If this option is true then IN exchange Form Encoded body of the exchange will be mapped to HTTP. Setting this to false will avoid the HTTP Form Encoded body mapping.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>mapHttpMessageHeaders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If this option is true then IN exchange Headers of the exchange will be mapped to HTTP headers. Setting this to false will avoid the HTTP Headers mapping.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>proxyAuthScheme</strong> (proxy)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Proxy authentication scheme to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>proxyHost</strong> (proxy)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Proxy hostname to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>proxyPort</strong> (proxy)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Proxy port to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>authHost</strong> (security)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Authentication host to use with NTML</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI Format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">atmosphere-websocket:///relative path[?options]</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_reading_and_writing_data_over_websocket">Reading and Writing Data over Websocket</h3>
+<div class="paragraph">
+<p>An atmopshere-websocket endpoint can either write data to the socket or
+read from the socket, depending on whether the endpoint is configured as
+the producer or the consumer, respectively.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configuring_uri_to_read_or_write_data">Configuring URI to Read or Write Data</h3>
+<div class="paragraph">
+<p>In the route below, Camel will read from the specified websocket
+connection.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("atmosphere-websocket:///servicepath")
+ .to("direct:next");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And the equivalent Spring sample:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><camelContext xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="atmosphere-websocket:///servicepath"/>
+ <to uri="direct:next"/>
+ </route>
+</camelContext></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the route below, Camel will read from the specified websocket
+connection.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("direct:next")
+ .to("atmosphere-websocket:///servicepath");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>And the equivalent Spring sample:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><camelContext xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="direct:next"/>
+ <to uri="atmosphere-websocket:///servicepath"/>
+ </route>
+</camelContext></code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="configuring-camel.html">Configuring Camel</a></p>
+</li>
+<li>
+<p><a href="component.html">Component</a></p>
+</li>
+<li>
+<p><a href="endpoint.html">Endpoint</a></p>
+</li>
+<li>
+<p><a href="getting-started.html">Getting Started</a></p>
+</li>
+<li>
+<p><a href="servlet.html">SERVLET</a></p>
+</li>
+<li>
+<p><a href="ahc-ws.html">AHC-WS</a>
+*
+<a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=39621544">Websocket</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atom-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atmos-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atom-component/index.html b/components/2.20.0/atom-component/index.html
new file mode 100644
index 0000000..ce9b1af
--- /dev/null
+++ b/components/2.20.0/atom-component/index.html
@@ -0,0 +1,570 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atom Component Available as of Camel version 1.2
+ The atom: component is used for polling Atom feeds.
+ Camel will poll the feed every 60 seconds by default.
+Note: The component currently only supports polling (consuming) feeds.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atom</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format atom://atomUri[?'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atom Component Available as of Camel version 1.2
+ The atom: component is used for polling Atom feeds.
+ Camel will poll the feed every 60 seconds by default.
+Note: The component currently only supports polling (consuming) feeds.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atom</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI format atom://atomUri[?'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atom-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atom-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atom_component">Atom Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 1.2</strong></p>
+</div>
+<div class="paragraph">
+<p>The <strong>atom:</strong> component is used for polling Atom feeds.</p>
+</div>
+<div class="paragraph">
+<p>Camel will poll the feed every 60 seconds by default.<br>
+ <strong>Note:</strong> The component currently only supports polling (consuming)
+feeds.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atom</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">atom://atomUri[?options]</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Where <strong>atomUri</strong> is the URI to the Atom feed to poll.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_options">Options</h3>
+<div class="paragraph">
+<p>The Atom component has no options.</p>
+</div>
+<div class="paragraph">
+<p>The Atom endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atom:feedUri</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>feedUri</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The URI to the feed to poll.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_27_parameters">Query Parameters (27 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>feedHeader</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether to add the feed object as a header</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>filter</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether to use filtering or not of the entries.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>lastUpdate</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the timestamp to be used for filtering entries from the atom feeds. This options is only in conjunction with the splitEntries.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Date</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>password</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the password to be used for basic authentication when polling from a HTTP feed</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sendEmptyMessageWhenIdle</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If the polling consumer did not poll any files you can enable this option to send an empty message (no body) instead.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>sortEntries</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether to sort entries by published date. Only works when splitEntries = true.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>splitEntries</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether or not entries should be sent individually or whether the entire feed should be sent as a single message</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>throttleEntries</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether all entries identified in a single feed poll should be delivered immediately. If true only one entry is processed per consumer.delay. Only applicable when splitEntries = true.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>username</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the username to be used for basic authentication when polling from a HTTP feed</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>pollStrategy</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">PollingConsumerPoll Strategy</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>backoffErrorThreshold</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>backoffIdleThreshold</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>backoffMultiplier</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>delay</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Milliseconds before the next poll. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">500</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>greedy</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If greedy is enabled then the ScheduledPollConsumer will run immediately again if the previous run polled 1 or more messages.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>initialDelay</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Milliseconds before the first poll starts. You can also specify time values using units such as 60s (60 seconds) 5m30s (5 minutes and 30 seconds) and 1h (1 hour).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">1000</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>runLoggingLevel</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">TRACE</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">LoggingLevel</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>scheduledExecutorService</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ScheduledExecutor Service</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>scheduler</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a cron scheduler from either camel-spring or camel-quartz2 component</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">none</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ScheduledPollConsumer Scheduler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>schedulerProperties</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To configure additional properties when using a custom scheduler or any of the Quartz2 Spring based scheduler.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>startScheduler</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the scheduler should be auto started.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>timeUnit</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Time unit for initialDelay and delay options.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">MILLISECONDS</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TimeUnit</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>useFixedDelay</strong> (scheduler)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>You can append query options to the URI in the following format,
+<code>?option=value&option=value&…​</code></p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_exchange_data_format">Exchange data format</h3>
+<div class="paragraph">
+<p>Camel will set the In body on the returned <code>Exchange</code> with the entries.
+Depending on the <code>splitEntries</code> flag Camel will either return one
+<code>Entry</code> or a <code>List<Entry></code>.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 10%;">
+<col style="width: 10%;">
+<col style="width: 80%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Option</th>
+<th class="tableblock halign-left valign-top">Value</th>
+<th class="tableblock halign-left valign-top">Behavior</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>splitEntries</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>true</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Only a single entry from the currently being processed feed is set:
+<code>exchange.in.body(Entry)</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>splitEntries</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>false</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The entire list of entries from the feed is set:
+<code>exchange.in.body(List<Entry>)</code></p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>Camel can set the <code>Feed</code> object on the In header (see <code>feedHeader</code>
+option to disable this):</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_message_headers">Message Headers</h3>
+<div class="paragraph">
+<p>Camel atom uses these headers.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 10%;">
+<col style="width: 90%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Header</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>CamelAtomFeed</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">When consuming the <code>org.apache.abdera.model.Feed</code> object is set to this
+header.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_samples">Samples</h3>
+<div class="paragraph">
+<p>In this sample we poll James Strachan’s blog.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">from("atom://http://macstrac.blogspot.com/feeds/posts/default").to("seda:feeds");</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In this sample we want to filter only good blogs we like to a SEDA
+queue. The sample also shows how to setup Camel standalone, not running
+in any Container or using Spring.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_see_also">See Also</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="configuring-camel.html">Configuring Camel</a></p>
+</li>
+<li>
+<p><a href="component.html">Component</a></p>
+</li>
+<li>
+<p><a href="endpoint.html">Endpoint</a></p>
+</li>
+<li>
+<p><a href="getting-started.html">Getting Started</a></p>
+</li>
+<li>
+<p><a href="rss.html">RSS</a></p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-map-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atmosphere-websocket-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atomix-map-component/index.html b/components/2.20.0/atomix-map-component/index.html
new file mode 100644
index 0000000..8670120
--- /dev/null
+++ b/components/2.20.0/atomix-map-component/index.html
@@ -0,0 +1,627 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atomix Map Component Available as of Camel version 2.20
+ The camel atomix-map component allows you to work with Atomix’s Distributed Map collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-map:mapName Options The Atomix Map component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atomix Map Component Available as of Camel version 2.20
+ The camel atomix-map component allows you to work with Atomix’s Distributed Map collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-map:mapName Options The Atomix Map component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atomix-map-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atomix-map-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atomix_map_component">Atomix Map Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.20</strong></p>
+</div>
+<div class="paragraph">
+<p>The camel atomix-map component allows you to work with <a href="http://atomix.io/atomix/">Atomix’s</a> <a href="http://atomix.io/atomix/docs/collections/#distributedmap">Distributed Map</a> collection.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their pom.xml for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atomix</artifactId>
+ <version>${camel-version}</version>
+ </dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> atomix-map:mapName</code></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_options">Options</h3>
+<div class="paragraph">
+<p>The Atomix Map component supports 5 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared component configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixMapConfiguration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared AtomixClient instance</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The nodes the AtomixClient should connect to</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">List</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The path to the AtomixClient configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atomix Map endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atomix-map:mapName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The distributed resource name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_18_parameters">Query Parameters (18 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix instance to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomix</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix configuration uri.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultAction</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The default action.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">PUT</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Action</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>key</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The key to use if none is set in the header or to listen for events for a specific key.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Object</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The address of the nodes composing the cluster.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resultHeader</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The header that wil carry the result.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the Atomix transport.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">io.atomix.catalyst.transport.netty.NettyTransport</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Transport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ttl</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The resource ttl.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The cluster wide default resource configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The local default resource options.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ephemeral</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>readConsistency</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceConfigs</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Cluster wide resources configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local resources configurations</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_headers">Headers</h3>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 10%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+<col style="width: 60%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Type</th>
+<th class="tableblock halign-left valign-top">Values</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CamelAtomixResourceAction</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixMap.Action</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>PUT</p>
+</li>
+<li>
+<p>PUT_IF_ABSENT</p>
+</li>
+<li>
+<p>GET</p>
+</li>
+<li>
+<p>CLEAR</p>
+</li>
+<li>
+<p>SIZE</p>
+</li>
+<li>
+<p>CONTAINS_KEY</p>
+</li>
+<li>
+<p>CONTAINS_VALUE</p>
+</li>
+<li>
+<p>IS_EMPTY</p>
+</li>
+<li>
+<p>ENTRY_SET</p>
+</li>
+<li>
+<p>REMOVE</p>
+</li>
+<li>
+<p>REPLACE</p>
+</li>
+<li>
+<p>VALUES</p>
+</li>
+</ul>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The action to perform</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CamelAtomixResourceKey</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Object</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="paragraph">
+<p>-</p>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The key to operate on</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CamelAtomixResourceValue</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Object</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="paragraph">
+<p>-</p>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The value, if missing In Body is used</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CamelAtomixResourceOldValue</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Object</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="paragraph">
+<p>-</p>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The old value</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CamelAtomixResourceTTL</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String / long</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="paragraph">
+<p>-</p>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The entry TTL</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">CamelAtomixResourceReadConsistency</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+<td class="tableblock halign-left valign-top"><div><div class="ulist">
+<ul>
+<li>
+<p>ATOMIC</p>
+</li>
+<li>
+<p>ATOMIC_LEASE</p>
+</li>
+<li>
+<p>SEQUENTIAL</p>
+</li>
+<li>
+<p>LOCAL</p>
+</li>
+</ul>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_configuring_the_component_to_connect_to_an_atomix_cluster">Configuring the component to connect to an Atomix cluster</h3>
+<div class="paragraph">
+<p>The nodes of the Atomix cluster you want to join can be se at Endpoint or component level (recommended), below some examples:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><strong>Endpoint:</strong></p>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><beans xmlns="...">
+ <camelContext xmlns="http://camel.apache.org/schema/spring">
+ <from uri="direct:start"/>
+ <to uri="atomix-map:myMap?nodes=node-1.atomix.cluster:8700,node-2.atomix.cluster:8700"/>
+ </route>
+ </camelContext>
+</beans></code></pre>
+</div>
+</div>
+</li>
+<li>
+<p><strong>Component:</strong></p>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><beans xmlns="...">
+ <bean id="atomix-map" class="org.apache.camel.component.atomix.client.map.AtomixMapComponent">
+ <property name="nodes" value="nodes=node-1.atomix.cluster:8700,node-2.atomix.cluster:8700"/>
+ </bean>
+
+ <camelContext xmlns="http://camel.apache.org/schema/spring">
+ <from uri="direct:start"/>
+ <to uri="atomix-map:myMap"/>
+ </route>
+ </camelContext>
+</beans></code></pre>
+</div>
+</div>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_usage_examples">Usage examples:</h3>
+<div class="ulist">
+<ul>
+<li>
+<p><strong>PUT an element with TTL of 1 second:</strong></p>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">FluentProducerTemplate.on(context)
+ .withHeader(AtomixClientConstants.RESOURCE_ACTION, AtomixMap.Action.PUT)
+ .withHeader(AtomixClientConstants.RESOURCE_KEY, key)
+ .withHeader(AtomixClientConstants.RESOURCE_TTL, "1s")
+ .withBody(val)
+ .to("direct:start")
+ .send();</code></pre>
+</div>
+</div>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-messaging-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atom-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atomix-messaging-component/index.html b/components/2.20.0/atomix-messaging-component/index.html
new file mode 100644
index 0000000..094c72d
--- /dev/null
+++ b/components/2.20.0/atomix-messaging-component/index.html
@@ -0,0 +1,449 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atomix Messaging Component Available as of Camel version 2.20
+ The camel atomix-messaging component allows you to work with Atomix’s Group Messaging.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-messaging:group The Atomix Messaging component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atomix Messaging Component Available as of Camel version 2.20
+ The camel atomix-messaging component allows you to work with Atomix’s Group Messaging.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-messaging:group The Atomix Messaging component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atomix-messaging-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atomix-messaging-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atomix_messaging_component">Atomix Messaging Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.20</strong></p>
+</div>
+<div class="paragraph">
+<p>The camel atomix-messaging component allows you to work with <a href="http://atomix.io/atomix/">Atomix’s</a> <a href="http://atomix.io/atomix/docs/groups/#messaging">Group Messaging</a>.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their pom.xml
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atomix</artifactId>
+ <version>${camel-version}</version>
+ </dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> atomix-messaging:group</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The Atomix Messaging component supports 5 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared component configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixMessaging Configuration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared AtomixClient instance</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The nodes the AtomixClient should connect to</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">List</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The path to the AtomixClient configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atomix Messaging endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atomix-messaging:group</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The distributed resource name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_19_parameters">Query Parameters (19 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix instance to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomix</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>broadcastType</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The broadcast type.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">ALL</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">BroadcastType</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>channelName</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The messaging channel name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix configuration uri.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultAction</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The default action.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">DIRECT</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Action</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>memberName</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix Group member name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The address of the nodes composing the cluster.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resultHeader</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The header that wil carry the result.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the Atomix transport.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">io.atomix.catalyst.transport.netty.NettyTransport</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Transport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The cluster wide default resource configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The local default resource options.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ephemeral</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>readConsistency</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceConfigs</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Cluster wide resources configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local resources configurations</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-multimap-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-map-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atomix-multimap-component/index.html b/components/2.20.0/atomix-multimap-component/index.html
new file mode 100644
index 0000000..209d78a
--- /dev/null
+++ b/components/2.20.0/atomix-multimap-component/index.html
@@ -0,0 +1,443 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atomix MultiMap Component Available as of Camel version 2.20
+ The camel atomix-multimap component allows you to work with Atomix’s Distributed MultiMap collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-multimap:multiMapName The Atomix MultiMap component supports 5 options which are listed below.
+ Name Description Default Type configuration (consumer)'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atomix MultiMap Component Available as of Camel version 2.20
+ The camel atomix-multimap component allows you to work with Atomix’s Distributed MultiMap collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-multimap:multiMapName The Atomix MultiMap component supports 5 options which are listed below.
+ Name Description Default Type configuration (consumer)'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atomix-multimap-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atomix-multimap-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atomix_multimap_component">Atomix MultiMap Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.20</strong></p>
+</div>
+<div class="paragraph">
+<p>The camel atomix-multimap component allows you to work with <a href="http://atomix.io/atomix/">Atomix’s</a> <a href="http://atomix.io/atomix/docs/collections/#distributedmultimap">Distributed MultiMap</a> collection.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their pom.xml
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atomix</artifactId>
+ <version>${camel-version}</version>
+ </dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> atomix-multimap:multiMapName</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The Atomix MultiMap component supports 5 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared component configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixMultiMap Configuration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared AtomixClient instance</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The nodes the AtomixClient should connect to</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">List</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The path to the AtomixClient configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atomix MultiMap endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atomix-multimap:multiMapName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The distributed resource name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_18_parameters">Query Parameters (18 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix instance to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomix</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix configuration uri.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultAction</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The default action.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">PUT</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Action</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>key</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The key to use if none is set in the header or to listen for events for a specific key.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Object</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The address of the nodes composing the cluster.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resultHeader</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The header that wil carry the result.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the Atomix transport.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">io.atomix.catalyst.transport.netty.NettyTransport</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Transport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ttl</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The resource ttl.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The cluster wide default resource configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The local default resource options.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ephemeral</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>readConsistency</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceConfigs</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Cluster wide resources configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local resources configurations</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-queue-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-messaging-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atomix-queue-component/index.html b/components/2.20.0/atomix-queue-component/index.html
new file mode 100644
index 0000000..1687076
--- /dev/null
+++ b/components/2.20.0/atomix-queue-component/index.html
@@ -0,0 +1,431 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atomix Queue Component Available as of Camel version 2.20
+ The camel atomix-queue component allows you to work with Atomix’s Distributed Queue collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-queue:queueName The Atomix Queue component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atomix Queue Component Available as of Camel version 2.20
+ The camel atomix-queue component allows you to work with Atomix’s Distributed Queue collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-queue:queueName The Atomix Queue component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atomix-queue-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atomix-queue-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atomix_queue_component">Atomix Queue Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.20</strong></p>
+</div>
+<div class="paragraph">
+<p>The camel atomix-queue component allows you to work with <a href="http://atomix.io/atomix/">Atomix’s</a> <a href="http://atomix.io/atomix/docs/collections/#distributedqueue">Distributed Queue</a> collection.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their pom.xml
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atomix</artifactId>
+ <version>${camel-version}</version>
+ </dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> atomix-queue:queueName</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The Atomix Queue component supports 5 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared component configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixQueue Configuration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared AtomixClient instance</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The nodes the AtomixClient should connect to</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">List</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The path to the AtomixClient configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atomix Queue endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atomix-queue:queueName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The distributed resource name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_16_parameters">Query Parameters (16 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix instance to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomix</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix configuration uri.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultAction</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The default action.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">ADD</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Action</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The address of the nodes composing the cluster.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resultHeader</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The header that wil carry the result.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the Atomix transport.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">io.atomix.catalyst.transport.netty.NettyTransport</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Transport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The cluster wide default resource configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The local default resource options.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ephemeral</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>readConsistency</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceConfigs</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Cluster wide resources configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local resources configurations</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-set-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-multimap-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atomix-set-component/index.html b/components/2.20.0/atomix-set-component/index.html
new file mode 100644
index 0000000..13b9827
--- /dev/null
+++ b/components/2.20.0/atomix-set-component/index.html
@@ -0,0 +1,437 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atomix Set Component Available as of Camel version 2.20
+ The camel atomix-set component allows you to work with Atomix’s Distributed Set collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-set:setName The Atomix Set component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atomix Set Component Available as of Camel version 2.20
+ The camel atomix-set component allows you to work with Atomix’s Distributed Set collection.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-set:setName The Atomix Set component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atomix-set-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atomix-set-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atomix_set_component">Atomix Set Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.20</strong></p>
+</div>
+<div class="paragraph">
+<p>The camel atomix-set component allows you to work with <a href="http://atomix.io/atomix/">Atomix’s</a> <a href="http://atomix.io/atomix/docs/collections/#distributedset">Distributed Set</a> collection.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their pom.xml
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atomix</artifactId>
+ <version>${camel-version}</version>
+ </dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> atomix-set:setName</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The Atomix Set component supports 5 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared component configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixSetConfiguration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared AtomixClient instance</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The nodes the AtomixClient should connect to</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">List</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The path to the AtomixClient configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atomix Set endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atomix-set:setName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The distributed resource name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_17_parameters">Query Parameters (17 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix instance to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomix</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix configuration uri.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultAction</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The default action.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">ADD</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Action</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The address of the nodes composing the cluster.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resultHeader</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The header that wil carry the result.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the Atomix transport.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">io.atomix.catalyst.transport.netty.NettyTransport</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Transport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ttl</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The resource ttl.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The cluster wide default resource configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The local default resource options.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ephemeral</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>readConsistency</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceConfigs</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Cluster wide resources configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local resources configurations</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-value-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-queue-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/atomix-value-component/index.html b/components/2.20.0/atomix-value-component/index.html
new file mode 100644
index 0000000..8b84e98
--- /dev/null
+++ b/components/2.20.0/atomix-value-component/index.html
@@ -0,0 +1,437 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Atomix Value Component Available as of Camel version 2.20
+ The camel atomix-value component allows you to work with Atomix’s Distributed Value.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-value:valueName The Atomix Value component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Atomix Value Component Available as of Camel version 2.20
+ The camel atomix-value component allows you to work with Atomix’s Distributed Value.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-atomix</artifactId> <version>${camel-version}</version> </dependency> URI format atomix-value:valueName The Atomix Value component supports 5 options which are listed below.
+ Name Description Default Type configuration (common)'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/atomix-value-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/atomix-value-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_atomix_value_component">Atomix Value Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.20</strong></p>
+</div>
+<div class="paragraph">
+<p>The camel atomix-value component allows you to work with <a href="http://atomix.io/atomix/">Atomix’s</a> <a href="http://atomix.io/atomix/docs/variables/#distributedvalue">Distributed Value</a>.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their pom.xml
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-atomix</artifactId>
+ <version>${camel-version}</version>
+ </dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_uri_format">URI format</h3>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java"> atomix-value:valueName</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The Atomix Value component supports 5 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared component configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixValue Configuration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The shared AtomixClient instance</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AtomixClient</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The nodes the AtomixClient should connect to</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">List</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The path to the AtomixClient configuration</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Atomix Value endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>atomix-value:valueName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_1_parameters">Path Parameters (1 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> The distributed resource name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_17_parameters">Query Parameters (17 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>atomix</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix instance to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Atomix</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configurationUri</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The Atomix configuration uri.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultAction</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The default action.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">SET</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Action</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>nodes</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The address of the nodes composing the cluster.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resultHeader</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The header that wil carry the result.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the Atomix transport.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">io.atomix.catalyst.transport.netty.NettyTransport</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Transport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ttl</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The resource ttl.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">long</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceConfig</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The cluster wide default resource configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>defaultResourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The local default resource options.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Properties</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>ephemeral</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets if the local member should join groups as PersistentMember or not. If set to ephemeral the local member will receive an auto generated ID thus the local one is ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>readConsistency</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The read consistency level.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ReadConsistency</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceConfigs</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Cluster wide resources configuration.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resourceOptions</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Local resources configurations</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Map</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/avro-component/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-set-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/avro-component/index.html b/components/2.20.0/avro-component/index.html
new file mode 100644
index 0000000..5df7899
--- /dev/null
+++ b/components/2.20.0/avro-component/index.html
@@ -0,0 +1,645 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Avro Component Available as of Camel version 2.10
+ This component provides a dataformat for avro, which allows serialization and deserialization of messages using Apache Avro’s binary dataformat. Moreover, it provides support for Apache Avro’s rpc, by providing producers and consumers endpoint for using avro over netty or http.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-avro</artifactId> <version>x.x.x</version> <!'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Avro Component Available as of Camel version 2.10
+ This component provides a dataformat for avro, which allows serialization and deserialization of messages using Apache Avro’s binary dataformat. Moreover, it provides support for Apache Avro’s rpc, by providing producers and consumers endpoint for using avro over netty or http.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-avro</artifactId> <version>x.x.x</version> <!'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/avro-component/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/avro-component/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_avro_component">Avro Component</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.10</strong></p>
+</div>
+<div class="paragraph">
+<p>This component provides a dataformat for avro, which allows
+serialization and deserialization of messages using Apache Avro’s binary
+dataformat. Moreover, it provides support for Apache Avro’s rpc, by
+providing producers and consumers endpoint for using avro over netty or
+http.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-avro</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_apache_avro_overview">Apache Avro Overview</h3>
+<div class="paragraph">
+<p>Avro allows you to define message types and a protocol using a json like
+format and then generate java code for the specified types and messages.
+An example of how a schema looks like is below.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml">{"namespace": "org.apache.camel.avro.generated",
+ "protocol": "KeyValueProtocol",
+
+ "types": [
+ {"name": "Key", "type": "record",
+ "fields": [
+ {"name": "key", "type": "string"}
+ ]
+ },
+ {"name": "Value", "type": "record",
+ "fields": [
+ {"name": "value", "type": "string"}
+ ]
+ }
+ ],
+
+ "messages": {
+ "put": {
+ "request": [{"name": "key", "type": "Key"}, {"name": "value", "type": "Value"} ],
+ "response": "null"
+ },
+ "get": {
+ "request": [{"name": "key", "type": "Key"}],
+ "response": "Value"
+ }
+ }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>You can easily generate classes from a schema, using maven, ant etc.
+More details can be found at the
+<a href="http://avro.apache.org/docs/current/">Apache Avro documentation</a>.</p>
+</div>
+<div class="paragraph">
+<p>However, it doesn’t enforce a schema first approach and you can create
+schema for your existing classes. <strong>Since 2.12</strong> you can use existing
+protocol interfaces to make RCP calls. You should use interface for the
+protocol itself and POJO beans or primitive/String classes for parameter
+and result types. Here is an example of the class that corresponds to
+schema above:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">package org.apache.camel.avro.reflection;
+
+public interface KeyValueProtocol {
+ void put(String key, Value value);
+ Value get(String key);
+}
+
+class Value {
+ private String value;
+ public String getValue() { return value; }
+ public void setValue(String value) { this.value = value; }
+}</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p><em>Note: Existing classes can be used only for RPC (see below), not in
+data format.</em></p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_the_avro_data_format">Using the Avro data format</h3>
+<div class="paragraph">
+<p>Using the avro data format is as easy as specifying that the class that
+you want to marshal or unmarshal in your route.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"> <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="direct:in"/>
+ <marshal>
+ <avro instanceClass="org.apache.camel.dataformat.avro.Message"/>
+ </marshal>
+ <to uri="log:out"/>
+ </route>
+ </camelContext></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>An alternative can be to specify the dataformat inside the context and
+reference it from your route.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"> <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
+ <dataFormats>
+ <avro id="avro" instanceClass="org.apache.camel.dataformat.avro.Message"/>
+ </dataFormats>
+ <route>
+ <from uri="direct:in"/>
+ <marshal ref="avro"/>
+ <to uri="log:out"/>
+ </route>
+ </camelContext></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the same manner you can umarshal using the avro data format.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_avro_rpc_in_camel">Using Avro RPC in Camel</h3>
+<div class="paragraph">
+<p>As mentioned above Avro also provides RPC support over multiple
+transports such as http and netty. Camel provides consumers and
+producers for these two transports.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">avro:[transport]:[host]:[port][?options]</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The supported transport values are currently http or netty.</p>
+</div>
+<div class="paragraph">
+<p><strong>Since 2.12</strong> you can specify message name right in the URI:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-java" data-lang="java">avro:[transport]:[host]:[port][/messageName][?options]</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>For consumers this allows you to have multiple routes attached to the
+same socket. Dispatching to correct route will be done by the avro
+component automatically. Route with no messageName specified (if any)
+will be used as default.</p>
+</div>
+<div class="paragraph">
+<p>When using camel producers for avro ipc, the "in" message body needs to
+contain the parameters of the operation specified in the avro protocol.
+The response will be added in the body of the "out" message.</p>
+</div>
+<div class="paragraph">
+<p>In a similar manner when using camel avro consumers for avro ipc, the
+requests parameters will be placed inside the "in" message body of the
+created exchange and once the exchange is processed the body of the
+"out" message will be send as a response.</p>
+</div>
+<div class="paragraph">
+<p><strong>Note:</strong> By default consumer parameters are wrapped into array. If you’ve
+got only one parameter, <strong>since 2.12</strong> you can use <code>singleParameter</code> URI
+option to receive it direcly in the "in" message body without array
+wrapping.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_avro_rpc_uri_options">Avro RPC URI Options</h3>
+<div class="paragraph">
+<p>The Avro component supports 2 options which are listed below.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>configuration</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">To use a shared AvroConfiguration to configure options once</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AvroConfiguration</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>resolveProperty Placeholders</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The Avro endpoint is configured using URI syntax:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>avro:transport:host:port/messageName</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>with the following path and query parameters:</p>
+</div>
+<div class="sect3">
+<h4 id="_path_parameters_4_parameters">Path Parameters (4 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>transport</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Transport to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">AvroTransport</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>port</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Port number to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">int</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>host</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Required</strong> Hostname to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>messageName</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The name of the message to send.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect3">
+<h4 id="_query_parameters_10_parameters">Query Parameters (10 parameters):</h4>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 50%;">
+<col style="width: 10%;">
+<col style="width: 20%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+<th class="tableblock halign-center valign-top">Default</th>
+<th class="tableblock halign-left valign-top">Type</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>protocol</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Avro protocol to use</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Protocol</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>protocolClassName</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Avro protocol to use defined by the FQN class name</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>protocolLocation</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Avro protocol location</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>reflectionProtocol</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>singleParameter</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">If true consumer parameter won’t be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>uriAuthority</strong> (common)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Authority to use (username and password)</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">String</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>bridgeErrorHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exceptionHandler</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">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 or ERROR level and ignored.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExceptionHandler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>exchangePattern</strong> (consumer)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets the exchange pattern when the consumer creates an exchange.</p></td>
+<td class="tableblock halign-center valign-top"></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ExchangePattern</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>synchronous</strong> (advanced)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).</p></td>
+<td class="tableblock halign-center valign-top"><p class="tableblock">false</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">boolean</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_avro_rpc_headers">Avro RPC Headers</h3>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 80%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><code>CamelAvroMessageName</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The name of the message to send. In consumer overrides message name from
+URI (if any)</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_examples">Examples</h3>
+<div class="paragraph">
+<p>An example of using camel avro producers via http:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"> <route>
+ <from uri="direct:start"/>
+ <to uri="avro:http:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+ <to uri="log:avro"/>
+ </route></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the example above you need to fill <code>CamelAvroMessageName</code> header.
+<strong>Since 2.12</strong> you can use following syntax to call constant messages:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"> <route>
+ <from uri="direct:start"/>
+ <to uri="avro:http:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+ <to uri="log:avro"/>
+ </route></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>An example of consuming messages using camel avro consumers via netty:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"> <route>
+ <from uri="avro:netty:localhost:{{avroport}}?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol"/>
+ <choice>
+ <when>
+ <el>${in.headers.CamelAvroMessageName == 'put'}</el>
+ <process ref="putProcessor"/>
+ </when>
+ <when>
+ <el>${in.headers.CamelAvroMessageName == 'get'}</el>
+ <process ref="getProcessor"/>
+ </when>
+ </choice>
+ </route></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p><strong>Since 2.12</strong> you can set up two distinct routes to perform the same
+task:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"> <route>
+ <from uri="avro:netty:localhost:{{avroport}}/put?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol">
+ <process ref="putProcessor"/>
+ </route>
+ <route>
+ <from uri="avro:netty:localhost:{{avroport}}/get?protocolClassName=org.apache.camel.avro.generated.KeyValueProtocol&singleParameter=true"/>
+ <process ref="getProcessor"/>
+ </route></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>In the example above, get takes only one parameter, so <code>singleParameter</code>
+is used and <code>getProcessor</code> will receive Value class directly in body,
+while <code>putProcessor</code> will receive an array of size 2 with String key and
+Value value filled as array contents.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+
+
+<footer class='entry-footer'>
+
+
+
+</footer>
+
+
+ </article>
+
+
+
+<nav class='entry-nav'>
+ <div class='entry-nav-links'><div class='prev-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/avro-dataformat/'>
+ <span aria-hidden='true'><svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="20" y1="12" x2="4" y2="12"/>
+ <polyline points="10 18 4 12 10 6"/>
+
+</svg>
+ Previous</span>
+ <span class='screen-reader'>Previous post: </span></a>
+ </div><div class='next-entry'>
+ <a href='https://camel.apache.org/components/2.20.0/atomix-value-component/'>
+ <span class='screen-reader'>Next post: </span><span aria-hidden='true'>Next <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <line x1="4" y1="12" x2="20" y2="12"/>
+ <polyline points="14 6 20 12 14 18"/>
+
+</svg>
+</span>
+ </a>
+ </div></div>
+</nav>
+
+
+
+
+
+ <div class='comments-container'>
+
+</div>
+
+
+</main>
+
+ <footer id='footer' class='footer-container'>
+ <div class='footer'>
+ <div class='social'>
+ <nav aria-label='Social Menu'>
+ <ul class='social-menu'>
+
+ </ul>
+</nav>
+
+ </div>
+
+ <div class='copyright'>
+ <p>
+
+
+
+
+ © 2004-2018 The Apache Software Foundation.
+</p>
+<p>
+ Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p>
+
+ </div>
+ </div>
+ </footer>
+
+ </div>
+
+ <script src='/js/site.36395d52b78f93dc7cc7.js'></script>
+
+
+</body>
+
+</html>
+
diff --git a/components/2.20.0/avro-dataformat/index.html b/components/2.20.0/avro-dataformat/index.html
new file mode 100644
index 0000000..6a715bd
--- /dev/null
+++ b/components/2.20.0/avro-dataformat/index.html
@@ -0,0 +1,369 @@
+<!DOCTYPE html>
+<html lang='en'>
+
+<head>
+ <meta charset='utf-8'>
+<meta name='viewport' content='width=device-width, initial-scale=1'>
+<meta name='description' content='Avro DataFormat Available as of Camel version 2.14
+ This component provides a dataformat for avro, which allows serialization and deserialization of messages using Apache Avro’s binary dataformat. Moreover, it provides support for Apache Avro’s rpc, by providing producers and consumers endpoint for using avro over netty or http.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-avro</artifactId> <version>x.x.x</version> <!'>
+
+<meta property='og:title' content=' • Apache Camel: Integration that you want'>
+<meta property='og:description' content='Avro DataFormat Available as of Camel version 2.14
+ This component provides a dataformat for avro, which allows serialization and deserialization of messages using Apache Avro’s binary dataformat. Moreover, it provides support for Apache Avro’s rpc, by providing producers and consumers endpoint for using avro over netty or http.
+ Maven users will need to add the following dependency to their pom.xml for this component:
+ <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-avro</artifactId> <version>x.x.x</version> <!'>
+<meta property='og:url' content='https://camel.apache.org/components/2.20.0/avro-dataformat/'>
+<meta property='og:site_name' content='Apache Camel: Integration that you want'>
+<meta property='og:type' content='article'><meta property='article:section' content='Components'>
+
+ <base href='https://camel.apache.org/'>
+ <title> • Apache Camel: Integration that you want</title>
+ <link rel='canonical' href='https://camel.apache.org/components/2.20.0/avro-dataformat/'>
+ <link href='' rel='alternate' type='application/rss+xml' title='Apache Camel: Integration that you want' />
+ <link rel='icon' href='/favicon.ico'>
+<link href='//fonts.googleapis.com/css?family=Raleway:400,300,600' rel='stylesheet' type='text/css'>
+<link rel='stylesheet' href='/css/site.142da777720723dd4ecadc8e70926967.css'>
+
+
+
+</head>
+
+
+<body class='page'>
+ <div class='u-full-width u-max-full-width container'>
+ <header class='header'>
+ <div class='site-header'>
+
+ <p class='title'>Apache Camel: Integration that you want</p>
+
+ <p>Apache Camel framework for easy integration</p>
+ </div>
+ </header>
+
+ <nav class='navbar' aria-label='Main Menu'>
+ <div class='container'>
+ <ul class='navbar-list'>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/'>Home</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/about/'>About</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/blog/'>News</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/getting-started/'>Getting started</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/manual/'>Manual</a>
+ </li>
+
+ <li class='navbar-item'>
+ <a class='navbar-link' href='/components/'>Components</a>
+ </li>
+
+ </ul>
+ </div>
+</nav>
+
+
+
+<main class='row content'>
+ <article lang='en' class='entry'>
+ <header class='entry-header'>
+ <div class='entry-info'>
+ <h1 class='entry-title title'></h1>
+
+ </div>
+
+<div class='meta'>
+ <span class='posted-on'>
+ <svg class='icon' viewbox='0 0 24 24' stroke-linecap='round' stroke-linejoin='round' stroke-width='2' aria-hidden='true'>
+
+ <rect x="3" y="4" width="18" height="18" rx="2" ry="2"/>
+ <line x1="16" y1="2" x2="16" y2="6"/>
+ <line x1="8" y1="2" x2="8" y2="6"/>
+ <line x1="3" y1="10" x2="21" y2="10"/>
+
+</svg>
+
+ <span class='screen-reader'>Posted on </span>
+ <time class='date' datetime='0001-01-01T00:00:00Z'>0001, Jan 01</time>
+ </span>
+
+</div>
+
+
+</header>
+
+ <div class='entry-content'>
+ <div class="sect1">
+<h2 id="_avro_dataformat">Avro DataFormat</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><strong>Available as of Camel version 2.14</strong></p>
+</div>
+<div class="paragraph">
+<p>This component provides a dataformat for avro, which allows
+serialization and deserialization of messages using Apache Avro’s binary
+dataformat. Moreover, it provides support for Apache Avro’s rpc, by
+providing producers and consumers endpoint for using avro over netty or
+http.</p>
+</div>
+<div class="paragraph">
+<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
+for this component:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml"><dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-avro</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency></code></pre>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_apache_avro_overview">Apache Avro Overview</h3>
+<div class="paragraph">
+<p>Avro allows you to define message types and a protocol using a json like
+format and then generate java code for the specified types and messages.
+An example of how a schema looks like is below.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code class="language-xml" data-lang="xml">{"namespace": "org.apache.camel.avro.generated",
+ "protocol": "KeyValueProtocol",
+
+ "types": [
+ {"name": "Key", "type": "record",
+ "fields": [
+ {"name": "key", "type": "string"}
+ ]
+ },
+ {"name": "Value", "type": "record",
+ "fields": [
+ {"name": "value", "type": "string"}
+ ]
+ }
+ ],
+
+ "messages": {
+ "put": {
+ "request": [{"name": "key", "type": "Key"}, {"name": "value", "type": "Value"} ],
+ "response": "null"
+ },
+ "get": {
+ "request": [{"name": "key", "type": "Key"}],
+ "response": "Value"
+ }
+ }
... 237612 lines suppressed ...
--
To stop receiving notification emails like this one, please contact
git-site-role@apache.org.