cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5391) Response code is not logged for SOAP responses
Date Wed, 20 Nov 2013 13:55:36 GMT

    [ https://issues.apache.org/jira/browse/CXF-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827668#comment-13827668
] 

Aki Yoshida commented on CXF-5391:
----------------------------------

Hi Sergey,
if we want to get some status for LocalTRP that is analogue to the http status code, we could
set it in the LocalTRP's serialization step and that can be pulled when the LogOutInterceptor
gets executed.
that's how the sttus code inclusion for HTTP was added to the LogOutInterceptor.

But is there some meaningful status code for LocalTRP? 
assuming for the error case, someone is already setting the appropriate code, we could add
the same logic that is in the httpdestination like?
everything ok and has body -> 200
ok but empty -> 202?
regards, aki

> 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)

Mime
View raw message