Atmos Component

Table of Contents

Options
Dependencies

Available as of Camel 2.15

Camel-Gora 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 component supports 14 endpoint options which are listed below:

{% raw %}

Name	Group	Default	Java Type	Description
name	common		`String`	Atmos name
operation	common		`AtmosOperation`	Required Operation to perform
enableSslValidation	common	`false`	`boolean`	Atmos SSL validation
fullTokenId	common		`String`	Atmos client fullTokenId
localPath	common		`String`	Local path to put files
newRemotePath	common		`String`	New path on Atmos when moving files
query	common		`String`	Search query on Atmos
remotePath	common		`String`	Where to put files on Atmos
secretKey	common		`String`	Atmos shared secret
uri	common		`String`	Atomos server uri
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	consumer (advanced)		`ExchangePattern`	Sets the exchange pattern when the consumer creates an exchange.
synchronous	advanced	`false`	`boolean`	Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).

{% endraw %}

Dependencies

To use Atmos in your camel routes you need to add the dependency on camel-atmos which implements this data format.

If you use maven you could just add the following to your pom.xml, substituting the version number for the latest & greatest release (see the download page for the latest versions).

<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>