InclusiveNamespaces and empty PrefixList

I have a dynamic client application that is sending a signed SOAP request to a service where an InclusiveNamespaces element contains a PrefixList that is empty. The service rejects the payload with the error: *Validation failed because:cvc-minLength-valid: Value '' with length = '0' is not

RE: Asking for comments about cxf-rs with oneway jms transport

Hi Tobias, The solution with two JMS brokers should work, alternatively I see the following options: 1) Using CXF Failover feature http://cxf.apache.org/docs/jax-rs-failover.html In this case Proxies and WebClients can be configured to failover to the same (or alternate) addresses in

Re: Why proxies encode '+' query parameters

On 08/03/16 17:16, Sergey Beryozkin wrote: On 08/03/16 16:56, Sergey Beryozkin wrote: "+" value also allowed in query representation, but is encoded for some reason by UriBuilder. Well, this is not CXF specific. So there would be problems with stored in db values if they contains "+" I'm

Why proxies encode '+' query parameters

"+" value also allowed in query representation, but is encoded for some reason by UriBuilder. So there would be problems with stored in db values if they contains "+" I'm not using jerecy, only org.apache.cxf.jaxrs.client.JAXRSClientFactoryBean to create proxies. I found

Re: Percent encoded string in @QueryParam

I'm not going to repeat most of what I've already said few times in this thread but only state again that CXF proxies depend on JAX-RS UriBuilder and therefore UriBuilder dictates how %-encoded query (and other) parameters get processed. This is a won't fix 'issue'. However I also mentioned

Re: Percent encoded string in @QueryParam

I agree that UriBuilder implements what is states. Such values are allowed in the query representations. The UriBuilder > does not know what the intention of the CXF proxy user is, it may have > an encoded representation of a given character stored in the DB and > wants to pass it as is via the

Re: Using RSA with SHA256 algorithm for WS-Security policy

Yes, there is a special JAX-WS configuration property to change the asymmetric signature algorithm - "ws-security.asymmetric.signature.algorithm". See here: http://cxf.apache.org/docs/ws-securitypolicy.html Colm. On Mon, Mar 7, 2016 at 6:20 PM, Giriraj Bhojak wrote: >