Client Proxy methods returning void eagerly close body even in error conditions

@Produces(JSON)
@PUT
void storeSomething(Something value);

    public static <X extends WebApplicationException> X summarize(final X wae) {
        wae.addSuppressed(new BodySummary(wae.getResponse()));
        throw wae;
    }

    @SuppressWarnings("PMD.DoNotExtendJavaLangThrowable")
    static class BodySummary extends Throwable {
        private static final long serialVersionUID = 1L;

        BodySummary(final Response response) {
            super("Failing body is: " + abbreviate(response));
        }

        private static String abbreviate(final Response response) {
            if (response instanceof BuiltResponse && ((BuiltResponse) response).isClosed()) {
                return "<closed>";
            }
            return StringUtils.abbreviate(response.readEntity(String.class), 5120);
        }
    }

   public static final EntityExtractor createVoidExtractor()
   {
      return new EntityExtractor()
      {
         public Object extractEntity(ClientContext context, Object... args)
         {
            ClientResponse response = context.getClientResponse();
            int status = response.getStatus();
            if (status >= 400)
            {
               response.bufferEntity();
               response.close();
               ClientInvocation.handleErrorStatus(response);
            }
            response.close();
            return null;
         }
      };
   }

Buffering the message entity data allows for multiple invocations of readEntity(...) methods on the response instance. Note however, that once the response instance itself is closed, the implementations are expected to release the buffered message entity data too. Therefore any subsequent attempts to read a message entity stream on such closed response will result in an IllegalStateException being thrown.