I don't think it will as I know I haven't implemented anything using the http/spi things yet and I don't remember Jim doing so either. The JAX-WS 2.2 TCK doesn't hit it at all. Thus, it's not really something that needs to be there to claim compliance.
I did see that blog entry and thought it looked interesting, but I really haven't had the time to try getting that stuff implemented. It may be pretty tricky to implement as it almost requires a whole new transport, but I haven't looked to much at it. Dan On Thursday 29 July 2010 9:50:39 pm Glen Mazza wrote: > 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-usin > g-jax-ws-22-http-spi [2] > https://jax-ws-commons.dev.java.net/grizzly-httpspi/jaxws-grizzly-httpspi/i > ndex.html -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
