Consolidating on a single framework, CXF good fit for this use-case?

Hi all,

I'm working on an internal product that has grown quite organically over
time. As a result, there is quite a mix of frameworks/libraries in use,
often with overlapping functionality. I'm looking at rationalizing this
to some reasonable mininum, with the aim to (1) minimize the number of
different frameworks in use and (2) reducing deployment footprint.

Right now we are using:
- Apache HTTP Components for an internal web server
- Jetty for an internal web server (published Web Services written with
SAAJ,
we can't dump SAAJ in this case)
- Grizzly for an internal web server (serves REST requests)
- Axis 1.4 for SOAP Web Service client
- CXF 2.7.8 for SOAP Web Service client (JAX-WS)
- Jersey for serving and invoking JAX-RS services
- Pretty soon I'll need to make HTTP(S) calls as well in combination
with SAAJ.

A couple of requirements that we have:
- Embedded Web Server must be able to handle requests asynchronously
- Need to be able to make async client requests
- SAAJ, JAX-WS 2.0, JAX-RS
- SSL/TLS with client certificates
- Authentication methods, both on outgoing and incoming requests:
basic, digest, NTLM, ideally OAuth2
- We see a potential need in the near future to handle >5000 requests/sec
- Using an application server/servlet container is no option
- Java 7, probably 8 pretty soon

Right now I'm thinking that we can (mostly) consolidate on CXF 3. It
certainlyticks the boxes wrt SAAJ, JAX-WS, JAX-RS and async client requests.

What I'm still unsure about is what to use for embedded web server. CXF
2.7.8doesn't seem to offer anything here. However I notice in the CXF
3.0.3distribution that there's a Jetty ServerEngine class and a Netty
ServerEngineclass. I can't find any documentation on this however.

I'm asking the community therefore:
- is CXF a good fit for this?
- do I need to pull in a separate dependency for an embedded HTTP(S) Server?

Maarten