Re: WSSecurityException: The signature or decryption was invalid

Update: There are four different servers load balanced for this one webservice. I've included all four public certificates in my truststore, and now I'm connecting without issue :) -- Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html

Re: Setting XML parser features

> On Apr 30, 2019, at 7:05 AM, Miljenko Brkic wrote: > > I have a SOAP endpoint and want to validate incoming requests against the > WSDL. The problem is that WSDL imports multiple XSDs using the same > namespace I would fix that problem, not try to hack the parser to accept it. The WSDL sh

Re: Problem following 301 (Moved permanently)

The following interceptor did the trick. Regards! private class MyMessageSenderEndingInterceptor extends AbstractPhaseInterceptor { public MyMessageSenderEndingInterceptor() { super(Phase.PREPARE_SEND_ENDING); addAfter(MessageSenderEndingInterceptor.class.getNa

Re: Problem following 301 (Moved permanently)

Hi Colm! Thank you so much for your help. I think I've found the problem's root. In completeExchange method (org.apache.cxf.jaxrs.client.AbstractClient class) whenever a redirect is accomplished the state's base URI is modified using the stored retransmit URL. From my understanding it isn't a good