>> As can be seen from the discussion below, >> interceptors can be injected by specifying them in web.xml, if one is >> not using Spring for setup. Today I tried out CXF 2.7.0 and I now got >> a ClassNotFoundException: (snip( >> >> As can be seen, the classname that was looked up was split over three >> lines, so this means that somehow, this logic has changed
Found the problem by looking at the code revisions for CXFNonSpringJaxrsServlet (https://fisheye6.atlassian.com/browse/cxf/branches/2.4.x-fixes/rt/frontend/jaxrs/src/main/java/org/apache/cxf/jaxrs/servlet/CXFNonSpringJaxrsServlet.java?r2=1366746&r1=1359097) Turns out that the default parameter splitting character changed July 18 from using a default of " " (space) to "," (comma). This broke the configuration. By specifying class.parameter.split.char one can decide which character should do the splitting. The following would need to be added in order not to change the former configuration: <init-param> <param-name>class.parameter.split.char</param-name> <param-value> </param-value> </init-param> <init-param> Using comma is fine anyhow, so using that from now on. regards Carl-Erik
