[camel] branch master updated: Fix yammer docs, as invalid utf-8 was reported in the sb auto-configuration docs

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new 201e0b4  Fix yammer docs, as invalid utf-8 was reported in the sb auto-configuration docs
201e0b4 is described below

commit 201e0b402ce4e870b7b50cc3aa037340b821ed7a
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Sat Feb 8 08:54:03 2020 +0100

    Fix yammer docs, as invalid utf-8 was reported in the sb auto-configuration docs
---
 .../src/main/docs/yammer-component.adoc            | 43 +---------------------
 1 file changed, 1 insertion(+), 42 deletions(-)

diff --git a/components/camel-yammer/src/main/docs/yammer-component.adoc b/components/camel-yammer/src/main/docs/yammer-component.adoc
index 30505f2..ec290a4 100644
--- a/components/camel-yammer/src/main/docs/yammer-component.adoc
+++ b/components/camel-yammer/src/main/docs/yammer-component.adoc
@@ -128,46 +128,6 @@ with the following path and query parameters:
 |===
 // endpoint options: END
 // spring-boot-auto-configure options: START
-== Spring Boot Auto-Configuration
-
-When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
-  <groupId>org.apache.camel.springboot</groupId>
-  <artifactId>camel-yammer-starter</artifactId>
-  <version>x.x.x</version>
-  <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-The component supports 20 options, which are listed below.
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.yammer.access-token* | The access token |  | String
-| *camel.component.yammer.basic-property-binding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | Boolean
-| *camel.component.yammer.bridge-error-handler* | 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
-| *camel.component.yammer.config.access-token* | The access token |  | String
-| *camel.component.yammer.config.consumer-key* | The consumer key |  | String
-| *camel.component.yammer.config.consumer-secret* | The consumer secret |  | String
-| *camel.component.yammer.config.delay* | Delay between polling in millis | 5000 | Long
-| *camel.component.yammer.config.function* | The function to use |  | String
-| *camel.component.yammer.config.function-type* | The function to use |  | YammerFunctionType
-| *camel.component.yammer.config.limit* | Return only the specified number of messages. Works for threaded=true and threaded=extended. | -1 | Integer
-| *camel.component.yammer.config.newer-than* | Returns messages newer than the message ID specified as a numeric string. This should be used when polling for new messages. If you're looking at messages, and the most recent message returned is 3516, you can make a request with the parameter "?newerThan=3516″ to ensure that you do not get duplicate copies of messages already on your page. | -1 | Long
-| *camel.component.yammer.config.older-than* | Returns messages older than the message ID specified as a numeric string. This is useful for paginating messages. For example, if you're currently viewing 20 messages and the oldest is number 2912, you could append "?olderThan=2912″ to your request to get the 20 messages prior to those you're seeing. | -1 | Long
-| *camel.component.yammer.config.requestor* | Set to true if you want to use raw JSON rather than converting to POJOs. |  | ApiRequestor
-| *camel.component.yammer.config.threaded* | threaded=true will only return the first message in each thread. This parameter is intended for apps which display message threads collapsed. threaded=extended will return the thread starter messages in order of most recently active as well as the two most recent messages, as they are viewed in the default view on the Yammer web interface. |  | String
-| *camel.component.yammer.config.use-json* | Set to true if you want to use raw JSON rather than converting to POJOs. | false | Boolean
-| *camel.component.yammer.config.user-id* | The user id |  | String
-| *camel.component.yammer.consumer-key* | The consumer key |  | String
-| *camel.component.yammer.consumer-secret* | The consumer secret |  | String
-| *camel.component.yammer.enabled* | Whether to enable auto configuration of the yammer component. This is enabled by default. |  | Boolean
-| *camel.component.yammer.lazy-start-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 the [...]
-|===
 // spring-boot-auto-configure options: END
 
 
@@ -379,5 +339,4 @@ from("direct:start")
     .to("mock:result");
 ----
 
-This will go out and fetch the current user's `User` object and set it as the Camel message body.
-
+This will go out and fetch the current user's `User` object and set it as the Camel message body.
\ No newline at end of file