Hi Sebastian,
I think I ran into the same issue like you have been described initially.
Switching to 2.1 Snapshot (2011-06-01) solved this issue for me.
Regarding you second issue - my code looks slightly different and provides
valid json representation back. Maybe this works for you as well.
Actually I'm not creating the JSONRepresentation by myself but just provide
pure Java Objects back. The JSON-serialization is then handled by restlet
itself. I'm using the Jackson-extension.
Code looks similar to:
@Get
public MyResponseClass get(){
myResponseClass response = new MyREsponseClass();
// some fany but unimportant stuff here ...
setStatus(Status.SUCCESS_OK);
return response;
}
If I call with accept=application/json, I get a Json response like expected.
Maybe that helps?
Cheers,
Stefan
On Tue, Jun 7, 2011 at 4:05 PM, Sebastian Wenninger <
[email protected]> wrote:
> I don't want to seem impatient, but this is a crucial part of my bachelor's
> thesis, so i don't have that much time to solve it.
> At least, can somebody else confirm that JsonRepresentations don't work
> properly so i can exclude an error for my part?
>
> Thanks,
> Sebastian
>
> --
> View this message in context:
> http://restlet-discuss.1400322.n2.nabble.com/IncompatibleClassChangeError-with-ConcurrentMap-tp6393712p6449749.html
> Sent from the Restlet Discuss mailing list archive at Nabble.com.
>
> ------------------------------------------------------
>
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2759594
>
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2759609
