Olingo2

Required What kind of operation to perform.

Enum values:

Required What sub operation to use for the selected operation.

HTTP connection creation timeout in milliseconds, defaults to 30,000 (30 seconds).

Content-Type header value can be used to specify JSON or XML message format, defaults to application/json;charset=utf-8.

Custom entity provider read properties applied to all read operations.

Custom entity provider write properties applied to create, update, patch, batch and merge operations. For instance users can skip the Json object wrapper or enable content only mode when sending request data. A service URI set in the properties will always be overwritten by the serviceUri configuration parameter. Please consider to using the serviceUri configuration parameter instead of setting the respective write property here.

Set this to true to filter out results that have already been communicated by this component.

Custom HTTP headers to inject into every request, this could include OAuth tokens, etc.

Sets the name of a parameter to be passed in the exchange In Body.

HTTP proxy server configuration.

Target OData service base URI, e.g. http://services.odata.org/OData/OData.svc.

HTTP request timeout in milliseconds, defaults to 30,000 (30 seconds).

If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.

For endpoints that return an array or collection, a consumer endpoint will map every element to distinct messages, unless splitResult is set to false.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. 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.

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.

Sets the exchange pattern when the consumer creates an exchange.

Enum values:

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.

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 starting the producer may take a little time and prolong the total processing time of the processing.

Custom HTTP async client builder for more complex HTTP client configuration, overrides connectionTimeout, socketTimeout, proxy and sslContext. Note that a socketTimeout MUST be specified in the builder, otherwise OData requests could block indefinitely.

Custom HTTP client builder for more complex HTTP client configuration, overrides connectionTimeout, socketTimeout, proxy and sslContext. Note that a socketTimeout MUST be specified in the builder, otherwise OData requests could block indefinitely.

The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.

The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.

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.

Milliseconds before the next poll.

If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.

Milliseconds before the first poll starts.

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.

The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.

Enum values:

Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.

To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler.

To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.

Whether the scheduler should be auto started.

Time unit for initialDelay and delay options.

Enum values:

Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.

To configure security using SSLContextParameters.

Executes a batch request

Creates a new OData resource

Deletes an OData resource and invokes callback with org

Patches/merges an OData resource using HTTP MERGE

Patches/merges an OData resource using HTTP PATCH

Reads an OData resource and invokes callback with appropriate result

Updates an OData resource

Reads an OData resource and invokes callback with the unparsed input stream