> + public ListenableFuture<BlobMetadata> blobMetadata(String container,
> String key) {
> + return async.getBlobMetadata(container, key);
> + }
> +
> + @Override
> + protected boolean deleteAndVerifyContainerGone(String container) {
> + async.deleteContainer(container);
> + try {
> + return !containerExists(container).get();
> + } catch (InterruptedException e) {
> + LOGGER.warn("deleteAndVerifyContainerGone operation execution
> fail", e);
> + return true;
> + } catch (ExecutionException e) {
> + LOGGER.warn("deleteAndVerifyContainerGone operation execution
> fail", e);
> + return true;
> + }
In these situations we usually propagate the exception in a RuntimeException
using Guava's `throw Throwables.propagate(ex);`. It is not ideal, but IMO it is
better to propagate the exception than to return back potentially wrong
information.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/188/files#r7184112
