Restlet Client不能很好地與澤西島服務溝通

我想爲我的澤西島服務實現一個restlet客戶端。我知道這個服務很有效，因爲我已經爲它開發了一個球衣客戶端。但是，球衣和休息似乎會出現相互溝通的問題。Restlet Client不能很好地與澤西島服務溝通

澤西服務

的ressource：

@Path("/object") 
@RolesAllowed({"admin", "user"}) 
public class ObjectResourceBean implements ObjectResourceIF { 
     @POST 
     @Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON}) 
     public Response postObject(JAXBElement<ObjectDTO> object) { 
      ObjectDTO c = object.getValue(); 
      String generatedId = generateID(); 
      c.setObjectId(generatedId); 
      c.setOwner(sec.getUserPrincipal().getName()); 
      return postAndGetResponse(c); 
     } 

     private Response postAndGetResponse(ObjectDTO object) { 
      Response res; 

       res = Response.created(UriBuilder.fromUri(uriInfo.getAbsolutePath() + "/" + object.getObjectId()).build()).entity(object).build(); 
       ObjectDAO.instance.getObjectDao().put(object.getObjectId(), object); 

       System.out.println("Response: " + res); 
      } 
      return res; 
     }

的Restlet裹接口：

@Path("/object") 
    @RolesAllowed({"admin", "user"}) 
    public interface ObjectResourceIF { 
     @Post 
     public Response postObject(JAXBElement<ObjectDTO> object); 
}

已經在這裏我不能新澤西註解像@POST工作。我必須使用Restlet框架中的@Post。但那不是真正的問題。

的Restlet客戶

ClientResource service = new ClientResource("http://localhost:8080/com-project-core/rest"); 
service.setChallengeResponse(ChallengeScheme.HTTP_BASIC, "admin", "xxx"); 
service.getReference().addSegment("object"); 
// *create object* 
JAXBElement<ObjectDTO> object = new JAXBElement<ObjectDTO>(new QName("object"), ObjectDTO.class, objectOne); 
    ObjectResourceIF objectResource = service.wrap(ObjectResourceIF.class); 

    List<Preference<MediaType>> acceptedMediaTypes = new ArrayList<Preference<MediaType>>(); 
    acceptedMediaTypes.add(new Preference(MediaType.APPLICATION_JSON)); 
    service.getClientInfo().setAcceptedMediaTypes(acceptedMediaTypes); 

    Response res = objectResource.postObject(object);

我只是得到一個內部服務器錯誤（500）。

Internal Server Error (500) - The server encountered an unexpected condition which prevented it from fulfilling the request 
    at org.restlet.resource.UniformResource.toObject(UniformResource.java:649) 
    at org.restlet.resource.ClientResource$1.invoke(ClientResource.java:1669) 
    at $Proxy12.postObject(Unknown Source) 
    at com.project.restlet.RestletConnectedTest.postObject(RestletConnectedTest.java:108) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
    at java.lang.reflect.Method.invoke(Method.java:597) 
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) 
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) 
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) 
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) 
    at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) 
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) 
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) 
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) 
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) 
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) 
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) 
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) 
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) 
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236) 
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) 
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) 
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) 
    Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: objectId : objectId 
    at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:86) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:96) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38) 
    at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:52) 
    at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29) 
    at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:136) 
    at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33) 
    at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:923) 
    at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:909) 
    at com.thoughtworks.xstream.XStream.fromXML(XStream.java:861) 
    at org.restlet.ext.xstream.XstreamRepresentation.getObject(XstreamRepresentation.java:166) 
    at org.restlet.ext.xstream.XstreamConverter.toObject(XstreamConverter.java:200) 
    at org.restlet.service.ConverterService.toObject(ConverterService.java:161) 
    at org.restlet.resource.UniformResource.toObject(UniformResource.java:647) 
    ... 27 more

在服務器端的請求被做

return res;

當我嘗試沒有與

service.post(object, MediaType.APPLICATION_JSON).write(System.out);

它的工作原理包裹界面！

正如我所說的，澤西客戶端也是如此。

