You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2020/01/24 18:33:40 UTC
[camel] 02/03: Fixed Build Take 2
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 88c25670170ca2c767938ae9a5fc05c2355e7d0d
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Jan 24 18:59:28 2020 +0100
Fixed Build Take 2
---
.../modules/ROOT/pages/file-watch-component.adoc | 4 +-
docs/components/modules/ROOT/pages/index.adoc | 136 +--------------------
.../commands/AbstractLocalCamelController.java | 2 +-
3 files changed, 8 insertions(+), 134 deletions(-)
diff --git a/docs/components/modules/ROOT/pages/file-watch-component.adoc b/docs/components/modules/ROOT/pages/file-watch-component.adoc
index d462dac..a6551c1 100644
--- a/docs/components/modules/ROOT/pages/file-watch-component.adoc
+++ b/docs/components/modules/ROOT/pages/file-watch-component.adoc
@@ -1,7 +1,9 @@
+[[file-watch-component]]
= File Watch Component
:page-source: components/camel-file-watch/src/main/docs/file-watch-component.adoc
*Since Camel 3.0*
+
*Since Camel 3.0*
@@ -168,4 +170,4 @@ relative filename. For absolute files this is the absolute path.
|`CamelFileParent` |The parent path.
|`CamelFileLastModified` |A `Long` value containing the last modified timestamp of the file.
-|===
+|===
\ No newline at end of file
diff --git a/docs/components/modules/ROOT/pages/index.adoc b/docs/components/modules/ROOT/pages/index.adoc
index b051f23..8c8bd6c 100644
--- a/docs/components/modules/ROOT/pages/index.adoc
+++ b/docs/components/modules/ROOT/pages/index.adoc
@@ -6,7 +6,7 @@ The following Apache Camel artifacts are provided:
== Components
// components: START
-Number of Components: 310 in 248 JAR artifacts (1 deprecated)
+Number of Components: 248 in 216 JAR artifacts (1 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -26,8 +26,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:asterisk-component.adoc[Asterisk] (camel-asterisk) | 2.18 | The asterisk component is used to interact with Asterisk PBX Server.
-| xref:atmos-component.adoc[Atmos] (camel-atmos) | 2.15 | The atmos component is used for integrating with EMC's Atomos Storage.
-
| xref:atmosphere-websocket-component.adoc[Atmosphere Websocket] (camel-atmosphere-websocket) | 2.14 | To exchange data with external Websocket clients using Atmosphere.
| xref:atom-component.adoc[Atom] (camel-atom) | 1.2 | The atom component is used for consuming Atom RSS feeds.
@@ -44,8 +42,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:atomix-value-component.adoc[Atomix Value] (camel-atomix) | 2.20 | The atomix-value component is used to access Atomix's distributed value.
-| xref:avro-component.adoc[Avro] (camel-avro) | 2.10 | Working with Apache Avro for data serialization.
-
| xref:aws2-translate-component.adoc[AWS 2 Translate] (camel-aws2-translate) | 3.1 | The aws2-translate component is used for managing Amazon Translate
| xref:aws-cw-component.adoc[AWS CloudWatch] (camel-aws-cw) | 2.11 | The aws-cw component is used for sending metrics to an Amazon CloudWatch.
@@ -74,8 +70,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:aws-msk-component.adoc[AWS MSK] (camel-aws-msk) | 3.0 | The aws-msk is used for managing Amazon MSK
-| xref:aws-s3-component.adoc[AWS S3 Storage Service] (camel-aws-s3) | 2.8 | The aws-s3 component is used for storing and retrieving object from Amazon S3 Storage Service.
-
| xref:aws-ses-component.adoc[AWS Simple Email Service] (camel-aws-ses) | 2.9 | The aws-ses component is used for sending emails with Amazon's SES service.
| xref:aws-sns-component.adoc[AWS Simple Notification System] (camel-aws-sns) | 2.8 | The aws-sns component is used for sending messages to an Amazon Simple Notification Topic.
@@ -110,24 +104,14 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:caffeine-loadcache-component.adoc[Caffeine LoadCache] (camel-caffeine) | 2.20 | The caffeine-loadcache component is used for integration with Caffeine Load Cache.
-| xref:cql-component.adoc[Cassandra CQL] (camel-cassandraql) | 2.15 | The cql component aims at integrating Cassandra 2.0 using the CQL3 API (not the Thrift API). It's based on Cassandra Java Driver provided by DataStax.
-
| xref:chatscript-component.adoc[ChatScript] (camel-chatscript) | 3.0 | Represents a ChatScript endpoint.
| xref:chunk-component.adoc[Chunk] (camel-chunk) | 2.15 | Transforms the message using a Chunk template.
| xref:class-component.adoc[Class] (camel-bean) | 2.4 | The Class component is for invoking Java classes (Java beans) from Camel.
-| xref:cm-sms-component.adoc[CM SMS Gateway] (camel-cm-sms) | 2.18 | The cm-sms component allows to integrate with CM SMS Gateway.
-
-| xref:cmis-component.adoc[CMIS] (camel-cmis) | 2.11 | The cmis component uses the Apache Chemistry client API and allows you to add/read nodes to/from a CMIS compliant content repositories.
-
-| xref:coap-component.adoc[CoAP] (camel-coap) | 2.16 | The coap component is used for sending and receiving messages from COAP capable devices.
-
| xref:cometd-component.adoc[CometD] (camel-cometd) | 2.0 | The cometd component is a transport for working with the Jetty implementation of the cometd/bayeux protocol.
-| xref:consul-component.adoc[Consul] (camel-consul) | 2.18 | The camel consul component allows you to work with Consul, a distributed, highly available, datacenter-aware, service discovery and configuration system.
-
| xref:controlbus-component.adoc[Control Bus] (camel-controlbus) | 2.11 | The controlbus component provides easy management of Camel applications based on the Control Bus EIP pattern.
| xref:corda-component.adoc[Corda] (camel-corda) | 2.23 | The corda component uses corda-rpc to interact with corda nodes.
@@ -176,8 +160,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:drill-component.adoc[Drill] (camel-drill) | 2.19 | The drill component gives you the ability to quering into apache drill cluster.
-| xref:dropbox-component.adoc[Dropbox] (camel-dropbox) | 2.14 | For uploading, downloading and managing files, folders, groups, collaborations, etc on dropbox DOT com.
-
| xref:ehcache-component.adoc[Ehcache] (camel-ehcache) | 2.18 | The ehcache component enables you to perform caching operations using Ehcache as cache implementation.
| xref:elasticsearch-rest-component.adoc[Elastichsearch Rest] (camel-elasticsearch-rest) | 2.21 | The elasticsearch component is used for interfacing with ElasticSearch server using REST API.
@@ -186,17 +168,13 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:elytron-component.adoc[Elytron] (camel-elytron) | 3.1 | The elytron component is allows you to work with the Elytron Security Framework
-| xref:etcd-component.adoc[Etcd] (camel-etcd) | 2.18 | The camel etcd component allows you to work with Etcd, a distributed reliable key-value store.
-
-| xref:exec-component.adoc[Exec] (camel-exec) | 2.3 | The exec component can be used to execute OS system commands.
-
| xref:facebook-component.adoc[Facebook] (camel-facebook) | 2.14 | The Facebook component provides access to all of the Facebook APIs accessible using Facebook4J.
| xref:fhir-component.adoc[FHIR] (camel-fhir) | 2.23 | The fhir component is used for working with the FHIR protocol (health care).
| xref:file-component.adoc[File] (camel-file) | 1.0 | The file component is used for reading or writing files.
-| xref:file-watch-component.adoc[file-watch] (camel-file-watch) | 3.0 | The file-watch is used to monitor file events in directory using java.nio.file.WatchService
+| xref:file-watch-component.adoc[File Watch] (camel-file-watch) | 3.0 | The file-watch is used to monitor file events in directory using java.nio.file.WatchService
| xref:flatpack-component.adoc[Flatpack] (camel-flatpack) | 1.4 | The flatpack component supports fixed width and delimited file parsing via the FlatPack library.
@@ -222,24 +200,8 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:google-bigquery-sql-component.adoc[Google BigQuery Standard SQL] (camel-google-bigquery) | 2.23 | Google BigQuery data warehouse for analytics (using SQL queries).
-| xref:google-calendar-component.adoc[Google Calendar] (camel-google-calendar) | 2.15 | The google-calendar component provides access to Google Calendar.
-
-| xref:google-calendar-stream-component.adoc[Google Calendar Stream] (camel-google-calendar) | 2.23 | The google-calendar component provides access to Google Calendar in a streaming mode.
-
| xref:google-drive-component.adoc[Google Drive] (camel-google-drive) | 2.14 | The google-drive component provides access to Google Drive file storage service.
-| xref:google-mail-component.adoc[Google Mail] (camel-google-mail) | 2.15 | The google-mail component provides access to Google Mail.
-
-| xref:google-mail-stream-component.adoc[Google Mail Stream] (camel-google-mail) | 2.22 | The google-mail component provides access to Google Mail.
-
-| xref:google-pubsub-component.adoc[Google Pubsub] (camel-google-pubsub) | 2.19 | Messaging client for Google Cloud Platform PubSub Service
-
-| xref:google-sheets-component.adoc[Google Sheets] (camel-google-sheets) | 2.23 | The google-sheets component provides access to Google Sheets.
-
-| xref:google-sheets-stream-component.adoc[Google Sheets Stream] (camel-google-sheets) | 2.23 | The google-sheets component provides access to Google Sheets.
-
-| xref:gora-component.adoc[Gora] (camel-gora) | 2.14 | The gora component allows you to work with NoSQL databases using the Apache Gora framework.
-
| xref:grape-component.adoc[Grape] (camel-grape) | 2.16 | The grape component allows you to fetch, load and manage additional jars when CamelContext is running.
| xref:graphql-component.adoc[GraphQL] (camel-graphql) | 3.0 | A Camel GraphQL Component
@@ -248,28 +210,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:guava-eventbus-component.adoc[Guava EventBus] (camel-guava-eventbus) | 2.10 | The guava-eventbus component provides integration bridge between Camel and Google Guava EventBus.
-| xref:hazelcast-atomicvalue-component.adoc[Hazelcast Atomic Number] (camel-hazelcast) | 2.7 | The hazelcast-atomicvalue component is used to access Hazelcast atomic number, which is an object that simply provides a grid wide number (long).
-
-| xref:hazelcast-instance-component.adoc[Hazelcast Instance] (camel-hazelcast) | 2.7 | The hazelcast-instance component is used to consume join/leave events of the cache instance in the cluster.
-
-| xref:hazelcast-list-component.adoc[Hazelcast List] (camel-hazelcast) | 2.7 | The hazelcast-list component is used to access Hazelcast distributed list.
-
-| xref:hazelcast-map-component.adoc[Hazelcast Map] (camel-hazelcast) | 2.7 | The hazelcast-map component is used to access Hazelcast distributed map.
-
-| xref:hazelcast-multimap-component.adoc[Hazelcast Multimap] (camel-hazelcast) | 2.7 | The hazelcast-multimap component is used to to access Hazelcast distributed multimap.
-
-| xref:hazelcast-queue-component.adoc[Hazelcast Queue] (camel-hazelcast) | 2.7 | The hazelcast-queue component is used to access Hazelcast distributed queue.
-
-| xref:hazelcast-replicatedmap-component.adoc[Hazelcast Replicated Map] (camel-hazelcast) | 2.16 | The hazelcast-replicatedmap component is used to access Hazelcast replicated map.
-
-| xref:hazelcast-ringbuffer-component.adoc[Hazelcast Ringbuffer] (camel-hazelcast) | 2.16 | The hazelcast-ringbuffer component is used to access Hazelcast distributed ringbuffer.
-
-| xref:hazelcast-seda-component.adoc[Hazelcast SEDA] (camel-hazelcast) | 2.7 | The hazelcast-seda component is used to access Hazelcast BlockingQueue.
-
-| xref:hazelcast-set-component.adoc[Hazelcast Set] (camel-hazelcast) | 2.7 | The hazelcast-set component is used to access Hazelcast distributed set.
-
-| xref:hazelcast-topic-component.adoc[Hazelcast Topic] (camel-hazelcast) | 2.15 | The hazelcast-topic component is used to access Hazelcast distributed topic.
-
| xref:hbase-component.adoc[HBase] (camel-hbase) | 2.10 | For reading/writing from/to an HBase store (Hadoop database).
| xref:hdfs-component.adoc[HDFS] (camel-hdfs) | 2.14 | For reading/writing from/to an HDFS filesystem using Hadoop 2.x.
@@ -296,8 +236,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:ignite-set-component.adoc[Ignite Sets] (camel-ignite) | 2.17 | The Ignite Sets endpoint is one of camel-ignite endpoints which allows you to interact with Ignite Set data structures.
-| xref:infinispan-component.adoc[Infinispan] (camel-infinispan) | 2.13 | For reading/writing from/to Infinispan distributed key/value store and data grid.
-
| xref:influxdb-component.adoc[InfluxDB] (camel-influxdb) | 2.18 | The influxdb component allows you to interact with InfluxDB, a time series database.
| xref:iota-component.adoc[IOTA] (camel-iota) | 2.23 | Component for integrate IOTA DLT
@@ -314,12 +252,8 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:jcache-component.adoc[JCache] (camel-jcache) | 2.17 | The jcache component enables you to perform caching operations using JSR107/JCache as cache implementation.
-| xref:jclouds-component.adoc[JClouds] (camel-jclouds) | 2.9 | For interacting with cloud compute & blobstore service via jclouds.
-
| xref:jcr-component.adoc[JCR] (camel-jcr) | 1.3 | The jcr component allows you to add/read nodes to/from a JCR compliant content repository.
-| xref:jdbc-component.adoc[JDBC] (camel-jdbc) | 1.2 | The jdbc component enables you to access databases through JDBC, where SQL queries are sent in the message body.
-
| xref:jetty-component.adoc[Jetty] (camel-jetty) | 1.2 | To use Jetty as a HTTP server as consumer for Camel routes.
| xref:websocket-component.adoc[Jetty Websocket] (camel-websocket) | 2.10 | The websocket component provides websocket endpoints with Jetty for communicating with clients using websocket.
@@ -330,8 +264,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:jing-component.adoc[Jing] (camel-jing) | 1.1 | Validates the payload of a message using RelaxNG Syntax using Jing library.
-| xref:jira-component.adoc[Jira] (camel-jira) | 3.0 | The jira component interacts with the JIRA issue tracker.
-
| xref:jms-component.adoc[JMS] (camel-jms) | 1.0 | The jms component allows messages to be sent to (or consumed from) a JMS Queue or Topic.
| xref:jmx-component.adoc[JMX] (camel-jmx) | 2.6 | The jmx component allows to receive JMX notifications.
@@ -348,36 +280,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:jt400-component.adoc[JT400] (camel-jt400) | 1.5 | The jt400 component allows you to exchanges messages with an AS/400 system using data queues or program call.
-| xref:kafka-component.adoc[Kafka] (camel-kafka) | 2.13 | The kafka component allows messages to be sent to (or consumed from) Apache Kafka brokers.
-
-| xref:kubernetes-config-maps-component.adoc[Kubernetes ConfigMap] (camel-kubernetes) | 2.17 | The Kubernetes Configmaps component provides a producer to execute kubernetes configmap operations.
-
-| xref:kubernetes-deployments-component.adoc[Kubernetes Deployments] (camel-kubernetes) | 2.20 | The Kubernetes Nodes component provides a producer to execute kubernetes node operations and a consumer to consume node events.
-
-| xref:kubernetes-hpa-component.adoc[Kubernetes HPA] (camel-kubernetes) | 2.23 | The Kubernetes HPA component provides a producer to execute kubernetes hpa operations and a consumer to consume HPA events.
-
-| xref:kubernetes-job-component.adoc[Kubernetes Job] (camel-kubernetes) | 2.23 | The Kubernetes Jobs component provides a producer to execute kubernetes job operations
-
-| xref:kubernetes-namespaces-component.adoc[Kubernetes Namespaces] (camel-kubernetes) | 2.17 | The Kubernetes Namespaces component provides a producer to execute kubernetes namespace operations and a consumer to consume namespace events.
-
-| xref:kubernetes-nodes-component.adoc[Kubernetes Nodes] (camel-kubernetes) | 2.17 | The Kubernetes Nodes component provides a producer to execute kubernetes node operations and a consumer to consume node events.
-
-| xref:kubernetes-persistent-volumes-component.adoc[Kubernetes Persistent Volume] (camel-kubernetes) | 2.17 | The Kubernetes Persistent Volumes component provides a producer to execute kubernetes persistent volume operations.
-
-| xref:kubernetes-persistent-volumes-claims-component.adoc[Kubernetes Persistent Volume Claim] (camel-kubernetes) | 2.17 | The Kubernetes Persistent Volumes Claims component provides a producer to execute kubernetes persistent volume claim operations.
-
-| xref:kubernetes-pods-component.adoc[Kubernetes Pods] (camel-kubernetes) | 2.17 | The Kubernetes Pods component provides a producer to execute kubernetes pod operations and a consumer to consume pod events.
-
-| xref:kubernetes-replication-controllers-component.adoc[Kubernetes Replication Controller] (camel-kubernetes) | 2.17 | The Kubernetes Replication Controllers component provides a producer to execute kubernetes replication controller operations and a consumer to consume replication controller events.
-
-| xref:kubernetes-resources-quota-component.adoc[Kubernetes Resources Quota] (camel-kubernetes) | 2.17 | The Kubernetes Resources Quota component provides a producer to execute kubernetes resources quota operations.
-
-| xref:kubernetes-secrets-component.adoc[Kubernetes Secrets] (camel-kubernetes) | 2.17 | The Kubernetes Secrets component provides a producer to execute kubernetes secret operations.
-
-| xref:kubernetes-service-accounts-component.adoc[Kubernetes Service Account] (camel-kubernetes) | 2.17 | The Kubernetes Service Accounts component provides a producer to execute service account operations.
-
-| xref:kubernetes-services-component.adoc[Kubernetes Services] (camel-kubernetes) | 2.17 | The Kubernetes Services component provides a producer to execute service operations and a consumer to consume service events.
-
| xref:kudu-component.adoc[Kudu] (camel-kudu) | 3.0 | Represents a Kudu endpoint. A kudu endpoint allows you to interact with Apache Kudu, a free and open source column-oriented data store of the Apache Hadoop ecosystem.
| xref:language-component.adoc[Language] (camel-language) | 2.5 | The language component allows you to send a message to an endpoint which executes a script by any of the supported Languages in Camel.
@@ -424,12 +326,8 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:nagios-component.adoc[Nagios] (camel-nagios) | 2.3 | To send passive checks to Nagios using JSendNSCA.
-| xref:nats-component.adoc[Nats] (camel-nats) | 2.17 | The nats component allows you produce and consume messages from NATS.
-
| xref:netty-component.adoc[Netty] (camel-netty) | 2.14 | Socket level networking using TCP or UDP with the Netty 4.x library.
-| xref:netty-http-component.adoc[Netty HTTP] (camel-netty-http) | 2.14 | Netty HTTP server and client using the Netty 4.x library.
-
| xref:nitrite-component.adoc[Nitrite] (camel-nitrite) | 3.0 | Used for integrating Camel with Nitrite databases.
| xref:nsq-component.adoc[NSQ] (camel-nsq) | 2.23 | Represents a nsq endpoint.
@@ -438,14 +336,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:olingo4-component.adoc[Olingo4] (camel-olingo4) | 2.19 | Communicates with OData 4.0 services using Apache Olingo OData API.
-| xref:milo-client-component.adoc[OPC UA Client] (camel-milo) | 2.19 | Connect to OPC UA servers using the binary protocol for acquiring telemetry data
-
-| xref:milo-server-component.adoc[OPC UA Server] (camel-milo) | 2.19 | Make telemetry data available as an OPC UA server
-
-| xref:openshift-build-configs-component.adoc[Openshift Build Config] (camel-kubernetes) | 2.17 | The Kubernetes Build Config component provides a producer to execute kubernetes build config operations.
-
-| xref:openshift-builds-component.adoc[Openshift Builds] (camel-kubernetes) | 2.17 | The Openshift Builds component provides a producer to execute openshift build operations.
-
| xref:openstack-cinder-component.adoc[OpenStack Cinder] (camel-openstack) | 2.19 | The openstack-cinder component allows messages to be sent to an OpenStack block storage services.
| xref:openstack-glance-component.adoc[OpenStack Glance] (camel-openstack) | 2.19 | The openstack-glance component allows messages to be sent to an OpenStack image services.
@@ -458,14 +348,10 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:openstack-swift-component.adoc[OpenStack Swift] (camel-openstack) | 2.19 | The openstack-swift component allows messages to be sent to an OpenStack object storage services.
-| xref:optaplanner-component.adoc[OptaPlanner] (camel-optaplanner) | 2.13 | Solves the planning problem contained in a message with OptaPlanner.
-
| xref:eventadmin-component.adoc[OSGi EventAdmin] (camel-eventadmin) | 2.6 | The eventadmin component can be used in an OSGi environment to receive OSGi EventAdmin events and process them.
| xref:paxlogging-component.adoc[OSGi PAX Logging] (camel-paxlogging) | 2.6 | The paxlogging component can be used in an OSGi environment to receive PaxLogging events and process them.
-| xref:paho-component.adoc[Paho] (camel-paho) | 2.16 | Component for communicating with MQTT message brokers using Eclipse Paho MQTT Client.
-
| xref:pdf-component.adoc[PDF] (camel-pdf) | 2.16 | The pdf components provides the ability to create, modify or extract content from PDF documents.
| xref:platform-http-component.adoc[Platform HTTP] (camel-platform-http) | 3.0 | HTTP service leveraging existing runtime platform HTTP server
@@ -478,8 +364,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:pubnub-component.adoc[PubNub] (camel-pubnub) | 2.19 | To send and receive messages to PubNub data stream network for connected devices.
-| xref:pulsar-component.adoc[Pulsar] (camel-pulsar) | 2.24 | Camel Apache Pulsar Component
-
| xref:quartz-component.adoc[Quartz] (camel-quartz) | 2.12 | Provides a scheduled delivery of messages using the Quartz 2.x scheduler.
| xref:quickfix-component.adoc[QuickFix] (camel-quickfix) | 2.1 | The quickfix component allows to send Financial Interchange (FIX) messages to the QuickFix engine.
@@ -558,12 +442,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:spring-redis-component.adoc[Spring Redis] (camel-spring-redis) | 2.11 | The spring-redis component allows sending and receiving messages from Redis.
-| xref:spring-ws-component.adoc[Spring WebService] (camel-spring-ws) | 2.6 | The spring-ws component is used for SOAP WebServices using Spring WebServices.
-
-| xref:sql-component.adoc[SQL] (camel-sql) | 1.4 | The sql component allows you to work with databases using JDBC SQL queries.
-
-| xref:sql-stored-component.adoc[SQL Stored Procedure] (camel-sql) | 2.17 | The sql component allows you to work with databases using JDBC Stored Procedure queries.
-
| xref:ssh-component.adoc[SSH] (camel-ssh) | 2.10 | The ssh component enables access to SSH servers such that you can send an SSH command, and process the response.
| xref:stax-component.adoc[StAX] (camel-stax) | 2.9 | The stax component allows messages to be process through a SAX ContentHandler.
@@ -576,8 +454,6 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
| xref:stub-component.adoc[Stub] (camel-stub) | 2.10 | The stub component provides a simple way to stub out any physical endpoints while in development or testing.
-| xref:telegram-component.adoc[Telegram] (camel-telegram) | 2.18 | The telegram component provides access to the Telegram Bot API.
-
| xref:thrift-component.adoc[Thrift] (camel-thrift) | 2.20 | The Thrift component allows to call and expose remote procedures (RPC) with Apache Thrift data format and serialization mechanism
| xref:tika-component.adoc[Tika] (camel-tika) | 2.19 | This component integrates with Apache Tika to extract content and metadata from thousands of file types.
@@ -638,7 +514,7 @@ Number of Components: 310 in 248 JAR artifacts (1 deprecated)
== Data Formats
// dataformats: START
-Number of Data Formats: 45 in 37 JAR artifacts (0 deprecated)
+Number of Data Formats: 44 in 36 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -648,8 +524,6 @@ Number of Data Formats: 45 in 37 JAR artifacts (0 deprecated)
| xref:asn1-dataformat.adoc[ASN.1 File] (camel-asn1) | 2.20 | The ASN.1 data format is used for file transfer with telecommunications protocols.
-| xref:avro-dataformat.adoc[Avro] (camel-avro) | 2.14 | The Avro data format is used for serialization and deserialization of messages using Apache Avro binary dataformat.
-
| xref:barcode-dataformat.adoc[Barcode] (camel-barcode) | 2.14 | The Barcode data format is used for creating barccode images (such as QR-Code)
| xref:base64-dataformat.adoc[Base64] (camel-base64) | 2.11 | The Base64 data format is used for base64 encoding and decoding.
@@ -784,7 +658,7 @@ Number of Languages: 17 in 11 JAR artifacts (0 deprecated)
== Miscellaneous Components
// others: START
-Number of Miscellaneous Components: 36 in 36 JAR artifacts (0 deprecated)
+Number of Miscellaneous Components: 35 in 35 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -794,8 +668,6 @@ Number of Miscellaneous Components: 36 in 36 JAR artifacts (0 deprecated)
| xref:aws-xray.adoc[AWS XRay] (camel-aws-xray) | 2.21 | Distributed tracing using AWS XRay
-| xref:blueprint.adoc[Blueprint] (camel-blueprint) | 2.4 | Using Camel with OSGi Blueprint
-
| xref:cdi.adoc[CDI] (camel-cdi) | 2.10 | Using Camel with CDI
| xref:cxf-transport.adoc[CXF Transport] (camel-cxf-transport) | 2.8 | Camel Transport for Apache CXF
diff --git a/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractLocalCamelController.java b/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractLocalCamelController.java
index 1f9f0e2..90a6ce1 100644
--- a/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractLocalCamelController.java
+++ b/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractLocalCamelController.java
@@ -89,7 +89,7 @@ public abstract class AbstractLocalCamelController extends AbstractCamelControll
answer.put("classResolver", context.getClassResolver().toString());
answer.put("packageScanClassResolver", context.adapt(ExtendedCamelContext.class).getPackageScanClassResolver().toString());
answer.put("applicationContextClassLoader", context.getApplicationContextClassLoader().toString());
- answer.put("headersMapFactory", context.getHeadersMapFactory().toString());
+ answer.put("headersMapFactory", context.adapt(ExtendedCamelContext.class).getHeadersMapFactory().toString());
for (Map.Entry<String, String> entry : context.getGlobalOptions().entrySet()) {
answer.put("property." + entry.getKey(), entry.getValue());