I also see the same failure in 2.0.10 except that the stack trace is a bit different because of a fair bit of refactoring between 2.0 and 2.1 (e.g. in 2.0, ClientInvocationHandler in an anonymous inner class in ClientResource.
So, the question is: Is this a bug? Does my assessment of the problem seem correct? Would it be fixed by passing "actualType" instead of "actualType.getClass()"? ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2883326