也許轉移類ObjectDTO是解決方案有用：

@XmlRootElement 
    @XmlAccessorType(XmlAccessType.FIELD) 
    public class ObjectDTO implements Serializable{ 

     /** 
     * 
     */ 
     private static final long serialVersionUID = -8545841080597549468L; 

     @XmlElement(name="objectId") 
     private String objectId; 
     @XmlElement(name="owner") 
     private String owner; 
     @XmlElement(name="objectName") 
     private String objectName; 

     public ObjectDTO() { 

     } 

     public ObjectDTO(String objectName) { 
      this.objectName = objectName; 
     } 

     public String getObjectId() { 
      return objectId; 
     } 

     public void setObjectId(String objectId) { 
      this.objectId = objectId; 
     } 

     public String getOwner() { 
      return owner; 
     } 

     public void setOwner(String owner) { 
      this.owner = owner; 
     } 
}

我試了一下沒有序列化也是如此。也沒有@XmlElement和@XmlAccessorType（XmlAccessType.FIELD）。我也試過

@Consumes({MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON})

註解在界面上。

來源

2012-07-09 Robin Wieruch

我們對Jersey服務器和Restlet客戶端有同樣的問題，但有一個get請求。通過Restlet客戶端與Restlet服務器通信，我們沒有問題。所以我們可以看到的唯一區別是，Restlet服務器實現將編組POJO的完整限定類名作爲JSON對象包裝在包含POJO負載的JSON對象周圍。的Restlet服務器上

package com.xyz; 

    public class ExamplePojo implements Serializable{ 

     private static final long serialVersionUID = 1L; 

     private String var; 

     public ExamplePojo(){ 

     } 
    //... 
    }

生成的JSON字符串：在它的默認實現

{"com.xyz.ExamplePojo":{"var":"10:23:53 30.10.2012"}}

但新澤西服務器，如果生產MediaType.APPLICATION_JSON沒有。新澤西服務器上生成的JSON字符串：

{"var":"10:23:53 30.10.2012"}

的問題是，如果我們試圖用通過的Restlet客戶端澤西服務器的通信，我們與根源您的堆棧跟蹤有像同樣的錯誤：

Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: var : var

我們的情況是，我們必須明確地定義JacksonConverter，如果Restlet客戶端使用Jersey服務器實現。

所以我們把從的Restlet拉鍊庫我們的客戶端項目的構建路徑

org.restlet.ext.jackson.jar  
org.codehaus.jackson.core.jar   
org.codehaus.jackson.mapper.jar

（資源的接口）

public interface PojoResource { 
    @Get("json") 
    public ExamplePojo retrieve(); 
}

，然後我們的JacksonConverter增加明確的註冊轉換器

public ExamplePojo doRequest(){ 
    ClientResource cr = new ClientResource(url); 
    // this is essential for Restlet-Jersey marshalling 
    Engine.getInstance().getRegisteredConverters().add(0, new JacksonConverter()); 
    PojoResource resource = cr.wrap(PojoResource.class); 
    return resource.retrieve(); 
}

和一切工作正常。

注意，顯式調用

Engine.getInstance().getRegisteredConverters().add(0, new JacksonConverter());

在Reslet客戶端來的Restlet服務器的通信沒有工作，但導致了

org.codehaus.jackson.map.JsonMappingException

因爲包裝JSON對象「的COM .xyz.ExamplePojo'作爲無法識別的字段，必須標記爲可忽略。

因此，在你的情況下，似乎Restlet沒有找到一個解組的轉換器，所以嘗試指定一個明確的。

來源

2012-10-30 11:56:43 elb

'{com.xyz.ExamplePojo {「var」：「10:23:53 30.10.2012」}}'不是有效的JSON。 – 2012-10-30 12:00:11

thx爲提示{「com.xyz.ExamplePojo」：{「var」：「10:23:53 30.10.2012」}}，現在它的有效 – elb 2012-10-30 12:38:27

Restlet Client不能很好地與澤西島服務溝通

回答

相關問題