felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
Date Thu, 06 Feb 2014 14:48:09 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893394#comment-13893394
] 

J.W. Janssen commented on FELIX-4421:
-------------------------------------

I'd propose to jump immediately to Jetty 9.x as this is the current active development branch
of Jetty. Implementing this could go along with the implementation of RFC-189 (HTTP-service
enhancements).

> Embed Jetty 8 in Felix Http Jetty
> ---------------------------------
>
>                 Key: FELIX-4421
>                 URL: https://issues.apache.org/jira/browse/FELIX-4421
>             Project: Felix
>          Issue Type: New Feature
>          Components: HTTP Service
>    Affects Versions: http-2.2.1
>            Reporter: Dominique Pfister
>         Attachments: patch.txt
>
>
> Currently, the Jetty version embedded in Felix Http Jetty is version 7.6.13.v20130916.
In order to leverage features available in Servlet API 3.0 only, I'd like to change the embedded
version to 8.1.14.v20131031.
> A quick test shows that increasing this version number in parent/pom.xml alone requires
some small changes to JettyService, deployment of a fresh build of Http Jetty into an OSGI
container succeeds, but no request can be handled, because Jetty internally calls methods
on interfaces and classes that were only introduced in Servlet API 3.0.
> This implies that the servlet version supported should be upped to 3.0 as well. In order
to be backward compatible with bundles expecting a 2.x version, one could also export a virtual
version (e.g. 2.6) to satisfy those.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message