Hello, thanks for the report, I've entered an issue for this bug: http://restlet.tigris.org/issues/show_bug.cgi?id=1202.
Here are some explanations of what happens. On client side, the TestClass instance is converted into a Representation (in order to generate the request), according to the currently registered converters (I think you are using the xstream and or jackson converters). On server side, there is a content negotiation algorithm that determines the right annotated method to invoke according to the media type of the incoming entity, the media-type preferences of the client, the capabilities of the registered converters and declared annotations. On client side, at this time, there is only a competition between the converters, the first declared converter able to convert the object is called (in your case, a one able to generate a json representation). As you notice, it seems better to be more generic and let the converters (shared between the client and server code I guess) make the job. But on the other side, it seems that the current client implementation should be able also to accept the annotation's parameters. I still have a question. Do you have a reason to specify the "xml" parameter? Best regards, Thierry Boileau ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2682405
