camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From acosent...@apache.org
Subject [2/4] camel git commit: Added camel-google-drive docs to gitbook
Date Sat, 02 Apr 2016 12:02:47 GMT
Added camel-google-drive docs to gitbook


Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/39b0bbf4
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/39b0bbf4
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/39b0bbf4

Branch: refs/heads/master
Commit: 39b0bbf4bc5c7802476fbcfe8aa12e7233c4ae4e
Parents: 7df0e26
Author: Andrea Cosentino <ancosen@gmail.com>
Authored: Sat Apr 2 12:26:31 2016 +0200
Committer: Andrea Cosentino <ancosen@gmail.com>
Committed: Sat Apr 2 12:26:31 2016 +0200

----------------------------------------------------------------------
 .../src/main/docs/google-drive.adoc             | 157 +++++++++++++++++++
 docs/user-manual/en/SUMMARY.md                  |   1 +
 2 files changed, 158 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/camel/blob/39b0bbf4/components/camel-google-drive/src/main/docs/google-drive.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-drive/src/main/docs/google-drive.adoc b/components/camel-google-drive/src/main/docs/google-drive.adoc
new file mode 100644
index 0000000..4955c1d
--- /dev/null
+++ b/components/camel-google-drive/src/main/docs/google-drive.adoc
@@ -0,0 +1,157 @@
+[[GoogleDrive-GoogleDriveComponent]]
+GoogleDrive Component
+~~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.14*
+
+The Google Drive component provides access to the
+http://drive.google.com[Google Drive file storage service] via the
+https://developers.google.com/drive/v2/reference[Google Drive Web APIs].
+
+Google Drive uses
+the https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
+protocol] for authenticating a Google account and authorizing access to
+user data. Before you can use this component, you will need to
+https://developers.google.com/drive/web/auth/web-server[create an
+account and generate OAuth credentials]. Credentials comprise of a
+clientId, clientSecret, and a refreshToken. A handy resource for
+generating a long-lived refreshToken is the
+https://developers.google.com/oauthplayground[OAuth playground].
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+-------------------------------------------------------
+    <dependency>
+            <groupId>org.apache.camel</groupId>
+            <artifactId>camel-google-drive</artifactId>
+            <version>2.14-SNAPSHOT</version>
+    </dependency>
+        
+-------------------------------------------------------
+
+[[GoogleDrive-URIFormat]]
+URI Format
+^^^^^^^^^^
+
+'''''
+
+The GoogleDrive Component uses the following URI format:
+
+---------------------------------------------------------
+        google-drive://endpoint-prefix/endpoint?[options]
+    
+---------------------------------------------------------
+
+Endpoint prefix can be one of:
+
+* drive-about
+* drive-apps
+* drive-changes
+* drive-channels
+* drive-children
+* drive-comments
+* drive-files
+* drive-parents
+* drive-permissions
+* drive-properties
+* drive-realtime
+* drive-replies
+* drive-revisions
+
+[[GoogleDrive-GoogleDriveComponent.1]]
+GoogleDriveComponent
+^^^^^^^^^^^^^^^^^^^^
+
+
+// component options: START
+The Google Drive component supports 2 options which are listed below.
+
+
+
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| configuration | GoogleDriveConfiguration | To use the shared configuration
+| clientFactory | GoogleDriveClientFactory | To use the GoogleCalendarClientFactory as factory
for creating the client. Will by default use BatchGoogleDriveClientFactory
+|=======================================================================
+// component options: END
+
+
+
+
+// endpoint options: START
+The Google Drive component supports 14 endpoint options which are listed below:
+
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| apiName | common |  | GoogleDriveApiName | *Required* What kind of operation to perform
+| methodName | common |  | String | *Required* What sub operation to use for the selected
operation
+| accessToken | common |  | String | OAuth 2 access token. This typically expires after an
hour so refreshToken is recommended for long term usage.
+| applicationName | common |  | String | Google drive application name. Example would be
camel-google-drive/1.0
+| clientFactory | common |  | GoogleDriveClientFactory | To use the GoogleCalendarClientFactory
as factory for creating the client. Will by default use BatchGoogleDriveClientFactory
+| clientId | common |  | String | Client ID of the drive application
+| clientSecret | common |  | String | Client secret of the drive application
+| inBody | common |  | String | Sets the name of a parameter to be passed in the exchange
In Body
+| refreshToken | common |  | String | OAuth 2 refresh token. Using this the Google Calendar
component can obtain a new accessToken whenever the current one expires - a necessity if the
application is long-lived.
+| scopes | common |  | List | Specifies the level of permissions you want a drive application
to have to a user account. See https://developers.google.com/drive/web/scopes for more info.
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the
Camel routing Error Handler which mean any exceptions occurred while the consumer is trying
to pickup incoming messages or the likes will now be processed as a message and handled by
the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler
to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) |  | ExceptionHandler | To let the consumer use
a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options
is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR
level and ignored.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern
when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be
strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+// endpoint options: END
+
+
+[[GoogleDrive-ProducerEndpoints]]
+Producer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Producer endpoints can use endpoint prefixes followed by endpoint names
+and associated options described next. A shorthand alias can be used for
+some endpoints. The endpoint URI MUST contain a prefix.
+
+Endpoint options that are not mandatory are denoted by []. When there
+are no mandatory options for an endpoint, one of the set of [] options
+MUST be provided. Producer endpoints can also use a special option
+*`inBody`* that in turn should contain the name of the endpoint option
+whose value will be contained in the Camel Exchange In message.
+
+Any of the endpoint options can be provided in either the endpoint URI,
+or dynamically in a message header. The message header name must be of
+the format `CamelGoogleDrive.<option>`. Note that the `inBody` option
+overrides message header, i.e. the endpoint option `inBody=option` would
+override a `CamelGoogleDrive.option` header.
+
+For more information on the endpoints and options see API documentation
+at: https://developers.google.com/drive/v2/reference/[https://developers.google.com/drive/v2/reference/]
+
+[[GoogleDrive-ConsumerEndpoints]]
+Consumer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Any of the producer endpoints can be used as a consumer endpoint.
+Consumer endpoints can use
+http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
+Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
+invocation. Consumer endpoints that return an array or collection will
+generate one exchange per element, and their routes will be executed
+once for each exchange.
+
+[[GoogleDrive-MessageHeaders]]
+Message Headers
+^^^^^^^^^^^^^^^
+
+Any URI option can be provided in a message header for producer
+endpoints with a `CamelGoogleDrive.` prefix.
+
+[[GoogleDrive-MessageBody]]
+Message Body
+^^^^^^^^^^^^
+
+All result message bodies utilize objects provided by the underlying
+APIs used by the GoogleDriveComponent. Producer endpoints can specify
+the option name for incoming message body in the `inBody` endpoint URI
+parameter. For endpoints that return an array or collection, a consumer
+endpoint will map every element to distinct messages.     

http://git-wip-us.apache.org/repos/asf/camel/blob/39b0bbf4/docs/user-manual/en/SUMMARY.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index 0b04436..935baa1 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -137,6 +137,7 @@
     * [Git](git.adoc)
     * [Github](github.adoc)
     * [Google Calendar](google-calendar.adoc)
+    * [Google Drive](google-drive.adoc)
     * [Ironmq](ironmq.adoc)
     * [JMS](jms.adoc)
     * [JMX](jmx.adoc)


Mime
View raw message