jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-438) Map S3 code BucketAlreadyExists
Date Wed, 29 Jan 2014 05:24:09 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885019#comment-13885019
] 

ASF subversion and git services commented on JCLOUDS-438:
---------------------------------------------------------

Commit b8fae85eaf26618731591c6ea47892a906133510 in branch refs/heads/1.7.x from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=b8fae85 ]

JCLOUDS-438: Map S3 code BucketAlreadyExists

Mapping to ResourceAlreadyExistsException allows external callers to
handle this situation specifically.


> Map S3 code BucketAlreadyExists
> -------------------------------
>
>                 Key: JCLOUDS-438
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-438
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.0
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>            Priority: Minor
>             Fix For: 1.7.1
>
>
> Presently jclouds throws IllegalStateException when creating a bucket name owned by another
user.  Instead we could raise a more specific exception, e.g. ResourceAlreadyExistsException.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message