cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Lowering the memory footprint on deployment of service endpoints
Date Fri, 07 Sep 2012 18:53:04 GMT

On Sep 6, 2012, at 4:12 PM, kongar <> wrote:

> 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.

Are you trying to deploy them as separate wars or all in a single war?

If in separate wars, you may likely be better off if you can move the CXF jars and the "shared"
classes generated from the schemas out of the wars and into something like a "shared/lib"
or similar.  If you do that, it's likely that CXF can share the JAXBContext objects which
can save a significant amount of memory.


>  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:
> Sent from the cxf-user mailing list archive at

Daniel Kulp -
Talend Community Coder -

View raw message