Looks like this error was coming with older version of CXF as well. So this might not be a CXF issue. Found that the exception message is not correct here. Think changing the maxHttpHeaderSize at the tomcat end might resolve this error.
-- View this message in context: http://cxf.547215.n5.nabble.com/Is-there-a-way-to-suppress-the-usage-of-org-apache-cxf-javascript-JavascriptQueryHandler-for-my-JAX--tp5733646p5733759.html Sent from the cxf-user mailing list archive at Nabble.com.
