You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Thibaut Robert <th...@gmail.com> on 2018/02/28 13:18:43 UTC
cxf 3.2 with tomcat 7
Hi,
When deploying cxf 3.2 on tomcat 7, it breaks because of a hard dependency
on Servlet 3.1 classes in Servlet3ContinuationProvider
(javax.servlet.WriteListener), which results in ClassNotFound at runtime.
Is it expected behavior, or should there be a check for servlet 3.1
availability like there is for servlet 3 ?
Note this was introduced by [CXF-6882] Initial JAX-RS NIO Write support.
Regards,
Thibaut
Re: cxf 3.2 with tomcat 7
Posted by Thibaut Robert <th...@gmail.com>.
Thanks for taking this into consideration !
Best regards,
Thibaut
On Mon, Mar 5, 2018 at 11:41 PM Andriy Redko <dr...@gmail.com> wrote:
> 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 <dr...@gmail.com> 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 <
> thibaut.robert@gmail.com> 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
>
>
>
>
>
>
>
>
Re: cxf 3.2 with tomcat 7
Posted by Andriy Redko <dr...@gmail.com>.
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 <dr...@gmail.com> 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 <th...@gmail.com> 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
Re: cxf 3.2 with tomcat 7
Posted by Daniel Kulp <dk...@apache.org>.
> On Mar 5, 2018, at 2:07 PM, Andriy Redko <dr...@gmail.com> 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?
I definitely think that makes sense to me. I didn’t realize Tomcat 7 hadn’t been updated to Servlet 3.1. Since 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.
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 <th...@gmail.com> 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
>
>
>
>
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: cxf 3.2 with tomcat 7
Posted by Andriy Redko <dr...@gmail.com>.
Hi Colm,
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?
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 <th...@gmail.com> 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
Re: cxf 3.2 with tomcat 7
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Andriy,
What do you think of this query?
Thanks,
Colm.
On Wed, Feb 28, 2018 at 1:18 PM, Thibaut Robert <th...@gmail.com>
wrote:
> Hi,
>
> When deploying cxf 3.2 on tomcat 7, it breaks because of a hard dependency
> on Servlet 3.1 classes in Servlet3ContinuationProvider
> (javax.servlet.WriteListener), which results in ClassNotFound at runtime.
>
> Is it expected behavior, or should there be a check for servlet 3.1
> availability like there is for servlet 3 ?
>
> Note this was introduced by [CXF-6882] Initial JAX-RS NIO Write support.
>
> Regards,
> Thibaut
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com