a:334)
>> at org.mortbay.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:169)
>> at
>> org.mortbay.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:2
>> 21) at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:721) ...
>> 32
>> more
>>
>> We use simple frontend for our web services. Attachments are supposed to
>> be
>> loaded as a response from web-method, which is java-first designed method
>> returning DataHandler object with AttachmentDataSource in it.
>>
>> Need some ideas. Are we doing something wrong or it is a bug in CXF and
>> MTOM attachments simply does not work with gzip compression?
>>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://www.dankulp.com/blog
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-GZIP-and-mtom-attachments-tp25472988p25488134.html
Sent from the cxf-user mailing list archive at Nabble.com.
It SOUNDS like a bug, probably an interceptor ordering issue. Is there any
way you could create a small test case and log a bug?
Dan
On Wed September 16 2009 9:59:12 am Виталий Литвак wrote:
> Hi.
>
> We were using CXF 2.0.10 in our application and now decided to use GZIP
> compression for
Hi.
We were using CXF 2.0.10 in our application and now decided to use GZIP
compression for messages. So we've upgraded to CXF 2.2.3. After solving some
migration problems we are finally available to use all our stuff without
GZIP compression. But if we turn it on (by adding GZIPFeature to
ServerF
