Created https://issues.apache.org/jira/browse/CXF-7668 to track that. If someone wants to pick it up right away, please feel free to do so. Thanks, guys!
>> On Mar 5, 2018, at 2:07 PM, Andriy Redko <[email protected]> wrote: >> I think this is very legitimate query. At some point JAX-RS 2.1 API dropped >> NIO support and the dependecy on Servlet 3.1 API as well, right before >> releasing the spec (commit reference >> https://github.com/jax-rs/api/commit/a4faa965bbe4d058caa41f56f712fa52fc9600fe#diff-bb05b5ab9309760c3271445278116a2f). >> We could try to make 3.0 the base line (right now it is 3.1) and see if it >> breaks something else besides NIO part. What do you think? DK> I definitely think that makes sense to me. I didn’t realize Tomcat 7 hadn’t been updated to Servlet 3.1. Since DK> it’s still on 3.0, I definitely think we should try and support it, even if it’s for some reduced level of functionality. DK> Dan >> Best Regards, >> Andriy Redko >> COh> Hi Andriy, >> COh> What do you think of this query? >> COh> Thanks, >> COh> Colm. >> COh> On Wed, Feb 28, 2018 at 1:18 PM, Thibaut Robert >> <[email protected]> wrote: >> COh> Hi, >> COh> When deploying cxf 3.2 on tomcat 7, it breaks because of a hard >> dependency >> COh> on Servlet 3.1 classes in Servlet3ContinuationProvider >> COh> (javax.servlet.WriteListener), which results in ClassNotFound at >> runtime. >> COh> Is it expected behavior, or should there be a check for servlet 3.1 >> COh> availability like there is for servlet 3 ? >> COh> Note this was introduced by [CXF-6882] Initial JAX-RS NIO Write >> support. >> COh> Regards, >> COh> Thibaut
