Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 20 Jun 2011 19:56:47 +0000 (UTC)
From: "Brendan Long (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <338567504.22293.1308599807713.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1144612190.22292.1308599807685.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-4126) S3Producer does not use
 CamelAwsS3ContentLength or CamelAwsS3ContentType
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brendan Long updated CAMEL-4126:
--------------------------------

    Component/s:     (was: camel-atom)
                 camel-aws

> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-4126
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4126
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.8.0
>            Reporter: Brendan Long
>            Priority: Minor
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length or content type, and we get warnings like this:
> WARN  AmazonS3Client - No content length specified for stream data.  Stream contents will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic binary.
> Since there are already Camel headers for this, I'm proposing that they be used when sending messages to S3. I can write a patch for this if it would help.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira