Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5E9EE18A65 for ; Tue, 1 Dec 2015 17:20:46 +0000 (UTC) Received: (qmail 19329 invoked by uid 500); 1 Dec 2015 17:20:46 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 19283 invoked by uid 500); 1 Dec 2015 17:20:46 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 19274 invoked by uid 99); 1 Dec 2015 17:20:46 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2015 17:20:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 838E4180965 for ; Tue, 1 Dec 2015 17:20:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.247 X-Spam-Level: * X-Spam-Status: No, score=1.247 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 45-O7AR4TK2r for ; Tue, 1 Dec 2015 17:20:29 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id D70BA21628 for ; Tue, 1 Dec 2015 17:20:28 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 64CA4E0682 for ; Tue, 1 Dec 2015 17:20:28 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 266AA3A05A2 for ; Tue, 1 Dec 2015 17:20:28 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r974176 [2/2] - in /websites/production/camel/content: amqp.html book-component-appendix.html book-in-one-page.html cache/main.pageCache camel-2170-release.html Date: Tue, 01 Dec 2015 17:20:27 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20151201172028.266AA3A05A2@svn01-us-west.apache.org> Modified: websites/production/camel/content/book-in-one-page.html ============================================================================== --- websites/production/camel/content/book-in-one-page.html (original) +++ websites/production/camel/content/book-in-one-page.html Tue Dec 1 17:20:27 2015 @@ -3719,11 +3719,11 @@ The tutorial has been designed in two pa While not actual tutorials you might find working through the source of the various Examples useful.

Tutorial on Spring Remoting with JMS

 

Thanks

This tutorial was kindly donated to Apache Camel by Martin Gilday.

Preface

This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a Spring service. The route works in a synchronous fashion returning a response to the client.

+/*]]>*/

See Also

-
Unable to render {include} The included page could not be found.

AMQP

Available as of Camel X.X

The amqp: component supports the AMQP protocol using the JMS Client API of the Qpid project. In case you want to use AMQP with RabbitMQ you might also be interested in the Camel RabbitMQ component.

Maven users will need to add the following dependency to their pom.xml for this co mponent:

+
Unable to render {include} The included page could not be found.

AMQP

The amqp: component supports the AMQP 1.0 protocol using the JMS Client API of the Qpid project. In case you want to use AMQP 0.9 (in particular RabbitMQ) you might also be interested in the Camel RabbitMQ component. Please keep in mind that prior to the Cam el 2.17.0 AMQP component supported AMQP 0.9 and above, however since Camel 2.17.0 it supports only AMQP 1.0.

Maven users will need to add the following dependency to their pom.xml for this component:

-

AMQP Options

You can specify all of the various configuration options of the JMS component after the destination name.

Using topics

To have using topics working with camel-amqp you need to configure the component to use "topic://" as topic prefix, as shown below:

- +

Using topics

To have using topics working with camel-amqp you need to configure the component to use topic:// as topic prefix, as shown below:

+ + </bean>]]>

 

Starting from the Camel 2.16.1 you can also use the AMQPComponent#amqp10Component(String connectionURI) factory method to return the AMQP 1.0 component with the pre-configured topic prefix: 

Creating AMQP 1.0 component
+

Keep in mind that starting from the Camel 2.17 the AMQPComponent#amqp10Component(String connectionURI) factory method has been deprecated on the behalf of the AMQPComponent#amqpComponent(String connectionURI)

Creating AMQP 1.0 component
+

 

 

See Also

SQS Component

Available as of Camel 2.6

The sqs component supports sending and receiving messages to Amazon's SQS service.

Prerequisites

You must have a valid Amazon Web Services developer account, and be signed up to use Amazon SQS. More information are available at Amazon SQS.

URI Format

-

The queue will be created if they don't already exists.
You can append query options to the URI in the following format, ?options=value&option2=value&...

URI Options

Name

Default Value

Context

Description

amazonSQSClient

null

Shared

Reference to a com.amazonaws.services.sqs.AmazonSQS in the Registry.< /p>

accessKey

null

Shared

Amazon AWS Access Key

secretKey

null

Shared

Amazon AWS Secret Key

amazonSQSEndpoint

null

Shared

