thanks Dan
On 20/12/12 14:16, dk...@apache.org wrote:
Author: dkulp
Date: Thu Dec 20 14:16:01 2012
New Revision: 1424479
URL: http://svn.apache.org/viewvc?rev=1424479view=rev
Log:
[CXF-4714] Better fix by fixing the underlying jetty stream
Modified:
I am operating in an environment where I communicate with web services to a
group of organization with certs signed by a common CA. This set of
organizations is mutable, and I don't want to manage my truststore everytime
a new organization joins. However, per my understanding of the
specifications
On 13/12/12 12:01, Sergey Beryozkin wrote:
Hi,
I've opened CXF-4696 [1] to get the client implementation moved out of
jax-rs frontend to its own module: to get the main module smaller, to
let users avoid downloading extra baggage when no client code is
utilized and in preparation for
I am operating in an environment where I communicate with web services to a
group of organization with certs signed by a common CA. This set of
organizations is mutable, and I don't want to manage my truststore everytime
a new organization joins. However, per my understanding of the
specifications
Hi
At the moment CXF 2.7.2-SNAPSHOT depends on jsr339-api-m10 - this is
quite close to the current JAX-RS 2.0 Snapshot API. ServiceMix spec
jsr339-api-m10 (v 2.2.0) is also available.
Next, jsr339-api-m13 and now jsr339-api-m15 are available in Central.
The differences between
I got this spun up but CXF doesn't seem to be acknowledging that I have
provided a custom interceptor. I use spring to provision endpoints, here is
an excerpt of my service definition:
jaxws:properties
entry key=ws-security.callback-handler
