Re: Performance issues with many outstanding async REST requests

Hi Benson, To ignore the pax-web and spin up a standalone jetty transport, you just need publish the endpoint with absolute url address like http://host:port/context …. with this absolute address the cxf http-jetty transport will kick in but not to use the servlet

Performance issues with many outstanding async REST requests

We observe the following: CXF 3.1.4 in Karaf 4.0.4, with pax web, and thus jetty 9.2.something. When we have hundreds of outstanding async requests, a thread from Jetty starts eating CPU time; it uses up an entire core -- it's spending time in some method of some Eclipse blocking queue class.

Re: mtom encryption with WS-Security

Have you added "" to your "EncryptedParts" policy? Colm. On Wed, Mar 2, 2016 at 9:25 PM, Deepti wrote: > Hi, > > I am using cxf 3.0.x for building my web service.I need the web service to > send an encrypted mtom-enabled attachment to the .net client.I tried to > enable

RE: STS Behavior Change In CXF 3+?

No, I'm not configuring an AttributeStatementProvider, at least not yet. Bearer tokens are an edge case for us so I probably haven't given them quite enough attention. The default AttributeStatement should be fine for us in this case though. Thanx, Stephen W. Chappell -Original

Re: STS Behavior Change In CXF 3+?

Hi Stephen, It should only add in that AttributeStatement if no other Statements are added into the generated assertion. It did have the behaviour that you specified, where the default AttributeStatement was also added to the Assertion, but this was fixed before CXF 3.1.4. Are you configuring a

dosgi/cxf-aegis rootClasses properties

Hello, I want to submit through a dosgi service a class like the following: @XmlRootElement(name = "MyClass") public class MyClass { T stuffInstance1; T stuffInstance2; @XmlElement(name = "stuffInstance1") T getStuffInstance1(){ }

How to manage resource owner login in CXF

I'm trying to figure out how to deal with resource owner login procedure in CXF OAuth2 implementation. In the docs (http://cxf.apache.org/docs/jax-rs-oauth2.html) it is stated that /The client application asks the current user (the browser) to go to a new address provided by the Location header

Re: Percent encoded string in @QueryParam

Briefly returning to this thread and clarify why I'm asking to check Jersey UriBuilder or perhaps, even better JAX-RS 2.0 Client API with Jersey and the way the certain combinations are treated: - double encoding of URI (Path, Query) parameters. - double encoding of Form parameters. - treatment