I was able to fix this by adding my own AbstractSoapInterceptor and
manually adding the mustUnderstand-Attribute to the EncryptedHeader
Element and set it to "true".
After this the remote server accept my messages.
Thanks - solved!
Am 16.11.2016 um 15:39 schrieb Martin Fernau:
Hi Colm,
thank
On Wed, Nov 16, 2016 at 3:32 AM, Sergey Beryozkin wrote:
> Hi Benson
>
> May be you can work with Bus DestinationRegistry and supply a configured
> JettyDestination
It turned out that the one parameter I cared about is accounted for as
a config admin param in the OSGi activator. So I don't need t