Re: cxf 3.2 with tomcat 7

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 wrote: >> I think this is very legitimate query. At some point JAX-RS 2.1 API

Re: cxf 3.2 with tomcat 7

> On Mar 5, 2018, at 2:07 PM, Andriy Redko 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 >

Re: cxf 3.2 with tomcat 7

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

Re: cxf 3.2 with tomcat 7

Hi Andriy, What do you think of this query? Thanks, Colm. On Wed, Feb 28, 2018 at 1:18 PM, Thibaut Robert wrote: > Hi, > > When deploying cxf 3.2 on tomcat 7, it breaks because of a hard dependency > on Servlet 3.1 classes in Servlet3ContinuationProvider >

Re: JAXBException when streaming XML response

Have you tried explicitly adding the BinaryDataProvider as a JAX-RS provider? Here's an example that explicitly adds the JAXBElementProvider: https://github.com/apache/cxf/blob/4aaba3503b926b43634a6977d0150e4fd4557aa1/systests/jaxrs/src/test/resources/jaxrs/WEB-INF/beans.xml#L67 Colm. On Fri,

Re: Followed wsdl_first_https but when I deploy to the server get not a valid service

Could you create a sample project that we can run to reproduce the error? Colm. On Fri, Mar 2, 2018 at 6:59 PM, David Wynter wrote: > I converted the wsdl_first_https sample for 3.2.2 to use my wsdl and > implemntation classes. I got it running locally. Then