[
https://issues.apache.org/jira/browse/FELIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053785#comment-14053785
]
Chetan Mehrotra commented on FELIX-4550:
----------------------------------------
bq. I don't want to get into a long discussion, but what about making this a
little bit pluggable, so we end up with two versions, one with Jetty8 and one
with Jetty9?
Ack. Can rework the patch for that. So what should be the way? One way I can
think of
* Create a new sibling module with artifactId org.apache.felix.http.jetty9
* Do not update the version in parent pom. Instead use separate profile where
Jetty9 has to be used and tested
* ConnectorFactory - Instead of changing existing interface introduce a new one
ConnectorFactory2 which takes Server instance such that same itest can be run
against both
* For Servlet API bundle I think it would be fine to export it new 3.1 packages
as I do not expect much change in previously released API bundle
Would that be ok?
> Upgrade embedded Jetty to version 9.2.x in Felix Http Jetty
> -----------------------------------------------------------
>
> Key: FELIX-4550
> URL: https://issues.apache.org/jira/browse/FELIX-4550
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
> Reporter: Chetan Mehrotra
> Attachments: FELIX-4550.patch
>
>
> Currently HTTP Service embeds Jetty 8.1.14.v20131031 which supports Servlet
> 3.0. Current Jetty version 9.2.1.v20140609 supports Servlet 3.1 which
> provided access to some new NIO based features. Further it also provides lots
> of new features like Spdy support , Websocket support etc [1]
> [1] https://webtide.com/jetty-9-features/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
