Hi Aki

There was one similar issue reported with 2.4, but was confirmed to be
fixed in 2.4.1.
We thought the issue was to do with one of the writers not doing
flush/close or similar...

On Thu, Aug 11, 2011 at 9:38 PM, Aki Yoshida <[email protected]> wrote:
> Hi Andi,
> I have had some problem with building your project using mvn, as your
> project has dependency to many components and I don't seem to be able
> to resolve a few of them. I will try to build it differently sometime.
>
> Regarding what you described, this is for the outbound response
> processing chain, right?
> And the problem is only occurring for the log output from the log
> interceptor and not for the actual response/fault messages that get
> serialized over the wire? And if you don't use the transform feature,
> you do not observe this logging problem?

The other question is whether it happens on the client or server side...

Thanks, Sergey

>
> regards, aki
>
>
> 2011/8/8 akuhtz <[email protected]>:
>> Hi Aki, Hi Sergey,
>>
>> I've found another problem with the StaxTransformFeature in combination with
>> the LoggingOutInterceptor.
>>
>> The setup is the same as in the project attached to
>> http://cxf.547215.n5.nabble.com/Problem-with-new-transform-feature-td4599185.html.
>>
>> 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.
>>
>> Currently I don't know what to use a base for a testcase from the CXF trunk
>> ...
>> I've attached the updated demo project. You can enable/disabled the
>> transformFeature in applicationContext.xml to see the output in the logfile.
>>
>> Regards,
>> Andi
>>
>> http://cxf.547215.n5.nabble.com/file/n4678061/cxf-transform-sample.zip
>> cxf-transform-sample.zip
>>
>> --
>> View this message in context: 
>> http://cxf.547215.n5.nabble.com/LoggingOutInterceptor-shows-wrong-or-no-payload-if-StaxTransformFeature-is-active-tp4678061p4678061.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>

Reply via email to