cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-5391) Response code is not logged for SOAP responses
Date Wed, 20 Nov 2013 18:34:35 GMT


Aki Yoshida commented on CXF-5391:

Hi Sergey,
But this 204 is jaxrs specific and i suppose you are already setting it within the jaxrs part,
HTTPDest has the logic of using the status code if it is already set in the message or if
not, choose between 200 and 202 based on several factors such as whether the call was oneway,
empty-partial-resp, partial reap, etc to get the right status code for jaxws stuff with or
without ws-* extensions. So I suppose, we can use the same logic of setting either 200 or
202 for LocalDest only when the code is not set.

In anyway, I'll create a new ticket to track this topic and link it from here.

regards, aki

> Response code is not logged for SOAP responses
> ----------------------------------------------
>                 Key: CXF-5391
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.7
>            Reporter: Mandy Warren
>            Assignee: Aki Yoshida
>            Priority: Minor
>             Fix For: 3.0.0-milestone1, 2.7.8, 2.6.11
> If you enable logging through the LoggingIn/OutInterceptors and then send a SOAP request
through, the response code is not logged.
> ---------------------------
> ID: 2
> Encoding: UTF-8
> Content-Type: text/xml
> The response code is logged fine for rest requests:
> ---------------------------
> ID: 19
> Response-Code: 200
> Content-Type: application/xml

This message was sent by Atlassian JIRA

View raw message