The region with which the AWS-SQS client wants to work with. Only works if Camel creates the AWS-SQS client, i.e., if you explicitly set amazonSQSClient, then this setting will have no effect. You would have to set it on the client you create directly

attributeNames

null

Consumer

A list of attributes to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest.

concurrentConsumers1Consumer(as of 2.15.0) Allows you to use multiple threads to poll the sqs queue to increase throughput

defaultVis ibilityTimeout

null

Shared

The visibility timeout (in seconds) to set in the com.amazonaws.services.sqs.model.CreateQueueRequest.

deleteAfterRead

true

Consumer

Delete message from SQS after it has been read (and processed by the route)

deleteIfFiltered

true

Consumer

Camel 2.12.2,2.13.0 Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage.

maxMessagesPerPoll

null

Consumer

The maximum number of messages which can be received in one poll to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest.

visibilityTimeout

null

Shared

The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently.

messageVisibilityTimeout

null

Consumer

Camel 2.8: The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest. It does NOT change the queue visibility tim eout attribute permanently.

extendMessageVisibility

false

Consumer

Camel 2.10: If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it taks a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs.

maximumMessageSize

null

Shared

Camel 2.8: The maximumMessageSize (in bytes) an SQS message can contain for this queue, to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest.

messageRetentionPeriod

null

Shared

Camel 2.8: The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue, to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest.

policy

null

Shar ed

Camel 2.8: The policy for this queue to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest.

delaySeconds

null

Producer

Camel 2.9.3: Delay sending messages for a number of seconds.

waitTimeSeconds

0

Producer

Camel 2.11: Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response.

receiveMessageWaitTimeSeconds

0

Shared

Camel 2.11: If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait.

queueOwnerAWSAccountId

null

Shared

Camel 2.12: Specify the queue owner aws account id when you need to connect the queue with different account owner.

region

null

Shared

Camel 2.12.3: Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL.

redrivePolicy

nullSharedCamel 2.15: Specify the policy that send message to DeadLetter queue. See detail at Amazon docs.

proxyHost

nullSharedCamel 2.16: Specify a proxy host to be used inside the client definition.

proxyPort

nullSharedCamel 2.16: Specify a proxy port to be used inside the client definition.

Required SQS component options

You have to provide the amazonSQSClient in the Registry or your accessKey and secretKey to access the Amazon's SQS.

Batch Consumer

This component implements the Batch Consumer.

This allows you for instance to know how many messages exists in this batch and for instance let the Aggregator aggregate this number of messages.

Usage

Message headers set by the SQS producer

Header

Type

Description

CamelAwsSqsMD5OfBody

String

The MD5 checksum of the Amazon SQS message.

CamelAwsSqsMessageId

String

The Amazon SQS message ID.

CamelAwsSqsDelaySeconds

Integer

Since Camel 2.11, the delay seconds that the Amazon SQS message can be see by others.

Message headers set by the SQS consume r

Header

Type

Description

CamelAwsSqsMD5OfBody

String

The MD5 checksum of the Amazon SQS message.

CamelAwsSqsMessageId

String

The Amazon SQS message ID.

CamelAwsSqsReceiptHandle

String

The Amazon SQS message receipt handle.

CamelAwsSqsAttributes

Map<String, String>

The Amazon SQS message attributes.

Advanced AmazonSQS configuration

If your Camel Application is running behind a firewall or if you need to have more control over the AmazonSQS instance configuration, you can create your own instance:

+

The queue will be created if they don't already exists.
You can append query options to the URI in the following format, ?options=value&option2=value&...

URI Options

Name

Default Value

Context

Description

amazonSQSClient

null

Shared

Reference to a com.amazonaws.services.sqs.AmazonSQS in the Registry.< /p>

accessKey

null

Shared

Amazon AWS Access Key

secretKey

null

Shared

Amazon AWS Secret Key

amazonSQSEndpoint

null

Shared

The region with which the AWS-SQS client wants to work with. Only works if Camel creates the AWS-SQS client, i.e., if you explicitly set amazonSQSClient, then this setting will have no effect. You would have to set it on the client you create directly

attributeNames

null

Consumer

A list of attributes to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest.

concurrentConsumers1Consumer(as of 2.15.0) Allows you to use multiple threads to poll the sqs queue to increase throughput

defaultVis ibilityTimeout

