It sounds good, normally we can pass the ACL through the header or set the default value through the endpoint configuration. Please fill a JIRA and submit a patch to it, so we can keep it traced.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: willemjiang On Thursday, November 8, 2012 at 8:04 AM, massyl wrote: > Hi all, > i'm working with aws-s3 endpoint and facing some limitation regarding > setting Acl on new created objects. > There is no way to specify what Acl to set on those newly created objects. > for new created buckets we have the possibility to use setPolicy(String) on > S3Configuration but not for created objects. > This limitation comes from S3Producer that creates internaly > PutObjectRequest without offring a means for providing Acl to set on this > PutObjectRequest. > > What do you think about enhancing this S3Producer to accept two new headers > for example : > 1) exchange.setHeader(S3Constant.CANNED_ACL,"public-read") // to set > commonly used ACL as strings > 2) exchange.setHeader(S3Constant.ACL, new AccessControlList(...) )// to set > more specific ACL using a well constructed object > > NB: > 1) The string will be used to get the right object from > CannedAccessControlList amazon enum for example > 2) AccessControlList may be amazon's AccessControlList object or a custom > Camel object that will map to amazon one. > > Thanks in advance for your reply > > Massyl > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/aws-s3-EndPoint-and-s3-Acl-on-created-objects-tp5722324.html > Sent from the Camel Development mailing list archive at Nabble.com > (http://Nabble.com).
