[jira] [Resolved] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty

["J.W. Janssen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.W. Janssen resolved FELIX-4421.
---------------------------------

    Resolution: Fixed
      Assignee: J.W. Janssen

I've upgraded the Jetty version to version 8. To mark the version bump in Jetty, I've bumped the versions of the HTTP bundles to 2.3.0-SNAPSHOT. See rev #1565705. 

For convenience, the latest snapshots of the HTTP bundles can be found in <http://repository.apache.org/content/groups/snapshots/org/apache/felix/>.

Please close this issue if the new bundles work correctly.

> 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
>            Assignee: J.W. Janssen
>         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)