null

Shared

The visibility timeout (in seconds) to set in the com.amazonaws.services.sqs.model.CreateQueueRequest.

deleteAfterRead

true

Consumer

Delete message from SQS after it has been read (and processed by the route)

deleteIfFiltered

true

Consumer

Camel 2.12.2,2.13.0 Whether or not to send the DeleteMessage to the SQS queue if an exchange fails to get through a filter. If 'false' and exchange does not make it through a Camel filter upstream in the route, then don't send DeleteMessage.

maxMessagesPerPoll

null

Consumer

The maximum number of messages which can be received in one poll to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest.

visibilityTimeout

null

Shared

The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest. This only make sense if its different from defaultVisibilityTimeout. It changes the queue visibility timeout attribute permanently.

messageVisibilityTimeout

null

Consumer

Camel 2.8: The duration (in seconds) that the received messages are hidden from subsequent retrieve requests after being retrieved by a ReceiveMessage request to set in the com.amazonaws.services.sqs.model.ReceiveMessageRequest. It does NOT change the queue visibility tim eout attribute permanently.

extendMessageVisibility

false

Consumer

Camel 2.10: If enabled then a scheduled background task will keep extending the message visibility on SQS. This is needed if it taks a long time to process the message. If set to true defaultVisibilityTimeout must be set. See details at Amazon docs.

maximumMessageSize

null

Shared

Camel 2.8: The maximumMessageSize (in bytes) an SQS message can contain for this queue, to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest.

messageRetentionPeriod

null

Shared

Camel 2.8: The messageRetentionPeriod (in seconds) a message will be retained by SQS for this queue, to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest.

policy

null

Shar ed

Camel 2.8: The policy for this queue to set in the com.amazonaws.services.sqs.model.SetQueueAttributesRequest.

delaySeconds

null

Producer

Camel 2.9.3: Delay sending messages for a number of seconds.

waitTimeSeconds

0

Producer

Camel 2.11: Duration in seconds (0 to 20) that the ReceiveMessage action call will wait until a message is in the queue to include in the response.

receiveMessageWaitTimeSeconds

0

Shared

Camel 2.11: If you do not specify WaitTimeSeconds in the request, the queue attribute ReceiveMessageWaitTimeSeconds is used to determine how long to wait.

queueOwnerAWSAccountId

null

Shared

Camel 2.12: Specify the queue owner aws account id when you need to connect the queue with different account owner.

region

null

Shared

Camel 2.12.3: Specify the queue region which could be used with queueOwnerAWSAccountId to build the service URL.

redrivePolicy

nullSharedCamel 2.15: Specify the policy that send message to DeadLetter queue. See detail at Amazon docs.

proxyHost

nullSharedCamel 2.16: Specify a proxy host to be used inside the client definition.

proxyPort

nullSharedCamel 2.16: Specify a proxy port to be used inside the client definition.

Required SQS component options

You have to provide the amazonSQSClient in the Registry or your accessKey and secretKey to access the Amazon's SQS.

Batch Consumer

This component implements the Batch Consumer.

This allows you for instance to know how many messages exists in this batch and for instance let the Aggregator aggregate this number of messages.

Usage

Message headers set by the SQS producer

Header

Type

Description

CamelAwsSqsMD5OfBody

String

The MD5 checksum of the Amazon SQS message.

CamelAwsSqsMessageId

String

The Amazon SQS message ID.

CamelAwsSqsDelaySeconds

Integer

Since Camel 2.11, the delay seconds that the Amazon SQS message can be see by others.

Message headers set by the SQS consume r

Header

Type

Description

CamelAwsSqsMD5OfBody

String

The MD5 checksum of the Amazon SQS message.

CamelAwsSqsMessageId

String

The Amazon SQS message ID.

CamelAwsSqsReceiptHandle

String

The Amazon SQS message receipt handle.

CamelAwsSqsAttributes

Map<String, String>

The Amazon SQS message attributes.

Advanced AmazonSQS configuration

If your Camel Application is running behind a firewall or if you need to have more control over the AmazonSQS instance configuration, you can create your own instance:

See Also

CXF Component

