cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <>
Subject HTTP SPI working for us?
Date Fri, 30 Jul 2010 01:50:39 GMT

Team, Jitendra Kotamaraju of the Metro team recently created[1] a
JAXWS-Grizzly-HTTP SPI[2] (Service Provider Interface, I guess) that allows
for a programmatic change of the underlying servlet container used for the
Endpoint class (Grizzly instead of Jetty in our case.)  

I haven't tested it on CXF 2.3, but he claims this should work on any JAX-WS
2.2 runtime.  Is this portion (the HTTP SPI) of JAX-WS 2.2 already finished
in the upcoming CXF 2.3, i.e., this should work for us?



View this message in context:
Sent from the cxf-dev mailing list archive at

View raw message