Thanks Colm. That is a very interesting option indeed even though it seems we have to loosen the Layout specification of the WS-Policy used.
Kind regards Jesper -----Original Message----- From: Colm O hEigeartaigh [mailto:cohei...@apache.org] Sent: 5. november 2018 12:53 To: users@cxf.apache.org Subject: Re: CXF and possible performance optimizations CXF supports a streaming WS-Security implementation that might suit your needs as well. You can enable it by setting the JAX-RS property "ws-security.enable.streaming" to "true". Colm. On Fri, Nov 2, 2018 at 8:24 PM Jesper Duelund Isaksen < jesper.duelund.isak...@systematic.com> wrote: > Alright, sounds great. I will have a deeper look into it. > > Thanks for the quick response. > > Kind regards > Jesper > > > -----Original Message----- > From: Markus Schulz [mailto:m...@onesty-tech.de] > Sent: 2. november 2018 10:32 > To: users@cxf.apache.org > Subject: Re: CXF and possible performance optimizations > > Am Freitag, 2. November 2018, 09:08:34 CET schrieb Jesper Duelund > Isaksen: > > Thanks for your suggestion Markus! > > > > It looks like a WebServiceProvider for either the SAXSource or > > StreamSource would fit our needs. > > > > However the note regarding developers needing to manually handle > > SOAP envelopes leads me to assume that everything WS-SecurityPolicy > > related needs to be manually handled as well. Would you consider that > > correct? > > no, you don't need to handle security manually. > Full WS-SecurityPolicy (or other cxf-specific interceptors) are available. > Simply put the ws-security-policy into your wsdl and let cxf do the > hard work for you. > > @ServiceMode(value = Service.Mode.PAYLOAD) > @WebServiceProvider(wsdlLocation = "your.wsdl", ...) public class > MyProvider implements Provider<Source> { > > @Override > public Source invoke(Source source) { > ...unmarshal source on demand with jaxb or similar... > } > > } > > regards > msc > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