When using CXF as a consumer, the CXF Bean Component allows you to factor out how message payloads are received from their processing as a RESTful or SOAP web service. This has the potential of using a multitude of transports to consume web services. The bean component's configuration is also simpler and provides the fastest method to implement web services using Camel and CXF.

When using CXF in streaming modes (see DataFormat option), then also read about Stream caching.

The cxf: component provides integration with Apache CXF for connecting to JAX-WS services hosted in CXF.

+/*]]>*/

  • CXF Component
    • URI format
    • Options
      • The descriptions of the dataformats @@ -19137,7 +19147,7 @@ The result of the operation will contain

        Option

        Default

        Description

        definition

        null

        The flatpack pzmap configuration file. Can be omitted in simpler situations, but its preferred to use the pzmap.

        fixed

        false

        Delimited or fixed.

        ignoreFirstRecord

        true

        Whether the first line is ignored for delimited files (for the column headers).

        textQualifier

        "

        If the text is qualified with a char such as ".

        delimiter

        ,

        The delimiter char (could be ; , or similar)

        parserFactory

        null

        Uses the default Flatpack parser factory.

        allowShortLines

        false

        Camel 2.9.7 and 2.10.5 onwards: Allows for lines to be shorter than expected and ignores the extra characters.

        ignoreExtraColumns

        false

        Camel 2.9.7 and 2.10.5 onwards: Allows for lines to be longer than expected and ignores the extra characters.

        -

        Usage

        +

        Usage

        To use the data format, simply instantiate an instance and invoke the marshal or unmarshal operation in the route builder:

        -

        Consumer added

        From Camel 2.10 onwards you can use consumer as an EventListener in JCR or a producer to read a node by identifier.

        Usage

        The repository element of the URI is used to look up the JCR Repository object in the Camel context registry.

        Producer

        Name

        Default Value

        Description

        CamelJcrOperation

        CamelJcrInsert

        CamelJcrInsert or CamelJcrGetById operation to use

        CamelJcrNodeName

        null

        Used to determine the node name to use.

        CamelJcrNodeTypenullCamel 2.16: To use a specify primary node type when creating adding a new node.

        When a message is sent to a JCR producer endpoint:

        • If the operation is CamelJcrInsert: A new node is created in the content repository, all the message headers of the IN message are transformed to javax.jcr.Value instances and added to the new node and the node's UUID is returned in the OUT message.
        • If the operation is CamelJcrGetById: A new node is retrieved from the repository using the message body as node identifier.

        Please note that the JCR Producer used message properties instead of message headers in Camel versions earlier than 2.12.3. See https://issues.apache.org/jira/browse/CAMEL-7067 f or more details.

         

        Consumer

        The consumer will connect to JCR periodically and return a List<javax.jcr.observation.Event> in the message body.

        Name

        Default Value

        Description

        eventTypes

        0

        A combination of one or more event types encoded as a bit mask value such as javax.jcr.observation. Event.NODE_ADDED, javax.jcr.observation.Event.NODE_REMOVED, etc.

        deep

        false

        When it is true, events whose associated parent node is at current path or within its subgraph are received.

        uuids

        null

        Only events whose associated parent node has one of the identifiers in the comma separated uuid list will be received.

        nodeTypeNames

        null

        Only events whose associated parent node has one of the node types (or a subtype of one of the node types) in this list will be received.

        noLocal

        false

        If noLocal is true, then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored.

        sessionLiveCheckInterval

        60000

        Interval in milliseconds to wait before each session live checking.

        sessionLiveCheckIntervalOnStart

        3000

        Interval in milliseconds to wait before the first session live checking.

        username

         

        Camel 2.15: Allows to specify the username as a uri parameter instead of in the authority section of the uri

        password

         

        Camel 2.15: Allows to specify the password as a uri parameter instead of in the authority section of the uri

        workspaceName

        null

        Camel 2.16: Allows to specify a workspace different from default

        Example

        The snippet below creates a node named node under the /home/test node in the content repository. One additional property is added to the node as well: my.contents.property which will contain the body of the message being sent.

        +

        Consumer added

        From Camel 2.10 onwards you can use consumer as an EventListener in JCR or a producer to read a node by identifier.

        Usage

        The repository element of the URI is used to look up the JCR Repository object in the Camel context registry.

        Producer

        Name

        Default Value

        Description

        CamelJcrOperation

        CamelJcrInsert

        CamelJcrInsert or CamelJcrGetById operation to use

        CamelJcrNodeName

        null

        Used to determine the node name to use.

        CamelJcrNodeTypenullCamel 2.16: To use a specify primary node type when creating adding a new node.

        When a message is sent to a JCR producer endpoint:

        • If the operation is CamelJcrInsert: A new node is created in the content repository, all the message headers of the IN message are transformed to javax.jcr.Value instances and added to the new node and the node's UUID is returned in the OUT message.
        • If the operation is CamelJcrGetById: A new node is retrieved from the repository using the message body as node identifier.

        Please note that the JCR Producer used message properties instead of message headers in Camel versions earlier than 2.12.3. See https://issues.apache.org/jira/browse/CAMEL-7067 f or more details.

         

        Consumer

        The consumer will connect to JCR periodically and return a List<javax.jcr.observation.Event> in the message body.

        Name

        Default Value

        Description

        eventTypes

        0

        A combination of one or more event types encoded as a bit mask value such as javax.jcr.observation. Event.NODE_ADDED, javax.jcr.observation.Event.NODE_REMOVED, etc.

        deep

        false

        When it is true, events whose associated parent node is at current path or within its subgraph are received.

        uuids

        null

        Only events whose associated parent node has one of the identifiers in the comma separated uuid list will be received.

        nodeTypeNames

        null

        Only events whose associated parent node has one of the node types (or a subtype of one of the node types) in this list will be received.

        noLocal

        false

        If noLocal is true, then events generated by the session through which the listener was registered are ignored. Otherwise, they are not ignored.

        sessionLiveCheckInterval

        60000

        Interval in milliseconds to wait before each session live checking.

        sessionLiveCheckIntervalOnStart

        3000

        Interval in milliseconds to wait before the first session live checking.

        username

         

        Camel 2.15: Allows to specify the username as a uri parameter instead of in the authority section of the uri

        password

         

        Camel 2.15: Allows to specify the password as a uri parameter instead of in the authority section of the uri

        workspaceName

        null

        Camel 2.16: Allows to specify a workspace different from default

        Example

        The snippet below creates a node named node under the /home/test node in the content repository. One additional property is added to the node as well: my.contents.property which will contain the body of the message being sent.

        @@ -21449,7 +21459,7 @@ from("direct:hello")

        URI format

        [... 42 lines stripped ...] Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/camel-2170-release.html ============================================================================== --- websites/production/camel/content/camel-2170-release.html (original) +++ websites/production/camel/content/camel-2170-release.html Tue Dec 1 17:20:27 2015 @@ -85,7 +85,7 @@ -

        Camel 2.17.0 release (currently in progress)

         

        New and Noteworthy

        Welcome to the x.y.z release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

        • highlighted issue fixed
        • Upgraded camel-hbase to Hadoop 2.x and HBase 1.1.x
        • Camel commands for Spring Boot
        • Many improvements to Camel 0;Kura
        • Added transacted option to SQL Component when used as a consumer in a transacted route.
        • Added support for UPDATE operation to ElasticSearch.
        • Allow to reuse existing configured Elasticsearch Client on the ElasticSearch component, instead of creating a client per endpoint. 
        • The include and exclude options on File2 and FTP endpoints is now case in-sensitive out of the box.
        • Resource based component such as XSLTVelocity etc can load the resource file from the Registry by using ref: as prefix.

         

        Fixed these issues

        • The Swagger Java now parses nested types in the POJO model that has been annotated with the swagger api annotations to use in the schema api model
        • Fixed Rest DSL with apiContextPath fail to start if there are 2 ore more rest's in use.
        • Paho component name is not limited to 4 characters anymore.
        • Fixed Spring Boot not starting Camel routes if running in Spring Cloud.

        New Enterprise Integration Patterns

        New Components

        • camel-kubernetes - Integrates Camel with Kubernetes

        New DSL

        New Annotations

        New Data Formats

        New Languages

        New Examples

        • camel-example-spring-boot-metrics - showing a Camel spring-boot application that report metrics to Graphite. Requires Graphite running on your network.

        New Tutorials

        API breaking

        Known Issues

        Dependency upgrades

        • Spring 4.1.x to 4.2.x
        • Spring-Boot 1.2.x to 1.3.x
        • EHCache from 2.10.0 to 2.10.1
        • slf 4j-api 1.6.x to 1.7.x

        Important changes to consider when upgrading

        • Removed camel-hbase as Karaf feature as it did not really work well in OSGi
        • camel-infinispan requires Java 8.
        • Support for Spring 4.0.x is deprecated.
        • Moved some Camel tooling related dependencies (such as maven/plexus) from the Camel Parent BOM to the tooling BOM (to have them separated).

        Getting the Distributions

        Binary Distributions

        Description

        Download Link

        PGP Signature file of download

        Windows Distribution

        apache-camel-x.y.x.zip

        apache-camel-x.y.x.zip.asc

        Unix/Linux/Cygwin Distribution

        apache-camel-x.y.x.tar.gz

        apache-camel-x.y.x.tar.gz.asc

        The above URLs use redirection

        The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox

        Source Distributions

        Description

        Download Link

        < /th>

        PGP Signature file of download

        Source for Windows

        apache-camel-x.y.x-src.zip

        apache-camel-x.y.x-src.zip.asc

        Getting the Binaries using Maven 2

        To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:

        +

        Camel 2.17.0 release (currently in progress)

         

        New and Noteworthy

        Welcome to the x.y.z release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

        • highlighted issue fixed
        • Upgraded camel-hbase to Hadoop 2.x and HBase 1.1.x
        • Camel commands for Spring Boot
        • Many improvements to Camel 0;Kura
        • Added transacted option to SQL Component when used as a consumer in a transacted route.
        • Added support for UPDATE operation to ElasticSearch.
        • Allow to reuse existing configured Elasticsearch Client on the ElasticSearch component, instead of creating a client per endpoint. 
        • The include and exclude options on File2 and FTP endpoints is now case in-sensitive out of the box.
        • Resource based component such as XSLTVelocity etc can load the resource file from the Registry by using ref: as prefix.
        • Upgraded camel-amqp to the latest qpid-jms-client (also AMQP < 1.0 is not supported anymore).

         

        Fixed these issues

        • The Swagger Java now parses nested types in the POJO model that has been annotated with the swagger api annotations to use in the schema api model
        • Fixed Rest DSL with apiContextPath fail to start if there are 2 ore more rest's in use.
        • Paho component name is not limited to 4 characters anymore.
        • Fixed Spring Boot not starting Camel routes if running in Spring Cloud.

        New Enterprise Integration Patterns

        New Components

        • camel-kubernetes - Integrates Camel with Kubernetes

        New DSL

        New Annotations

        New Data Formats

        New Languages

        New Examples

        • camel-example-spring-boot-metrics - showing a Camel spring-boot application that report metrics to Graphite. Requires Graphite running on your network.

        New Tutorials

        API breaking

        Known Issues

        Dependency upgrades< /h2>
        • Spring 4.1.x to 4.2.x
        • Spring-Boot 1.2.x to 1.3.x
        • EHCache from 2.10.0 to 2.10.1
        • slf4j-api 1.6.x to 1.7.x

        Important changes to consider when upgrading

        • Removed camel-hbase as Karaf feature as it did not really work well in OSGi
        • camel-infinispan requires Java 8.
        • Support for Spring 4.0.x is deprecated.
        • Moved some Camel tooling related dependencies (such as maven/plexus) from the Camel Parent BOM to the tooling BOM (to have them separated).

        Getting the Distributions

        Binary Distributions

        Description

        Download Link

        PGP Signature file of download

        Windows Distribution

        apache-camel-x.y.x.zip

        apache-camel-x.y.x.zip.asc

        Unix/Linux/Cygwin Distribution

        apache-camel-x.y.x.tar.gz

        apache-camel-x.y.x.tar.gz.asc

        The above URLs use redirection

        The above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox

        Source Distributions

        Description

        Download Link

        PGP Signature file of download

        Source for Windows

        apache-camel-x.y.x-src.zip

        apache-camel-x.y.x-src.zip.asc

        Getting the Binaries using Maven 2

        To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is:

        -

        Changelog

        For a more detailed view of new features and bug fixes, see the:


        +

        Changelog

        For a more detailed view of new features and bug fixes, see the: