Hello all, I am working with several service endpoints with wsdls that all import the same huge schemas (HL7) that seems to choke my application server whenever I try to deploy them. I am publishing my endpoints via the cxf-servlet.xml config file. Would using a Spring application context or the CXF API to publish provide me any substantial benefit? Supposedly the former loads modules that I may not need, but the latter two are not as well documented, and consequently, I am having a harder time trying to get those to work. My deployment seems to choke on the WSDLServiceBuilder/JAXBDataBinding phase, so I'm guessing the benefits of not using cxf-servlet.xml will not matter.
Can anyone shed some light on what CXF is doing during deployment (i.e. WSDLServiceBuilder)? Maybe if I understand what is going on, I can tune and lower the memory footprint. Any help will be greatly appreciated! -- View this message in context: http://cxf.547215.n5.nabble.com/Lowering-the-memory-footprint-on-deployment-of-service-endpoints-tp5713684.html Sent from the cxf-user mailing list archive at Nabble.com.
