[
https://issues.apache.org/jira/browse/CXF-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827616#comment-13827616
]
Sergey Beryozkin commented on CXF-5391:
---------------------------------------
Hi Aki, my understanding is that Local Transport is used to test WS & RS
endpoints, so the higher-level info like headers, etc may be handy to display,
example, Content-Type is HTTP header.
Note, in the JAX-RS case, the response code is set before the transport is even
invoked, in JAXRSOutInterceptor, before LoggingOutInterceptor is invoked so we
see the response code on the JAX-RS out path. Not sure though if it is possible
to set up the response code earlier on the WS out path
Cheers, Sergey
> Response code is not logged for SOAP responses
> ----------------------------------------------
>
> Key: CXF-5391
> URL: https://issues.apache.org/jira/browse/CXF-5391
> 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
(v6.1#6144)
