Thanks for the reply. We are doing it using several wars and sharing the schemas as a library is definitely on our task list.
So, my colleague found something that got us over the memory hump. When standing up our service, we pretty much just followed what was the instructions on the User's Guide for creating the Service and configuring it, but with two major differences. We removed the "@WebService" annotations on our service implementation and instead have it implement the port class. The endpoints are configured in the cxf-servlet.xml as usual. With these changes, it looks like CXF doesn't try to compile the WSDLs again on deploy. This seems to work for us, and our memory footprint is much much lower. -- View this message in context: http://cxf.547215.n5.nabble.com/Lowering-the-memory-footprint-on-deployment-of-service-endpoints-tp5713684p5713724.html Sent from the cxf-user mailing list archive at Nabble.com.
