It looks like the CXFNonSpringJaxrsServlet does not look for and set any interceptors.
Is this intentional? I've built a version of CXFNonSpringJaxrsServlet (from 2.2.3) that does set the out interceptors in loadBus, and that seems to work, but I have no idea about any broader possible implications... I see in 2.2.4 snapshot, it doesn't set the interceptors either. Is this the right approach? Thanks, Linus -----Message d'origine----- De : Linus Kamb [mailto:[email protected]] Envoyé : Tuesday, October 06, 2009 2:56 PM À : [email protected] Objet : RE: CXFNonSpringJaxrsServlet web.xml interceptor configuration I could add that when I run stand alone and add the interceptor programmatically, it works fine. - Linus _____ De : Linus Kamb [mailto:[email protected]] Envoyé : Tuesday, October 06, 2009 2:44 PM À : [email protected] Objet : CXFNonSpringJaxrsServlet web.xml interceptor configuration Hopefully this is an easy question, but I cant seem to figure out what I am doing wrong. I am trying to attach the GZIPOutInterceptor to a jaxrs service running under the CXFNonSpringJaxrsServlet. I have <init-param>s for the jaxrs.serviceClasses and jaxrs.providers (into which I have successfully added a Filter,) but <init-param> <param-name>jaxrs.outInterceptors</param-name> <param-value>org.apache.cxf.transport.http.gzip.GZIPOutInterceptor</param-va lue> </init-param> is not working for me. I am using CXF 2.2.3 Attached is web.xml file. Thanks, Linus
