Hi Bill, This indeed looks like a bug. I've fixed it based on your suggestion in both SVN trunk and 2.0 branch. Could you confirm it works with the next 2.1 snapshot?
Best regards, Jerome -- http://www.restlet.org http://twitter.com/#!/jlouvel -----Message d'origine----- De : Bill Claypool [mailto:[email protected]] Envoyé : lundi 21 novembre 2011 17:50 À : [email protected] Objet : RE: ClientResource.wrap with Result<> callback 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=28833 26 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2885134
