Return-Path: 
 <issues-return-21338-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 87851108E3
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Thu, 15 Jan 2015 00:53:33 +0000 (UTC)
Received: (qmail 58288 invoked by uid 500); 15 Jan 2015 00:53:35 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 58251 invoked by uid 500); 15 Jan 2015 00:53:35 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 58240 invoked by uid 99); 15 Jan 2015 00:53:35 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jan 2015 00:53:35 +0000
Date: Thu, 15 Jan 2015 00:53:34 +0000 (UTC)
From: "Chris Pimlott (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12767614.1421282927000.87584.1421283214682@Atlassian.JIRA>
In-Reply-To: <JIRA.12767614.1421282927000@Atlassian.JIRA>
References: <JIRA.12767614.1421282927000@Atlassian.JIRA>
 <JIRA.12767614.1421282927499@arcas>
Subject: [jira] [Updated] (CAMEL-8246) ZipAggregationStrategy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Chris Pimlott updated CAMEL-8246:
---------------------------------
    Description: 
ZipAggregationStrategy does not preserve any headers from the aggregated exchanges.  This makes it difficult to do something like name the output zip file based on the correlation key:

{code:xml}
    <from uri="direct:input"/>
    <aggregate strategyRef="zipStrategy" eagerCheckCompletion="true">
      <correlationExpression>
        <simple>${header[batchId]}</simple>
      </correlationExpression>
      <completionSize>
        <simple>${header[batchSize]}</simple>
      </completionSize>
      <setHeader headerName="CamelFileName">
        <simple>batch-${header[batchId]}.zip</simple>
      </setHeader>
      <to uri="direct:output"/>
    </aggregate>
{code}

This behavior is inconsistent with other existing AggregationStrategies, including AggregationStrategyBeanAdapter, FlexibleAggregationStrategy, UseLatestAggregationStrategy, and UseOriginalAggregationStrategy, which all use the first exchange received (or a copy of it) to initialize the aggregated exchange, hence preserving headers and properties, including those which may used to determine the correlation of related exchanges.
 

  was:
ZipAggregationStrategy does not preserve any headers from the aggregated exchanges.  This makes it difficult to do something like name the output zip file based on the correlation key:

{code:xml}
    <from uri="direct:input"/>
    <aggregate strategyRef="zipStrategy" eagerCheckCompletion="true">
      <correlationExpression>
        <simple>${header[batchId]}</simple>
      </correlationExpression>
      <completionSize>
        <simple>${header[batchSize]}</simple>
      </completionSize>
      <setHeader headerName="CamelFileName">
        <simple>batch-${header[batchId]}.zip</simple>
      </setHeader>
      <to uri="direct:output"/>
    </aggregate>
{code}

This behavior is inconsistent with other existing AggregationStrategies, including AggregationStrategyBeanAdapter, FlexibleAggregationStrategy, UseLatestAggregationStrategy, and UseOriginalAggregationStrategy, which all use a complete copy of the first exchange received when initializing the aggregated exchange.

 


> ZipAggregationStrategy
> ----------------------
>
>                 Key: CAMEL-8246
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8246
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.14.0
>            Reporter: Chris Pimlott
>              Labels: aggregate, zip
>
> ZipAggregationStrategy does not preserve any headers from the aggregated exchanges.  This makes it difficult to do something like name the output zip file based on the correlation key:
> {code:xml}
>     <from uri="direct:input"/>
>     <aggregate strategyRef="zipStrategy" eagerCheckCompletion="true">
>       <correlationExpression>
>         <simple>${header[batchId]}</simple>
>       </correlationExpression>
>       <completionSize>
>         <simple>${header[batchSize]}</simple>
>       </completionSize>
>       <setHeader headerName="CamelFileName">
>         <simple>batch-${header[batchId]}.zip</simple>
>       </setHeader>
>       <to uri="direct:output"/>
>     </aggregate>
> {code}
> This behavior is inconsistent with other existing AggregationStrategies, including AggregationStrategyBeanAdapter, FlexibleAggregationStrategy, UseLatestAggregationStrategy, and UseOriginalAggregationStrategy, which all use the first exchange received (or a copy of it) to initialize the aggregated exchange, hence preserving headers and properties, including those which may used to determine the correlation of related exchanges.
>  



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