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
Hello!
Thanx. I wrote an interceptor what clear the SoapHeader, and put before
the MAPCodec interceptor. And Its working.
thanx
Csaba
On 2018-11-01 19:31, Daniel Kulp wrote:
You likely will need to write an interceptor for the client that removes all
the WS-Addressing headers from the
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
Am Freitag, 2. November 2018, 06:35:09 CET schrieb Jesper Duelund
Isaksen:
> Hello!
>
> I am currently on a project where we are building a platform exposing
> a large number of standard WSDL-first SOAP services with typed SEI
> classes. The purpose of the platform is to do authentication and
>
Hello!
I am currently on a project where we are building a platform exposing a large
number of standard WSDL-first SOAP services with typed SEI classes. The purpose
of the platform is to do authentication and authorization for a large number of
users before the users access external data
