代码之家  ›  专栏  ›  技术社区  ›  Mincong Huang

如何在Jersey客户端中引发定制异常?

  •  2
  • Mincong Huang  · 技术社区  · 6 年前

    我正在通过我的项目学习jersey和jax-rs 2.x “商店” . 我希望我的客户端sdk ShopException 当http响应为4xx或5xx时。这是我试过的 ClientResponseFilter 在客户端生成器中:

    target =
        ClientBuilder.newBuilder()
            .register(ShopApplication.newJacksonJsonProvider())
            .register((ClientResponseFilter) (requestCtx, responseCtx) -> {
              if (responseCtx instanceof ClientResponse) {
                ClientResponse resp = (ClientResponse) responseCtx;
                if (resp.getStatus() >= 400) {
                  ShopExceptionData data = resp.readEntity(ShopExceptionData.class);
                  throw new ShopException(resp.getStatus(), data);
                }
              }
            })
            .build()
            .target(Main.BASE_URI.resolve("products"));
    

    测试结果如下:

    @Test
    public void getProduct_invalidId() {
      try {
        target.path("123!").request(APPLICATION_JSON).get(Product.class);
        fail("GET should raise an exception");
      } catch (ShopException e) {
        assertThat(e.getData().getErrorCode()).isEqualTo(ShopError.PRODUCT_ID_INVALID.code);
        assertThat(e.getData().getErrorMessage()).isEqualTo(ShopError.PRODUCT_ID_INVALID.message);
      }
    }
    

    问题是,我的定制 购物异常 被球衣缠住裹在里面 javax.ws.rs.ProcessingException :

    javax.ws.rs.ProcessingException
        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:287)
        at org.glassfish.jersey.client.JerseyInvocation.lambda$invoke$1(JerseyInvocation.java:767)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:316)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:298)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:229)
        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:414)
        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:765)
        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:428)
        at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:324)
        at io.mincong.shop.rest.ProductResourceIT.getProduct_invalidId(ProductResourceIT.java:64)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
        at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
        at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
        at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
        at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
        at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
        at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
    Caused by: io.mincong.shop.rest.ShopException
        at io.mincong.shop.rest.ProductResourceIT.lambda$setUp$0(ProductResourceIT.java:42)
        at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:133)
        at org.glassfish.jersey.client.ClientFilteringStages$ResponseFilterStage.apply(ClientFilteringStages.java:121)
        at org.glassfish.jersey.process.internal.Stages.process(Stages.java:171)
        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:283)
        ... 33 more
    

    有办法避免吗 ProcessingException ,并确保引发的异常是 购物异常 ?

    1 回复  |  直到 6 年前
        1
  •  1
  •   Paul Samsotha    6 年前

    注:这是一个部分的答案,因为我还没有弄清楚所有的情况。


    如果你从源头上看 JerseyInvocation ,您将看到方法 invoke(Class responseType) ,这是当我们让请求传递希望反序列化响应的类参数时调用的方法。这是你在这里使用的,通过 Product.class

    target.path("123!").request(APPLICATION_JSON).get(Product.class);
    

    正在查找 invoke() 方法,我们可以看到

    return requestScope.runInScope(new Producer<T>() {
        @Override
        public T call() throws ProcessingException {
            try {
                return translate(runtime.invoke(requestForCall(requestContext)), requestScope, responseType);
            } catch (final ProcessingException ex) {
                if (ex.getCause() instanceof WebApplicationException) {
                    throw (WebApplicationException) ex.getCause();
                }
                throw ex;
            }
        }
    });
    

    这个 translate 方法是将异常包装在 ProcessingException . 如果你看后面的几行 catch ,你应该看到我们的解决方案的机会。如果异常的原因是 WebApplicationException ,则将引发该异常。所以你的解决办法是 ShopException 延伸 Web应用程序异常

    现在我说这只是一个部分的答案,因为当你只想要一个 Response 从请求中返回

    Response res = target.path("123!").request(APPLICATION_JSON).get();
    

    当你这样做的时候 invoke() (no arguments) 被称为。它不像以前那样做 调用() 方法可以。所以如果你能搞清楚,你就有了完整的解决方案。

    另一个解决方法是 处理例外 你自己再重新考虑一下原因。如果您正在制作一个sdk,那么这一切都将在用户不知情的情况下完成。