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/10/14 08:33:53 UTC
[camel] 06/08: CAMEL-15684 - Removed camel-hipchat
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 bfd9ef330ff67bba1875bac9a2332833fc487fd5
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Wed Oct 14 10:31:25 2020 +0200
CAMEL-15684 - Removed camel-hipchat
---
.../org/apache/camel/catalog/components.properties | 1 -
.../apache/camel/catalog/components/hipchat.json | 59 -----
.../org/apache/camel/catalog/docs.properties | 1 -
.../camel/catalog/docs/hipchat-component.adoc | 246 --------------------
docs/components/modules/ROOT/nav.adoc | 1 -
.../modules/ROOT/pages/hipchat-component.adoc | 248 ---------------------
6 files changed, 556 deletions(-)
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components.properties b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components.properties
index e7eebaa..09c54a2 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components.properties
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components.properties
@@ -161,7 +161,6 @@ hazelcast-set
hazelcast-topic
hbase
hdfs
-hipchat
http
https
iec60870-client
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/hipchat.json b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/hipchat.json
deleted file mode 100644
index 872542f..0000000
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/components/hipchat.json
+++ /dev/null
@@ -1,59 +0,0 @@
-{
- "component": {
- "kind": "component",
- "name": "hipchat",
- "title": "Hipchat",
- "description": "Send and receive messages to\/from Hipchat service.",
- "deprecated": false,
- "firstVersion": "2.15.0",
- "label": "api,chat,cloud",
- "javaType": "org.apache.camel.component.hipchat.HipchatComponent",
- "supportLevel": "Stable",
- "groupId": "org.apache.camel",
- "artifactId": "camel-hipchat",
- "version": "3.6.0-SNAPSHOT",
- "scheme": "hipchat",
- "extendsScheme": "",
- "syntax": "hipchat:protocol:host:port",
- "async": false,
- "api": false,
- "consumerOnly": false,
- "producerOnly": false,
- "lenientProperties": false
- },
- "componentProperties": {
- "bridgeErrorHandler": { "kind": "property", "displayName": "Bridge Error Handler", "group": "consumer", "label": "consumer", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "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 [...]
- "lazyStartProducer": { "kind": "property", "displayName": "Lazy Start Producer", "group": "producer", "label": "producer", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the r [...]
- "basicPropertyBinding": { "kind": "property", "displayName": "Basic Property Binding", "group": "advanced", "label": "advanced", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": true, "secret": false, "defaultValue": false, "description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities" }
- },
- "properties": {
- "protocol": { "kind": "path", "displayName": "Protocol", "group": "common", "label": "", "required": true, "type": "string", "javaType": "java.lang.String", "deprecated": false, "deprecationNote": "", "secret": false, "configurationClass": "org.apache.camel.component.hipchat.HipchatConfiguration", "configurationField": "configuration", "description": "The protocol for the hipchat server, such as http." },
- "host": { "kind": "path", "displayName": "Host", "group": "common", "label": "", "required": true, "type": "string", "javaType": "java.lang.String", "deprecated": false, "deprecationNote": "", "secret": false, "configurationClass": "org.apache.camel.component.hipchat.HipchatConfiguration", "configurationField": "configuration", "description": "The host for the hipchat server, such as api.hipchat.com" },
- "port": { "kind": "path", "displayName": "Port", "group": "common", "label": "", "required": false, "type": "integer", "javaType": "java.lang.Integer", "deprecated": false, "secret": false, "defaultValue": "80", "configurationClass": "org.apache.camel.component.hipchat.HipchatConfiguration", "configurationField": "configuration", "description": "The port for the hipchat server. Is by default 80." },
- "authToken": { "kind": "parameter", "displayName": "Auth Token", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "configurationClass": "org.apache.camel.component.hipchat.HipchatConfiguration", "configurationField": "configuration", "description": "OAuth 2 auth token" },
- "consumeUsers": { "kind": "parameter", "displayName": "Consume Users", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "configurationClass": "org.apache.camel.component.hipchat.HipchatConfiguration", "configurationField": "configuration", "description": "Username(s) when consuming messages from the hiptchat server. Multiple user names can be separated by comma." },
- "httpClient": { "kind": "parameter", "displayName": "Http Client", "group": "common", "label": "", "required": false, "type": "object", "javaType": "org.apache.http.impl.client.CloseableHttpClient", "deprecated": false, "secret": false, "defaultValue": "CloseableHttpClient default from HttpClient library", "configurationClass": "org.apache.camel.component.hipchat.HipchatConfiguration", "configurationField": "configuration", "description": "The CloseableHttpClient reference from regis [...]
- "bridgeErrorHandler": { "kind": "parameter", "displayName": "Bridge Error Handler", "group": "consumer", "label": "consumer", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "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 b [...]
- "sendEmptyMessageWhenIdle": { "kind": "parameter", "displayName": "Send Empty Message When Idle", "group": "consumer", "label": "consumer", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead." },
- "exceptionHandler": { "kind": "parameter", "displayName": "Exception Handler", "group": "consumer (advanced)", "label": "consumer,advanced", "required": false, "type": "object", "javaType": "org.apache.camel.spi.ExceptionHandler", "optionalPrefix": "consumer.", "deprecated": false, "secret": false, "description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with [...]
- "exchangePattern": { "kind": "parameter", "displayName": "Exchange Pattern", "group": "consumer (advanced)", "label": "consumer,advanced", "required": false, "type": "object", "javaType": "org.apache.camel.ExchangePattern", "enum": [ "InOnly", "InOut", "InOptionalOut" ], "deprecated": false, "secret": false, "description": "Sets the exchange pattern when the consumer creates an exchange." },
- "pollStrategy": { "kind": "parameter", "displayName": "Poll Strategy", "group": "consumer (advanced)", "label": "consumer,advanced", "required": false, "type": "object", "javaType": "org.apache.camel.spi.PollingConsumerPollStrategy", "deprecated": false, "secret": false, "description": "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 h [...]
- "lazyStartProducer": { "kind": "parameter", "displayName": "Lazy Start Producer", "group": "producer", "label": "producer", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the [...]
- "basicPropertyBinding": { "kind": "parameter", "displayName": "Basic Property Binding", "group": "advanced", "label": "advanced", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities" },
- "synchronous": { "kind": "parameter", "displayName": "Synchronous", "group": "advanced", "label": "advanced", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported)." },
- "backoffErrorThreshold": { "kind": "parameter", "displayName": "Backoff Error Threshold", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "integer", "javaType": "int", "deprecated": false, "secret": false, "description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in." },
- "backoffIdleThreshold": { "kind": "parameter", "displayName": "Backoff Idle Threshold", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "integer", "javaType": "int", "deprecated": false, "secret": false, "description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in." },
- "backoffMultiplier": { "kind": "parameter", "displayName": "Backoff Multiplier", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "integer", "javaType": "int", "deprecated": false, "secret": false, "description": "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 [...]
- "delay": { "kind": "parameter", "displayName": "Delay", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "integer", "javaType": "long", "deprecated": false, "secret": false, "defaultValue": 5000, "description": "Milliseconds before the next poll." },
- "greedy": { "kind": "parameter", "displayName": "Greedy", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": false, "description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages." },
- "initialDelay": { "kind": "parameter", "displayName": "Initial Delay", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "integer", "javaType": "long", "deprecated": false, "secret": false, "defaultValue": 1000, "description": "Milliseconds before the first poll starts." },
- "repeatCount": { "kind": "parameter", "displayName": "Repeat Count", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "integer", "javaType": "long", "deprecated": false, "secret": false, "defaultValue": 0, "description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever." },
- "runLoggingLevel": { "kind": "parameter", "displayName": "Run Logging Level", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "object", "javaType": "org.apache.camel.LoggingLevel", "enum": [ "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "OFF" ], "deprecated": false, "secret": false, "defaultValue": "TRACE", "description": "The consumer logs a start\/complete log line when it polls. This option allows you to configure the logging level for that." },
- "scheduledExecutorService": { "kind": "parameter", "displayName": "Scheduled Executor Service", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "object", "javaType": "java.util.concurrent.ScheduledExecutorService", "deprecated": false, "secret": false, "description": "Allows for configuring a custom\/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool." },
- "scheduler": { "kind": "parameter", "displayName": "Scheduler", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "object", "javaType": "java.lang.Object", "deprecated": false, "secret": false, "defaultValue": "none", "description": "To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler" },
- "schedulerProperties": { "kind": "parameter", "displayName": "Scheduler Properties", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "object", "javaType": "java.util.Map<java.lang.String, java.lang.Object>", "prefix": "scheduler.", "multiValue": true, "deprecated": false, "secret": false, "description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler." },
- "startScheduler": { "kind": "parameter", "displayName": "Start Scheduler", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": true, "description": "Whether the scheduler should be auto started." },
- "timeUnit": { "kind": "parameter", "displayName": "Time Unit", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "object", "javaType": "java.util.concurrent.TimeUnit", "enum": [ "NANOSECONDS", "MICROSECONDS", "MILLISECONDS", "SECONDS", "MINUTES", "HOURS", "DAYS" ], "deprecated": false, "secret": false, "defaultValue": "MILLISECONDS", "description": "Time unit for initialDelay and delay options." },
- "useFixedDelay": { "kind": "parameter", "displayName": "Use Fixed Delay", "group": "scheduler", "label": "consumer,scheduler", "required": false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false, "defaultValue": true, "description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details." }
- }
-}
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties
index eeb7887..adb36cf 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs.properties
@@ -218,7 +218,6 @@ hbase-component
hdfs-component
header-language
headersmap
-hipchat-component
hl7-dataformat
hl7terser-language
http-component
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hipchat-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hipchat-component.adoc
deleted file mode 100644
index 7b53762..0000000
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/hipchat-component.adoc
+++ /dev/null
@@ -1,246 +0,0 @@
-[[hipchat-component]]
-= Hipchat Component
-:docTitle: Hipchat
-:artifactId: camel-hipchat
-:description: Send and receive messages to/from Hipchat service.
-:since: 2.15
-:supportLevel: Stable
-:component-header: Both producer and consumer are supported
-include::{cq-version}@camel-quarkus:ROOT:partial$reference/components/hipchat.adoc[]
-
-*Since Camel {since}*
-
-*{component-header}*
-
-The Hipchat component supports producing and consuming messages from/to
-https://www.hipchat.com[Hipchat] service.
-
-*Prerequisites*
-
-You must have a valid Hipchat user account and get a
-https://www.hipchat.com/account/api[personal access token] that you can
-use to produce/consume messages.
-
-
-== URI Format
-
-[source,java]
--------------------------------
-hipchat://[host][:port]?options
--------------------------------
-
-You can append query options to the URI in the following format,
-?options=value&option2=value&...
-
-== URI Options
-
-
-// component options: START
-The Hipchat component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *bridgeErrorHandler* (consumer) | 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. | false | boolean
-| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
-| *basicPropertyBinding* (advanced) | *Deprecated* Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
-|===
-// component options: END
-
-
-
-
-
-
-// endpoint options: START
-The Hipchat endpoint is configured using URI syntax:
-
-----
-hipchat:protocol:host:port
-----
-
-with the following path and query parameters:
-
-=== Path Parameters (3 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *protocol* | *Required* The protocol for the hipchat server, such as http. | | String
-| *host* | *Required* The host for the hipchat server, such as api.hipchat.com | | String
-| *port* | The port for the hipchat server. Is by default 80. | 80 | Integer
-|===
-
-
-=== Query Parameters (25 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *authToken* (common) | OAuth 2 auth token | | String
-| *consumeUsers* (common) | Username(s) when consuming messages from the hiptchat server. Multiple user names can be separated by comma. | | String
-| *httpClient* (common) | The CloseableHttpClient reference from registry to be used during API HTTP requests. | CloseableHttpClient default from HttpClient library | CloseableHttpClient
-| *bridgeErrorHandler* (consumer) | 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. | false | boolean
-| *sendEmptyMessageWhenIdle* (consumer) | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | boolean
-| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | | ExceptionHandler
-| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer creates an exchange. There are 3 enums and the value can be one of: InOnly, InOut, InOptionalOut | | ExchangePattern
-| *pollStrategy* (consumer) | 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. | | PollingConsumerPollStrategy
-| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
-| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
-| *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean
-| *backoffErrorThreshold* (scheduler) | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | | int
-| *backoffIdleThreshold* (scheduler) | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | | int
-| *backoffMultiplier* (scheduler) | 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. | | int
-| *delay* (scheduler) | Milliseconds before the next poll. | 5000 | long
-| *greedy* (scheduler) | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | boolean
-| *initialDelay* (scheduler) | Milliseconds before the first poll starts. | 1000 | long
-| *repeatCount* (scheduler) | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0 | long
-| *runLoggingLevel* (scheduler) | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. There are 6 enums and the value can be one of: TRACE, DEBUG, INFO, WARN, ERROR, OFF | TRACE | LoggingLevel
-| *scheduledExecutorService* (scheduler) | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | | ScheduledExecutorService
-| *scheduler* (scheduler) | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | none | Object
-| *schedulerProperties* (scheduler) | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | | Map
-| *startScheduler* (scheduler) | Whether the scheduler should be auto started. | true | boolean
-| *timeUnit* (scheduler) | Time unit for initialDelay and delay options. There are 7 enums and the value can be one of: NANOSECONDS, MICROSECONDS, MILLISECONDS, SECONDS, MINUTES, HOURS, DAYS | MILLISECONDS | TimeUnit
-| *useFixedDelay* (scheduler) | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | boolean
-|===
-// endpoint options: END
-
-
-
-
-
-
-
-== Scheduled Poll Consumer
-
-This component implements the
-ScheduledPollConsumer. Only the last message
-from the provided 'consumeUsers' are retrieved and sent as Exchange
-body. If you do not want the same message to be retrieved again when
-there are no new messages on next poll then you can add the
-idempotent consumer as shown below. All
-the options on the ScheduledPollConsumer can
-also be used for more control on the consumer.
-
-[source,java]
----------------------------------------------------------------------------------
-@Override
-public void configure() throws Exception {
- String hipchatEndpointUri = "hipchat://?authToken=XXXX&consumeUsers=@Joe,@John";
- from(hipchatEndpointUri)
- .idempotentConsumer(
- simple("${in.header.HipchatMessageDate} ${in.header.HipchatFromUser}"),
- MemoryIdempotentRepository.memoryIdempotentRepository(200)
- )
- .to("mock:result");
-}
----------------------------------------------------------------------------------
-
-=== Message headers set by the Hipchat consumer
-
-[width="100%",cols="10%,10%,10%,70%",options="header",]
-|=======================================================================
-
-|*Header* |*Constant* |*Type* |*Description*
-
-|HipchatFromUser |HipchatConstants.FROM_USER |_String_ |The body has the message that was sent from this user to the owner of
-authToken
-
-|HipchatMessageDate |HipchatConstants.MESSAGE_DATE |_String_ |The date message was sent. The format is ISO-8601 as present in the
-Hipchat https://www.hipchat.com/docs/apiv2/method/view_recent_privatechat_history[response].
-
-|HipchatFromUserResponseStatus |HipchatConstants.FROM_USER_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_
-The status of the API response received.
-|=======================================================================
-
-== Hipchat Producer
-
-Producer can send messages to both Room's and User's simultaneously. The
-body of the exchange is sent as message. Sample usage is shown below.
-Appropriate headers needs to be set.
-
-[source,java]
-----------------------------------------------------------
-@Override
- public void configure() throws Exception {
- String hipchatEndpointUri = "hipchat://?authToken=XXXX";
- from("direct:start")
- .to(hipchatEndpointUri)
- .to("mock:result");
- }
-----------------------------------------------------------
-
-=== Message headers evaluated by the Hipchat producer
-
-[width="100%",cols="10%,10%,10%,70%",options="header",]
-|=======================================================================
-
-|*Header* |*Constant* |*Type* |*Description*
-
-|HipchatToUser |HipchatConstants.TO_USER |_String_ |The Hipchat user to which the message needs to be sent.
-
-|HipchatToRoom |HipchatConstants.TO_ROOM |_String_ |The Hipchat room to which the message needs to be sent.
-
-|HipchatMessageFormat |HipchatConstants.MESSAGE_FORMAT |String |Valid formats are 'text' or 'html'. *Default: 'text'*
-
-|HipchatMessageBackgroundColor |HipchatConstants.MESSAGE_BACKGROUND_COLOR |_String_ |Valid color values are 'yellow', 'green', 'red', 'purple', 'gray',
-'random'. *Default: 'yellow' (Room Only)*
-
-|HipchatTriggerNotification |HipchatConstants.TRIGGER_NOTIFY |_String_ |Valid values are 'true' or 'false'. Whether this message should trigger
-a user notification (change the tab color, play a sound, notify mobile
-phones, etc). *Default: 'false' (Room Only)*
-|=======================================================================
-
-=== Message headers set by the Hipchat producer
-
-[width="100%",cols="10%,10%,10%,70%",options="header",]
-|=======================================================================
-
-|*Header* |*Constant* |*Type* |*Description*
-
-|HipchatToUserResponseStatus |HipchatConstants.TO_USER_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_
-The status of the API response received when message sent to the user.
-
-|HipchatFromUserResponseStatus |HipchatConstants.TO_ROOM_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_ |The status of the API response received when message sent to the room.
-|=======================================================================
-
-=== Configuring Http Client
-
-The HipChat component allow your own `HttpClient` configuration. This can be done by defining a reference for `CloseableHttpClient` in the http://camel.apache.org/registry.html[registry] (e.g. Spring Context) and then, set the parameter during the Endpoint definition, for example: `hipchat:http://api.hipchat.com?httpClient=#myHttpClient`.
-
-[source,java]
-------------------------------------------
-CloseableHttpClient httpclient = HttpClients.custom()
- .setConnectionManager(connManager)
- .setDefaultCookieStore(cookieStore)
- .setDefaultCredentialsProvider(credentialsProvider)
- .setProxy(new HttpHost("myproxy", 8080))
- .setDefaultRequestConfig(defaultRequestConfig)
- .build();
-------------------------------------------
-
-To see more information about Http Client configuration, please check the https://hc.apache.org/httpcomponents-client-ga/examples.html[official documentation].
-
-
-=== Dependencies
-
-Maven users will need to add the following dependency to their pom.xml.
-
-*pom.xml*
-
-[source,xml]
-------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-hipchat</artifactId>
- <version>${camel-version}</version>
-</dependency>
-------------------------------------------
-
-where `$\{camel-version}` must be replaced by the actual version of Camel.
-
-include::camel-spring-boot::page$hipchat-starter.adoc[]
diff --git a/docs/components/modules/ROOT/nav.adoc b/docs/components/modules/ROOT/nav.adoc
index f5c3113..1fc770a 100644
--- a/docs/components/modules/ROOT/nav.adoc
+++ b/docs/components/modules/ROOT/nav.adoc
@@ -164,7 +164,6 @@
*** xref:hazelcast-topic-component.adoc[Hazelcast Topic]
** xref:hbase-component.adoc[HBase]
** xref:hdfs-component.adoc[HDFS]
-** xref:hipchat-component.adoc[Hipchat]
** xref:http-component.adoc[HTTP]
** xref:iec60870-client-component.adoc[IEC 60870 Client]
** xref:iec60870-server-component.adoc[IEC 60870 Server]
diff --git a/docs/components/modules/ROOT/pages/hipchat-component.adoc b/docs/components/modules/ROOT/pages/hipchat-component.adoc
deleted file mode 100644
index 422caf1..0000000
--- a/docs/components/modules/ROOT/pages/hipchat-component.adoc
+++ /dev/null
@@ -1,248 +0,0 @@
-[[hipchat-component]]
-= Hipchat Component
-//THIS FILE IS COPIED: EDIT THE SOURCE FILE:
-:page-source: components/camel-hipchat/src/main/docs/hipchat-component.adoc
-:docTitle: Hipchat
-:artifactId: camel-hipchat
-:description: Send and receive messages to/from Hipchat service.
-:since: 2.15
-:supportLevel: Stable
-:component-header: Both producer and consumer are supported
-include::{cq-version}@camel-quarkus:ROOT:partial$reference/components/hipchat.adoc[]
-
-*Since Camel {since}*
-
-*{component-header}*
-
-The Hipchat component supports producing and consuming messages from/to
-https://www.hipchat.com[Hipchat] service.
-
-*Prerequisites*
-
-You must have a valid Hipchat user account and get a
-https://www.hipchat.com/account/api[personal access token] that you can
-use to produce/consume messages.
-
-
-== URI Format
-
-[source,java]
--------------------------------
-hipchat://[host][:port]?options
--------------------------------
-
-You can append query options to the URI in the following format,
-?options=value&option2=value&...
-
-== URI Options
-
-
-// component options: START
-The Hipchat component supports 3 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *bridgeErrorHandler* (consumer) | 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. | false | boolean
-| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
-| *basicPropertyBinding* (advanced) | *Deprecated* Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
-|===
-// component options: END
-
-
-
-
-
-
-// endpoint options: START
-The Hipchat endpoint is configured using URI syntax:
-
-----
-hipchat:protocol:host:port
-----
-
-with the following path and query parameters:
-
-=== Path Parameters (3 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *protocol* | *Required* The protocol for the hipchat server, such as http. | | String
-| *host* | *Required* The host for the hipchat server, such as api.hipchat.com | | String
-| *port* | The port for the hipchat server. Is by default 80. | 80 | Integer
-|===
-
-
-=== Query Parameters (25 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *authToken* (common) | OAuth 2 auth token | | String
-| *consumeUsers* (common) | Username(s) when consuming messages from the hiptchat server. Multiple user names can be separated by comma. | | String
-| *httpClient* (common) | The CloseableHttpClient reference from registry to be used during API HTTP requests. | CloseableHttpClient default from HttpClient library | CloseableHttpClient
-| *bridgeErrorHandler* (consumer) | 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. | false | boolean
-| *sendEmptyMessageWhenIdle* (consumer) | If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. | false | boolean
-| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | | ExceptionHandler
-| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer creates an exchange. There are 3 enums and the value can be one of: InOnly, InOut, InOptionalOut | | ExchangePattern
-| *pollStrategy* (consumer) | 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. | | PollingConsumerPollStrategy
-| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
-| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
-| *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean
-| *backoffErrorThreshold* (scheduler) | The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. | | int
-| *backoffIdleThreshold* (scheduler) | The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. | | int
-| *backoffMultiplier* (scheduler) | 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. | | int
-| *delay* (scheduler) | Milliseconds before the next poll. | 5000 | long
-| *greedy* (scheduler) | If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. | false | boolean
-| *initialDelay* (scheduler) | Milliseconds before the first poll starts. | 1000 | long
-| *repeatCount* (scheduler) | Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. | 0 | long
-| *runLoggingLevel* (scheduler) | The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. There are 6 enums and the value can be one of: TRACE, DEBUG, INFO, WARN, ERROR, OFF | TRACE | LoggingLevel
-| *scheduledExecutorService* (scheduler) | Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. | | ScheduledExecutorService
-| *scheduler* (scheduler) | To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler | none | Object
-| *schedulerProperties* (scheduler) | To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. | | Map
-| *startScheduler* (scheduler) | Whether the scheduler should be auto started. | true | boolean
-| *timeUnit* (scheduler) | Time unit for initialDelay and delay options. There are 7 enums and the value can be one of: NANOSECONDS, MICROSECONDS, MILLISECONDS, SECONDS, MINUTES, HOURS, DAYS | MILLISECONDS | TimeUnit
-| *useFixedDelay* (scheduler) | Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. | true | boolean
-|===
-// endpoint options: END
-
-
-
-
-
-
-
-== Scheduled Poll Consumer
-
-This component implements the
-ScheduledPollConsumer. Only the last message
-from the provided 'consumeUsers' are retrieved and sent as Exchange
-body. If you do not want the same message to be retrieved again when
-there are no new messages on next poll then you can add the
-idempotent consumer as shown below. All
-the options on the ScheduledPollConsumer can
-also be used for more control on the consumer.
-
-[source,java]
----------------------------------------------------------------------------------
-@Override
-public void configure() throws Exception {
- String hipchatEndpointUri = "hipchat://?authToken=XXXX&consumeUsers=@Joe,@John";
- from(hipchatEndpointUri)
- .idempotentConsumer(
- simple("${in.header.HipchatMessageDate} ${in.header.HipchatFromUser}"),
- MemoryIdempotentRepository.memoryIdempotentRepository(200)
- )
- .to("mock:result");
-}
----------------------------------------------------------------------------------
-
-=== Message headers set by the Hipchat consumer
-
-[width="100%",cols="10%,10%,10%,70%",options="header",]
-|=======================================================================
-
-|*Header* |*Constant* |*Type* |*Description*
-
-|HipchatFromUser |HipchatConstants.FROM_USER |_String_ |The body has the message that was sent from this user to the owner of
-authToken
-
-|HipchatMessageDate |HipchatConstants.MESSAGE_DATE |_String_ |The date message was sent. The format is ISO-8601 as present in the
-Hipchat https://www.hipchat.com/docs/apiv2/method/view_recent_privatechat_history[response].
-
-|HipchatFromUserResponseStatus |HipchatConstants.FROM_USER_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_
-The status of the API response received.
-|=======================================================================
-
-== Hipchat Producer
-
-Producer can send messages to both Room's and User's simultaneously. The
-body of the exchange is sent as message. Sample usage is shown below.
-Appropriate headers needs to be set.
-
-[source,java]
-----------------------------------------------------------
-@Override
- public void configure() throws Exception {
- String hipchatEndpointUri = "hipchat://?authToken=XXXX";
- from("direct:start")
- .to(hipchatEndpointUri)
- .to("mock:result");
- }
-----------------------------------------------------------
-
-=== Message headers evaluated by the Hipchat producer
-
-[width="100%",cols="10%,10%,10%,70%",options="header",]
-|=======================================================================
-
-|*Header* |*Constant* |*Type* |*Description*
-
-|HipchatToUser |HipchatConstants.TO_USER |_String_ |The Hipchat user to which the message needs to be sent.
-
-|HipchatToRoom |HipchatConstants.TO_ROOM |_String_ |The Hipchat room to which the message needs to be sent.
-
-|HipchatMessageFormat |HipchatConstants.MESSAGE_FORMAT |String |Valid formats are 'text' or 'html'. *Default: 'text'*
-
-|HipchatMessageBackgroundColor |HipchatConstants.MESSAGE_BACKGROUND_COLOR |_String_ |Valid color values are 'yellow', 'green', 'red', 'purple', 'gray',
-'random'. *Default: 'yellow' (Room Only)*
-
-|HipchatTriggerNotification |HipchatConstants.TRIGGER_NOTIFY |_String_ |Valid values are 'true' or 'false'. Whether this message should trigger
-a user notification (change the tab color, play a sound, notify mobile
-phones, etc). *Default: 'false' (Room Only)*
-|=======================================================================
-
-=== Message headers set by the Hipchat producer
-
-[width="100%",cols="10%,10%,10%,70%",options="header",]
-|=======================================================================
-
-|*Header* |*Constant* |*Type* |*Description*
-
-|HipchatToUserResponseStatus |HipchatConstants.TO_USER_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_
-The status of the API response received when message sent to the user.
-
-|HipchatFromUserResponseStatus |HipchatConstants.TO_ROOM_RESPONSE_STATUS |_http://hc.apache.org/httpcomponents-core-4.2.x/httpcore/apidocs/org/apache/http/StatusLine.html[StatusLine]_ |The status of the API response received when message sent to the room.
-|=======================================================================
-
-=== Configuring Http Client
-
-The HipChat component allow your own `HttpClient` configuration. This can be done by defining a reference for `CloseableHttpClient` in the http://camel.apache.org/registry.html[registry] (e.g. Spring Context) and then, set the parameter during the Endpoint definition, for example: `hipchat:http://api.hipchat.com?httpClient=#myHttpClient`.
-
-[source,java]
-------------------------------------------
-CloseableHttpClient httpclient = HttpClients.custom()
- .setConnectionManager(connManager)
- .setDefaultCookieStore(cookieStore)
- .setDefaultCredentialsProvider(credentialsProvider)
- .setProxy(new HttpHost("myproxy", 8080))
- .setDefaultRequestConfig(defaultRequestConfig)
- .build();
-------------------------------------------
-
-To see more information about Http Client configuration, please check the https://hc.apache.org/httpcomponents-client-ga/examples.html[official documentation].
-
-
-=== Dependencies
-
-Maven users will need to add the following dependency to their pom.xml.
-
-*pom.xml*
-
-[source,xml]
-------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-hipchat</artifactId>
- <version>${camel-version}</version>
-</dependency>
-------------------------------------------
-
-where `$\{camel-version}` must be replaced by the actual version of Camel.
-
-include::camel-spring-boot::page$hipchat-starter.adoc[]