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: Log empty message (with HTTP status code only)

Sergey, thank you. But how could I log the fact of 202 response? Segery Maslov On Tue, Dec 29, 2015 at 11:55 PM, Sergey Beryozkin wrote: > I think it might be because 202 is handled by a oneway processor and the > outbound chain is not invoked though I might be wrong... >

Re: Log empty message (with HTTP status code only)

I think it might be because 202 is handled by a oneway processor and the outbound chain is not invoked though I might be wrong... Sergey On 29/12/15 11:17, Sergey Maslov wrote: The issue is reproduced for with 202 - Accepted http status. On Tue, Dec 29, 2015 at 1:28 PM, Sergey Maslov

Re: Log empty message (with HTTP status code only)

I'm not sure right now, perhaps Aki or Dan may have an idea. May be you can register a custom Log interceptor, after LoggingInInterceptor, that will check CXF message if it is one way (there has to be some property set in the message) and log only if it is oneway... Cheers, Sergey On

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

async problem ; Illegal State Exception

I switched some code of mine to use AsyncRequest, and I get some scary backtraces even though everything seems to be working just fine. Note the presence of org.jolokia.osgi.security.BasicAuthenticationHttpContext.handleSecurity in the backtrace. Now, I am running in Karaf with the jolokia

Re: async problem ; Illegal State Exception

Removing jolokia made this disappear, so I don't think it belongs here, however odd it is that it only appeared with the use of CXF async. On Tue, Dec 29, 2015 at 2:38 PM, Benson Margulies wrote: > I switched some code of mine to use AsyncRequest, and I get some scary >

Problem starting CXF API bundle in Eclipse Virgo

Hi all, When deploying & starting CXF DOSGI bundles in Eclipse Virgo I notice the following exception in the logs: /[2015-12-29 13:31:09.326] ERROR Blueprint Extender: 3 org.apache.aries.blueprint.container.BlueprintContainerImpl Unable to start blueprint container for bundle

Re: Log empty message (with HTTP status code only)

The issue is reproduced for with 202 - Accepted http status. On Tue, Dec 29, 2015 at 1:28 PM, Sergey Maslov wrote: > Hi! > I need to log imcoming requests with corresponsing responses. > According > I add custom LoggingFeature and implement LogEventSender interface. >

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 =