The stack trace is unfamiliar, but otherwise this sounds a bit like what I experienced and reported about here:
http://restlet.tigris.org/ds/viewMessage.do?dsMessageId=2702864&dsForumId=4447 <http://restlet.tigris.org/ds/viewMessage.do?dsMessageId=2702864&dsForumId=4447>Maybe toggling AUTO_CLOSE_TARGET will help you. If not, try overriding WriterRepresentation.write(OutputStream) as I describe. Or it could be something else entirely... --tim On Tue, Apr 19, 2011 at 5:32 PM, Brian Anderson <b...@nwlink.com> wrote: > I have an Android client that is roughly equivalent to the serialization > example (First Application). > > Using 2.0.6 or 2.1M3 the Android client works fine using Java serialization > as the representation. > > I modified the Android client to explicitly register the Jackson converter > so that I can retrieve the Contact using a JSON representation from the > server. This also works fine using 2.0.6. (I am using Jackson 1.7.1.) > > Unfortunately, this does not work using 2.1M3. The Android client appears > to properly retrieve the JSON representation from the server but hangs > trying to convert the JSON representation into a Contact. > > I've enclosed a stack trace obtained from the Eclipse debugger attached to > the Android AVD illustrating the context of the failure. Not sure, but this > looks like it might be associated with the new NIO stuff. > > Note that this does seem to work when the client is a plain old JSE > edition. Of course I don't have to explicitly register the Jackson > converter here. > > Cheers, > > Brian > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2721560 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2721778
