自定义消息在泽西岛找不到正文阅读器测试

Question

我的球衣测试课有一个奇怪的问题。

当执行我的测试代码并在org.glassfish.jersey.message.internal.ReaderInterceptorExecutor的第203行放置断点时，我看到我的阅读器不在reader.workers.但是，正如您在下面看到的，我在ResourceConfig中注册了这个MessageBodyReader。

所有相关代码如下所示。

@Provider
@Produces({V1_JSON})
@Consumes({V1_JSON})
public class JsonMessageBodyHandlerV1
    implements
      MessageBodyWriter<Object>,
      MessageBodyReader<Object> {
  ...
}

是的，可读的返回为真。

调试时，我看到代码点击了writeTo，但没有点击readFrom。

public class TestLocationResource extends JerseyTest {

  public static class LocationResourceHK2Binder extends AbstractBinder {

    @Override
    protected void configure() {
      // Singleton bindings.
      bindAsContract(LocationDao.class).in(Singleton.class);

      // Singleton instance bindings.
      bind(new FakeLocationDao()).to(LocationDao.class);
    }
  }

  @Test
  public void basicTest() {

    LocationListV1 actualResponse = /**/
    /**/target(LocationResourceV1.PathFields.PATH_ROOT)
    /*   */.path(LocationResourceV1.PathFields.SUBPATH_LIST)
    /*   */.request(V1_JSON)
    /*   */.header(HEADER_API_KEY, "abcdefg")
    /*   */.get(LocationListV1.class);

    assertEquals(10, actualResponse.getLocations().size());
  }

  @Override
  protected Application configure() {
    enable(TestProperties.LOG_TRAFFIC);
    enable(TestProperties.DUMP_ENTITY);

    ResourceConfig rc = new ResourceConfig();
    rc.registerClasses(LocationResourceV1.class, JsonMessageBodyHandlerV1.class);
    rc.register(new LocationResourceHK2Binder());

    return rc;
  }
}

（从这个例子中得出。）

public class LocationResourceV1 implements ILocationResourceV1 {
  ...

  @Inject
  private LocationDao daoLoc;

  private final LocationTranslator translator = new LocationTranslator();

  @Override
  public LocationListV1 listV1(String apiKey) {
    return translator.translate(daoLoc.query(LocationFilters.SELECT_ALL));
  }

  ...

  @VisibleForTesting
  public void setLocationDao(LocationDao dao) {
    this.daoLoc = dao;
  }
}

（请注意，Web 服务注释（如@GET）位于接口中。

org . glassfish . jersey . message . internal . messagebodyprovidernotfoundexception:找不到MessageBodyReader for media type = application/vnd . com . company-v1 JSON，type = class com . company . rest . v1 . resources . location . JSON . location listv1 . at org . glassfish . jersey . message . internal . readerinterceptorexecutor＄termineralreaderinterceptor . around readfrom(readerinterceptorexexe...]

[...]
INFO: [HttpServer] Started.
Oct 29, 2013 4:26:16 PM org.glassfish.jersey.filter.LoggingFilter log
INFO: 1 * LoggingFilter - Request received on thread main
1 > GET http://localhost:9998/location/list
1 > Accept: application/vnd.com.company-v1+json
1 > X-ApiKey: abcdefg

Oct 29, 2013 3:30:21 PM org.glassfish.jersey.internal.Errors logErrors
WARNING: The following warnings have been detected: WARNING: HK2 service reification failed for [com.company.persistence.dao.intf.LocationDao] with an exception:
MultiException stack 1 of 2
java.lang.NoSuchMethodException: Could not find a suitable constructor in com.company.persistence.dao.intf.LocationDao class.
    at org.glassfish.jersey.internal.inject.JerseyClassAnalyzer.getConstructor(JerseyClassAnalyzer.java:189)
    at org.jvnet.hk2.internal.Utilities.getConstructor(Utilities.java:159)
    at org.jvnet.hk2.internal.ClazzCreator.initialize(ClazzCreator.java:125)
    at org.jvnet.hk2.internal.ClazzCreator.initialize(ClazzCreator.java:176)
    at org.jvnet.hk2.internal.SystemDescriptor.internalReify(SystemDescriptor.java:649)
    at org.jvnet.hk2.internal.SystemDescriptor.reify(SystemDescriptor.java:604)
    at org.jvnet.hk2.internal.ServiceLocatorImpl.reifyDescriptor(ServiceLocatorImpl.java:396)
    [...]
MultiException stack 2 of 2
java.lang.IllegalArgumentException: Errors were discovered while reifying SystemDescriptor(
    implementation=com.company.persistence.dao.intf.LocationDao
    contracts={com.company.persistence.dao.intf.LocationDao}
    scope=org.glassfish.jersey.process.internal.RequestScoped
    qualifiers={}
    descriptorType=CLASS
    descriptorVisibility=NORMAL
    metadata=
    rank=0
    loader=org.glassfish.hk2.utilities.binding.AbstractBinder$2@568bf3ec
    proxiable=null
    proxyForSameScope=null
    analysisName=null
    id=143
    locatorId=0
    identityHashCode=2117810007
    reified=false)
    at org.jvnet.hk2.internal.SystemDescriptor.reify(SystemDescriptor.java:615)
    at org.jvnet.hk2.internal.ServiceLocatorImpl.reifyDescriptor(ServiceLocatorImpl.java:396)
    at org.jvnet.hk2.internal.ServiceLocatorImpl.narrow(ServiceLocatorImpl.java:1916)
    at org.jvnet.hk2.internal.ServiceLocatorImpl.access$700(ServiceLocatorImpl.java:113)
    at org.jvnet.hk2.internal.ServiceLocatorImpl$6.compute(ServiceLocatorImpl.java:993)
    at org.jvnet.hk2.internal.ServiceLocatorImpl$6.compute(ServiceLocatorImpl.java:988)
    [...]
    [...]
    (Above is repeated 4 times)
    [...]
    [...]

Oct 29, 2013 3:30:22 PM org.glassfish.jersey.filter.LoggingFilter log
INFO: 2 * LoggingFilter - Response received on thread main
2 < 200
2 < Date: Tue, 29 Oct 2013 22:30:21 GMT
2 < Content-Length: 16
2 < Content-Type: application/vnd.com.company-v1+json
{"locations":[]}

Oct 29, 2013 3:30:22 PM org.glassfish.jersey.test.grizzly.GrizzlyTestContainerFactory$GrizzlyTestContainer stop
INFO: Stopping GrizzlyTestContainer...
Oct 29, 2013 3:30:22 PM org.glassfish.grizzly.http.server.NetworkListener stop
INFO: Stopped listener bound to [localhost:9998]

有人知道我做错了什么吗？

Answer 1

第一个堆栈跟踪来自您的客户端，因为您没有在那里注册消息正文提供程序（因此找不到它）。泽西测试#配置方法应该仅用于配置服务器端。还有另一种名为“泽西测试#配置客户端”的方法，用于客户端。如果要使用自定义提供程序，则需要重写这两种方法。

第二个堆栈跟踪来自您的< code > locationresourcehk 2 binder 。经过

bindAsContract(LocationDao.class).in(Singleton.class);

您告诉HK2，LocationDao类应该实例化为单例，然后HK2将其注入LocationDaotypes。您可能希望更改活页夹以使用以下内容：

bind(new FakeLocationDao()).to(LocationDao.class);

有关此主题的详细信息，请参阅自定义注入和生命周期管理。