[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[ https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.W. Janssen updated FELIX-4421: Fix Version/s: http-2.3.0 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 Fix For: http-2.3.0 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)
[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[
https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister updated FELIX-4421:
-
Attachment: patch.txt
Patch that increases Jetty and Servlet API version, and provides NY (not
yet)-implementations for new ServletContext methods introduced in version 3.0.
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 on 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)
[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[
https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister updated FELIX-4421:
-
Attachment: patch.txt
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 on 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)
[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[
https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister updated FELIX-4421:
-
Attachment: (was: patch.txt)
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 on 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)
[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[
https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister updated FELIX-4421:
-
Description:
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 on 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.
was:
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 on 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.
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 on 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)
[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[
https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister updated FELIX-4421:
-
Description:
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 on 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.
was:
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 on 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.
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 on 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)
[jira] [Updated] (FELIX-4421) Embed Jetty 8 in Felix Http Jetty
[ https://issues.apache.org/jira/browse/FELIX-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated FELIX-4421: - Description: 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. was: 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 on 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. 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)
