cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <glen.ma...@gmail.com>
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?

Thanks,
Glen

[1]
http://weblogs.java.net/blog/jitu/archive/2010/07/09/grizzly-transport-using-jax-ws-22-http-spi
[2]
https://jax-ws-commons.dev.java.net/grizzly-httpspi/jaxws-grizzly-httpspi/index.html

-- 
View this message in context: http://cxf.547215.n5.nabble.com/HTTP-SPI-working-for-us-tp2259090p2259090.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Mime
View raw message