felix-dev mailing list archives

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

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

Felix Meschberger commented on FELIX-4421:

[~jajans] I thought this would come up :-)

According to [~dpfister] the changes from Jetty 7 to Jetty 8 are not that dramatic and require
little changes to the bridge. The changes to Jetty 9 seem to be rather substantial apart from
Jetty 9 requiring Java 7 (there is still a large install base on Java 6, unfortunately).

So in the interest of having Servlet API 3 soonish, I suggest to first go for Jetty 8 (and
have a release of that) and do the Jetty 9 switch later.


> 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

View raw message