You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andreas Kuhtz (JIRA)" <ji...@apache.org> on 2011/08/16 09:36:27 UTC
[jira] [Created] (CXF-3744) LoggingOutInterceptor shows wrong or no
payload if StaxTransformFeature is active
LoggingOutInterceptor shows wrong or no payload if StaxTransformFeature is active
---------------------------------------------------------------------------------
Key: CXF-3744
URL: https://issues.apache.org/jira/browse/CXF-3744
Project: CXF
Issue Type: Bug
Affects Versions: 2.4.2
Reporter: Andreas Kuhtz
If the transform feature is configured the SoapMessage is not logged correct. In case of a SoapFault no payload is logged. If a valid response is logged only the content of the SoapBody is logged but not the whole Envelope.
The corresponding thread in the mailing list: http://cxf.547215.n5.nabble.com/LoggingOutInterceptor-shows-wrong-or-no-payload-if-StaxTransformFeature-is-active-td4678061.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-3744) LoggingOutInterceptor shows wrong or
no payload if StaxTransformFeature is active
Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aki Yoshida reassigned CXF-3744:
--------------------------------
Assignee: Aki Yoshida
> LoggingOutInterceptor shows wrong or no payload if StaxTransformFeature is active
> ---------------------------------------------------------------------------------
>
> Key: CXF-3744
> URL: https://issues.apache.org/jira/browse/CXF-3744
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.4.2
> Reporter: Andreas Kuhtz
> Assignee: Aki Yoshida
>
> If the transform feature is configured the SoapMessage is not logged correct. In case of a SoapFault no payload is logged. If a valid response is logged only the content of the SoapBody is logged but not the whole Envelope.
> The corresponding thread in the mailing list: http://cxf.547215.n5.nabble.com/LoggingOutInterceptor-shows-wrong-or-no-payload-if-StaxTransformFeature-is-active-td4678061.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3744) LoggingOutInterceptor shows wrong or
no payload if StaxTransformFeature is active
Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aki Yoshida resolved CXF-3744.
------------------------------
Resolution: Fixed
Fix Version/s: 2.5
2.4.3
added the fault checking (i.e., getContent(Exception.class)) to skip the transformation if the fault was already raised.
> LoggingOutInterceptor shows wrong or no payload if StaxTransformFeature is active
> ---------------------------------------------------------------------------------
>
> Key: CXF-3744
> URL: https://issues.apache.org/jira/browse/CXF-3744
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.4.2
> Reporter: Andreas Kuhtz
> Assignee: Aki Yoshida
> Fix For: 2.4.3, 2.5
>
>
> If the transform feature is configured the SoapMessage is not logged correct. In case of a SoapFault no payload is logged. If a valid response is logged only the content of the SoapBody is logged but not the whole Envelope.
> The corresponding thread in the mailing list: http://cxf.547215.n5.nabble.com/LoggingOutInterceptor-shows-wrong-or-no-payload-if-StaxTransformFeature-is-active-td4678061.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3744) LoggingOutInterceptor shows wrong or
no payload if StaxTransformFeature is active
Posted by "Aki Yoshida (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aki Yoshida resolved CXF-3744.
------------------------------
Resolution: Fixed
fixed the position of the TransformOutInterceptor.
> LoggingOutInterceptor shows wrong or no payload if StaxTransformFeature is active
> ---------------------------------------------------------------------------------
>
> Key: CXF-3744
> URL: https://issues.apache.org/jira/browse/CXF-3744
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.4.2
> Reporter: Andreas Kuhtz
> Assignee: Aki Yoshida
> Fix For: 2.4.3, 2.5
>
>
> If the transform feature is configured the SoapMessage is not logged correct. In case of a SoapFault no payload is logged. If a valid response is logged only the content of the SoapBody is logged but not the whole Envelope.
> The corresponding thread in the mailing list: http://cxf.547215.n5.nabble.com/LoggingOutInterceptor-shows-wrong-or-no-payload-if-StaxTransformFeature-is-active-td4678061.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (CXF-3744) LoggingOutInterceptor shows wrong or
no payload if StaxTransformFeature is active
Posted by "Andreas Kuhtz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Kuhtz reopened CXF-3744:
--------------------------------
One problem still exists.
If the transformFeature is enabled (applicationContext.xml: line 67) and the Test transformedCallTest is executed, the following output is traced (note the payload! ... and the missing Encoding):
{code}
12:55:25.030 INFO [qtp19725666-15][org.apache.cxf.interceptor.LoggingOutInterceptor] - Outbound Message
---------------------------
ID: 2
Content-Type: text/xml
Headers: {}
Payload: <TransformTestResponse xmlns="http://cxf.apache.org/transform/test" xmlns:ns2="http://cxf.apache.org/transform/header" xmlns:ns3="http://cxf.apache.org/transform/header/element" xmlns:ns4="http://cxf.apache.org/transform/fault"><Status>LOOPBACK</Status></TransformTestResponse>
--------------------------------------
{code}
whereas the following is logged if the feature is disabled:
{code}
13:01:32.381 INFO [qtp19725666-14][org.apache.cxf.interceptor.LoggingOutInterceptor] - Outbound Message
---------------------------
ID: 2
Encoding: UTF-8
Content-Type: text/xml
Headers: {}
Payload: <?xml version='1.0' encoding='UTF-8'?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><ns2:SoapHeaderOut xmlns:ns4="http://cxf.apache.org/transform/fault" xmlns:ns3="http://cxf.apache.org/transform/header/element" xmlns:ns2="http://cxf.apache.org/transform/header" xmlns="http://cxf.apache.org/transform/test"><ns2:OperationalMode>SIMULATION1</ns2:OperationalMode><ns2:SomeCorrelationId>test-123</ns2:SomeCorrelationId></ns2:SoapHeaderOut></soap:Header><soap:Body><TransformTestResponse xmlns:ns4="http://cxf.apache.org/transform/fault" xmlns:ns3="http://cxf.apache.org/transform/header/element" xmlns:ns2="http://cxf.apache.org/transform/header" xmlns="http://cxf.apache.org/transform/test"><Status>LOOPBACK</Status></TransformTestResponse></soap:Body></soap:Envelope>
--------------------------------------
{code}
Unfortunately I don't know how to track this in a unit testcase.
> LoggingOutInterceptor shows wrong or no payload if StaxTransformFeature is active
> ---------------------------------------------------------------------------------
>
> Key: CXF-3744
> URL: https://issues.apache.org/jira/browse/CXF-3744
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.4.2
> Reporter: Andreas Kuhtz
> Assignee: Aki Yoshida
> Fix For: 2.4.3, 2.5
>
>
> If the transform feature is configured the SoapMessage is not logged correct. In case of a SoapFault no payload is logged. If a valid response is logged only the content of the SoapBody is logged but not the whole Envelope.
> The corresponding thread in the mailing list: http://cxf.547215.n5.nabble.com/LoggingOutInterceptor-shows-wrong-or-no-payload-if-StaxTransformFeature-is-active-td4678061.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira