Think we finally managed to get the functionality same as with the earlier version of CXF. But we noticed an unusual thing. It is about the memory the application is consuming with the new CXF libraries. Application with the new CXF libraries is consuming a lot more memory and the GC time is also higher. The JVM has gone from using 8 GB to more than 10GB.
Do you see anything that we will need to take care of with the latest ones? Below are list of customisations that I had to do in our application to retain the functionality after using the new CXF libraries. 1. Constructing JAXBContext for one of the WS clients. (This is a static variable done in a static block. So does not construct for every request) 2. Added an AbstractSoapInterceptor for our WS to remove the SOAPAction from the requests. 3. Added StaxTransformFeature to convert some of the root elements coming without namespace to append namespaces. -- 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--tp5733646p5733949.html Sent from the cxf-user mailing list archive at Nabble.com.
