Re: Playing with readEntity(String.class)

The problem was the server response. A server should not return a string, even if correctly encoded, because a string is not a valid JSON object. http://stackoverflow.com/questions/18419428/what-is-the-minimum-valid-json On Wed, Dec 30, 2015 at 12:06 PM, Sergey Beryozkin

Re: Playing with readEntity(String.class)

Hi This is to do with a default CXF JSONProvider which is Jettison based. Jettison, historically, escapes forward slashes, I don't know why, it was there when I started maintaining it. What you can do is to configure CXF JSONProvider not to do it, set its 'escapeForwardSlashesAlways' to

Re: Playing with readEntity(String.class)

Thanks Sergey, but in the meanwhile I tried fruitless different options which include escapeForwardSlashesAlways(false). I have also tried to change entirely the implementation, but even Jersey have the same behaviour. This is pretty strange to me. On Tue, Dec 29, 2015 at 7:10 PM, Sergey

Playing with readEntity(String.class)

Hi All, I don't understand why when I receive a json encoded string this is not decoded automatically. I wrote this code: Client client = ClientBuilder.newClient().register(JSONProvider.class); WebTarget target = client.target("http://example.org/rest/service1;); target =