Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 18 Nov 2016 09:27:59 +0000 (UTC)
From: "Andrea Cosentino (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13021578.1479413692000.312048.1479461279880@Atlassian.JIRA>
In-Reply-To: <JIRA.13021578.1479413692000@Atlassian.JIRA>
References: <JIRA.13021578.1479413692000@Atlassian.JIRA> <JIRA.13021578.1479413692327@arcas>
Subject: [jira] [Resolved] (CAMEL-10493) Typo in documentation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 18 Nov 2016 09:28:01 -0000


     [ https://issues.apache.org/jira/browse/CAMEL-10493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino resolved CAMEL-10493.
--------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Future)

> Typo in documentation
> ---------------------
>
>                 Key: CAMEL-10493
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10493
>             Project: Camel
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.15.3
>            Reporter: Tatyana Bardakh
>            Assignee: Andrea Cosentino
>            Priority: Trivial
>
> Splitter doc:
> Camel 2.14: If enabled then the aggregate method on AggregationStrategy can be called concurrently. Notice that this would require the implementation of AggregationStrategy to be implemented as thread-safe. By default this is false meaning that Camel synchronizes the call to the aggregate method. Though in some use-cases this can be used to {color: red}archive{color} higher performance when the AggregationStrategy is implemented as thread-safe.
> Should be: achieve


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)