Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 10 Oct 2016 10:03:43 -0400
From: Andriy Redko <drreta@gmail.com>
Reply-To: Andriy Redko <drreta@gmail.com>
Message-ID: <1352819961.20161010100343@gmail.com>
To: Sergey Beryozkin <sberyozkin@gmail.com>
CC: Daniel Kulp <dev@cxf.apache.org>
Subject: Re: Upgrading Servlet API version to 3.1
In-Reply-To: <46047343-84b6-1fb3-747f-3878e4c42201@gmail.com>
References: <a9eaed79-7bb4-b160-86cc-49e9a44c4265@gmail.com> <46047343-84b6-1fb3-747f-3878e4c42201@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Oct 2016 14:04:18 -0000

Hey Sergey,

Thanks a bunch, I am looking into Netty transport, it depends on Servlet 2.5,
I am curious to know why ...

Best Regards,
    Andriy Redko

SB> I've committed it to the master only

SB> Cheers, Sergey
SB> On 06/10/16 13:54, Sergey Beryozkin wrote:
>> Hi

>> I've started preparing CXF 3.2.0-SNAPSHOT only to move Servlet API 3.1
>> [1]. In CXF 3.2.0 we'll most likely need it to support JAX-RS 2.1 NIO
>> features and perhaps the JAX-WS frontend can be enhanced accordingly.
>> It may also help us with improving the CXF web socket transport.

>> We've been using geronimo servlet artifacts, but no geronimo servlet 3.1
>> artifact exists and I've noticed Karaf 4 has been updated to use

>> javax.servlet/javax.servlet-api/3.1.0

>> Thus I'm also updating the master code to use this artifact - any
>> concerns - let me know please.

>> (The only exception is a netty server module - apparently this one still
>> needs Servlet 2.5).

>> Cheers, Sergey


>> [1] https://issues.apache.org/jira/browse/CXF-7077