felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Walker (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
Date Fri, 07 Feb 2014 11:22:20 GMT

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

Rob Walker edited comment on FELIX-4421 at 2/7/14 11:22 AM:
------------------------------------------------------------

Agree. Our project would also have an interest in Jetty 9 and RFC-189 (which I see has it's
own JIRA). Do we need a separate JIRA for Jetty 9?

Perhaps if we get Jetty 8 support into an official release, we can get the latest head version
or a sandbox version with Jetty 9 in that for sites happy to be early adopters. It's only
a matter of time before Jetty 9 becomes the defacto standard, so it's really down to early
access for the brave


was (Author: walkerr):
Agree. Our project would also have an interest in Jetty 9 and RFC-189 (which I see has it's
own JIRA). Do we need a separate JIRA for Jetty 9?

> 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