> To support it on the server side you can use a servlet filter rather than > the interceptors, but for the client side CXF needs to do the zipping and > setting of all the relevant HTTP headers itself. Before I upgraded the > interceptors to work on the server side as well as the client I used to use > http://sourceforge.net/projects/pjl-comp-filter in my web.xml. >
This part of the application is actually not inside a Servlet. Actually we are using CXF as a REST client, using some examples out there, the following code was made from a 2.0.4 version of CXF. final JaxWsProxyFactoryBean sf = new JaxWsProxyFactoryBean(); > sf.setServiceClass(this.serviceInterface); > sf.getServiceFactory().setWrapped(false); > sf.getClientFactoryBean().setBindingId(HttpBindingFactory.HTTP_BINDING_ID); > sf.setAddress(this.httpAddress); final Object object = sf.create(); > final Client client = ClientProxy.getClient(object); > So we don't have any web.xml in the classpath. Too bad this tip seemed good. Considering the modification of the input interceptor. I cannot say I will have time to work on it indefinetly as I'm staffed on other things, but if I want to implement the same intelligent mecanism used to write a gzipped stream. I have somehow planned as follows 1 - I think first should create an AbstractThresholdInputStream 2 - Optimize the GZipInInterceptor 3 - ? Well that's were I'm confused, is it possible to have some guidance. Thx a lot, Regards, On Mon, Aug 4, 2008 at 16:42, Ian Roberts <[EMAIL PROTECTED]> wrote: > Brice wrote: > >> It's mostly for the writing side of things. >>> >>> >> Ok I just get this part, while looking at the code. Indeed the >> GZipInInterceptor doesn't have a GZipThresholdOutputStream nor a >> AbstractThresholdOutputStream exists. >> I just looked a the code, well for now the code is a bit obscure. >> >> However on a different view and with my limited understanding, I really >> don't get why CXF requires to write gzip interceptors, why couldn't we >> rely >> on the transport layer wether it is jetty or commons-http. >> > > To support it on the server side you can use a servlet filter rather than > the interceptors, but for the client side CXF needs to do the zipping and > setting of all the relevant HTTP headers itself. Before I upgraded the > interceptors to work on the server side as well as the client I used to use > http://sourceforge.net/projects/pjl-comp-filter in my web.xml. > > > Ian > > -- > Ian Roberts | Department of Computer Science > [EMAIL PROTECTED] | University of Sheffield, UK > -- Bryce
