[jira] [Created] (FELIX-6706) Avoid Jetty restart in case of a required configuration
Carsten Ziegeler created FELIX-6706: --- Summary: Avoid Jetty restart in case of a required configuration Key: FELIX-6706 URL: https://issues.apache.org/jira/browse/FELIX-6706 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.jetty12-1.0.6, http.jetty-5.1.14 If Jetty is configured through an OSGi configuration (singleton not factory), then Jetty is restarted. In this case, Jetty is first started with the default properties, then a managed service is registered which then later on is triggered by the OSGi configuration. And that results in Jetty restarting. While this works, it is unnecessary -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6702) Make Jetty bundles EE version neutral
[ https://issues.apache.org/jira/browse/FELIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-6702: Fix Version/s: http.jetty12-1.0.6 http.jetty-5.1.14 > Make Jetty bundles EE version neutral > - > > Key: FELIX-6702 > URL: https://issues.apache.org/jira/browse/FELIX-6702 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty12-1.0.4, http.jetty-5.1.12 >Reporter: Paul Rütter (BlueConic) >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty12-1.0.6, http.jetty-5.1.14 > > > As discussed in FELIX-6701, this issue asks to make the jetty bundles EE > version neutral, to make it easier to migrate to newer EE versions in the > future. > Upgrade instructions once this PR is merged: > h1. When using Jetty 5.1.12 > * org.apache.felix.jakarta.ee9.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee9.websocket.enable -> > org.apache.felix.jetty.websocket.enable > h1. When using Jetty12 1.0.4 > * org.apache.felix.jakarta.ee10.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee10.websocket.enable -> > org.apache.felix.jetty.websocket.enable > Classifiers: > * with-jetty-ee10-websockets -> with-jetty-websockets > * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FELIX-6702) Make Jetty bundles EE version neutral
[ https://issues.apache.org/jira/browse/FELIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-6702. - Resolution: Fixed Thanks [~paul_blueconic], PR is applied > Make Jetty bundles EE version neutral > - > > Key: FELIX-6702 > URL: https://issues.apache.org/jira/browse/FELIX-6702 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty12-1.0.4, http.jetty-5.1.12 >Reporter: Paul Rütter (BlueConic) >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty12-1.0.6, http.jetty-5.1.14 > > > As discussed in FELIX-6701, this issue asks to make the jetty bundles EE > version neutral, to make it easier to migrate to newer EE versions in the > future. > Upgrade instructions once this PR is merged: > h1. When using Jetty 5.1.12 > * org.apache.felix.jakarta.ee9.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee9.websocket.enable -> > org.apache.felix.jetty.websocket.enable > h1. When using Jetty12 1.0.4 > * org.apache.felix.jakarta.ee10.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee10.websocket.enable -> > org.apache.felix.jetty.websocket.enable > Classifiers: > * with-jetty-ee10-websockets -> with-jetty-websockets > * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FELIX-6702) Make Jetty bundles EE version neutral
[ https://issues.apache.org/jira/browse/FELIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-6702: --- Assignee: Carsten Ziegeler > Make Jetty bundles EE version neutral > - > > Key: FELIX-6702 > URL: https://issues.apache.org/jira/browse/FELIX-6702 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty12-1.0.4, http.jetty-5.1.12 >Reporter: Paul Rütter (BlueConic) >Assignee: Carsten Ziegeler >Priority: Major > > As discussed in FELIX-6701, this issue asks to make the jetty bundles EE > version neutral, to make it easier to migrate to newer EE versions in the > future. > Upgrade instructions once this PR is merged: > h1. When using Jetty 5.1.12 > * org.apache.felix.jakarta.ee9.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee9.websocket.enable -> > org.apache.felix.jetty.websocket.enable > h1. When using Jetty12 1.0.4 > * org.apache.felix.jakarta.ee10.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee10.websocket.enable -> > org.apache.felix.jetty.websocket.enable > Classifiers: > * with-jetty-ee10-websockets -> with-jetty-websockets > * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6702) Make Jetty bundles EE version neutral
[ https://issues.apache.org/jira/browse/FELIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-6702: Affects Version/s: http.jetty-5.1.12 http.jetty12-1.0.4 > Make Jetty bundles EE version neutral > - > > Key: FELIX-6702 > URL: https://issues.apache.org/jira/browse/FELIX-6702 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http.jetty12-1.0.4, http.jetty-5.1.12 >Reporter: Paul Rütter (BlueConic) >Priority: Major > > As discussed in FELIX-6701, this issue asks to make the jetty bundles EE > version neutral, to make it easier to migrate to newer EE versions in the > future. > Upgrade instructions once this PR is merged: > h1. When using Jetty 5.1.12 > * org.apache.felix.jakarta.ee9.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee9.websocket.enable -> > org.apache.felix.jetty.websocket.enable > h1. When using Jetty12 1.0.4 > * org.apache.felix.jakarta.ee10.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee10.websocket.enable -> > org.apache.felix.jetty.websocket.enable > Classifiers: > * with-jetty-ee10-websockets -> with-jetty-websockets > * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] FELIX-6702 Make Jetty bundles EE version neutral [felix-dev]
cziegeler merged PR #315: URL: https://github.com/apache/felix-dev/pull/315 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] FELIX-6702 Make Jetty bundles EE version neutral [felix-dev]
cziegeler commented on PR #315: URL: https://github.com/apache/felix-dev/pull/315#issuecomment-2099740193 Thanks @paulrutter -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FELIX-6703) Missing conf properties in the documentation
[ https://issues.apache.org/jira/browse/FELIX-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Palano updated FELIX-6703: --- Labels: webconsole (was: web-console-configuration) > Missing conf properties in the documentation > > > Key: FELIX-6703 > URL: https://issues.apache.org/jira/browse/FELIX-6703 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-5.0.2 >Reporter: Luca Palano >Priority: Major > Labels: webconsole > > The webconsole documentation doesn't report in the "[OSGi Configuration Admin > title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]; > section, the following configuration properties: > * shutdown.timeout > * reload.timeout > Introduced by FELIX-6356, already merged on master. > [Here|https://github.com/apache/felix-dev/pull/316] is my github PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FELIX-6705) Update to Jetty 12.0.9
[ https://issues.apache.org/jira/browse/FELIX-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rütter updated FELIX-6705: --- Fix Version/s: (was: http.jetty12-1.0.4) > Update to Jetty 12.0.9 > -- > > Key: FELIX-6705 > URL: https://issues.apache.org/jira/browse/FELIX-6705 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Assignee: Carsten Ziegeler >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6705) Update to Jetty 12.0.9
[ https://issues.apache.org/jira/browse/FELIX-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844439#comment-17844439 ] Paul Rütter commented on FELIX-6705: https://github.com/apache/felix-dev/pull/318 > Update to Jetty 12.0.9 > -- > > Key: FELIX-6705 > URL: https://issues.apache.org/jira/browse/FELIX-6705 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Assignee: Carsten Ziegeler >Priority: Major > Fix For: http.jetty12-1.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6705) Update to Jetty 12.0.9
Paul Rütter created FELIX-6705: -- Summary: Update to Jetty 12.0.9 Key: FELIX-6705 URL: https://issues.apache.org/jira/browse/FELIX-6705 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Paul Rütter Assignee: Carsten Ziegeler Fix For: http.jetty12-1.0.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] Upgrade to jetty 12.0.9 [felix-dev]
paulrutter opened a new pull request, #318: URL: https://github.com/apache/felix-dev/pull/318 https://issues.apache.org/jira/browse/FELIX-6705 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] FELIX-6704: Include config/factory PID in error message [felix-dev]
kwin opened a new pull request, #317: URL: https://github.com/apache/felix-dev/pull/317 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (FELIX-6704) Improve error logging for exceptions thrown from Configuration Plugins in ConfigurationManager
Konrad Windszus created FELIX-6704:
--
Summary: Improve error logging for exceptions thrown from
Configuration Plugins in ConfigurationManager
Key: FELIX-6704
URL: https://issues.apache.org/jira/browse/FELIX-6704
Project: Felix
Issue Type: Improvement
Components: Configuration Admin
Affects Versions: configadmin-1.9.24
Reporter: Konrad Windszus
Currently all throwables are caught in
https://github.com/apache/felix-dev/blob/517f9a0c89cad1866f315255568b40c568f5239d/configadmin/src/main/java/org/apache/felix/cm/impl/ConfigurationManager.java#L932
and logged.
The important factory or configuration PID is not emitted in the log message
though.
Example:
{code}
07.05.2024 20:41:33.820 *ERROR* [FelixLogListener]
LogService.org.apache.felix.configadmin Service
[org.apache.felix.cm.ConfigurationAdmin,47,
[org.osgi.service.cm.ConfigurationAdmin]] Unexpected problem calling
configuration plugin [org.osgi.service.cm.ConfigurationPlugin, id=41,
bundle=38/slinginstall:org.apache.felix.configadmin.plugin.interpolation-1.2.6.jar]
(org.apache.felix.log.LogException:
org.osgi.util.converter.ConversionException: Cannot convert TO BE PROVIDED to
class java.lang.Integer)
org.apache.felix.log.LogException: org.osgi.util.converter.ConversionException:
Cannot convert TO BE PROVIDED to class java.lang.Integer
at org.osgi.util.converter.ConvertingImpl.to(ConvertingImpl.java:243)
at
org.osgi.util.converter.CustomConverterImpl$ConvertingWrapper.to(CustomConverterImpl.java:183)
at
org.osgi.util.converter.CustomConverterImpl$ConvertingWrapper.to(CustomConverterImpl.java:151)
at
org.osgi.util.converter.CustomConverterImpl$ConvertingWrapper.to(CustomConverterImpl.java:141)
at
org.apache.felix.configadmin.plugin.interpolation.InterpolationConfigurationPlugin.convertType(InterpolationConfigurationPlugin.java:308)
at
org.apache.felix.configadmin.plugin.interpolation.InterpolationConfigurationPlugin.lambda$replace$0(InterpolationConfigurationPlugin.java:197)
at
org.apache.felix.configadmin.plugin.interpolation.Interpolator.replace(Interpolator.java:149)
at
org.apache.felix.configadmin.plugin.interpolation.InterpolationConfigurationPlugin.replace(InterpolationConfigurationPlugin.java:179)
at
org.apache.felix.configadmin.plugin.interpolation.InterpolationConfigurationPlugin.getNewValue(InterpolationConfigurationPlugin.java:171)
at
org.apache.felix.configadmin.plugin.interpolation.InterpolationConfigurationPlugin.modifyConfiguration(InterpolationConfigurationPlugin.java:133)
at
org.apache.felix.cm.impl.ConfigurationManager.callPlugins(ConfigurationManager.java:928)
[org.apache.felix.configadmin:1.9.24]
at
org.apache.felix.cm.impl.ConfigurationAdapter.getProcessedProperties(ConfigurationAdapter.java:293)
[org.apache.felix.configadmin:1.9.24]
at
org.apache.felix.scr.impl.manager.RegionConfigurationSupport.getConfigurationInfo(RegionConfigurationSupport.java:532)
[org.apache.felix.scr:2.2.4]
at
org.apache.felix.scr.impl.manager.RegionConfigurationSupport.configurationEvent(RegionConfigurationSupport.java:333)
[org.apache.felix.scr:2.2.4]
at
org.apache.felix.scr.impl.manager.RegionConfigurationSupport$2.configurationEvent(RegionConfigurationSupport.java:115)
[org.apache.felix.scr:2.2.4]
at
org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:1721)
[org.apache.felix.configadmin:1.9.24]
at
org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:1662)
[org.apache.felix.configadmin:1.9.24]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:122)
[org.apache.felix.configadmin:1.9.24]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:84)
[org.apache.felix.configadmin:1.9.24]
at java.base/java.lang.Thread.run(Thread.java:829)
{code}
For debugging purposes the configuration PID is the most crucial bit of
information and this is missing from this log message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FELIX-6703) Missing conf properties in the documentation
[ https://issues.apache.org/jira/browse/FELIX-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Palano updated FELIX-6703: --- Description: The webconsole documentation doesn't report in the "[OSGi Configuration Admin title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]; section, the following configuration properties: * shutdown.timeout * reload.timeout Introduced by FELIX-6356, already merged on master. [Here|https://github.com/apache/felix-dev/pull/316] is my github PR. was: The webconsole documentation doesn't report in the "[OSGi Configuration Admin title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]; section, the following configuration properties: * shutdown.timeout * reload.timeout Introduced by FELIX-6356, already merged on master. > Missing conf properties in the documentation > > > Key: FELIX-6703 > URL: https://issues.apache.org/jira/browse/FELIX-6703 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-5.0.2 >Reporter: Luca Palano >Priority: Major > Labels: web-console-configuration > > The webconsole documentation doesn't report in the "[OSGi Configuration Admin > title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]; > section, the following configuration properties: > * shutdown.timeout > * reload.timeout > Introduced by FELIX-6356, already merged on master. > [Here|https://github.com/apache/felix-dev/pull/316] is my github PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] webconsole doc: add missing conf props [felix-dev]
lucapalano opened a new pull request, #316: URL: https://github.com/apache/felix-dev/pull/316 [FELIX-6703](https://issues.apache.org/jira/browse/FELIX-6703) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FELIX-6703) Missing conf properties in the documentation
[ https://issues.apache.org/jira/browse/FELIX-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Palano updated FELIX-6703: --- Summary: Missing conf properties in the documentation (was: Add missing conf properties in the documentation) > Missing conf properties in the documentation > > > Key: FELIX-6703 > URL: https://issues.apache.org/jira/browse/FELIX-6703 > Project: Felix > Issue Type: Bug > Components: Web Console >Affects Versions: webconsole-5.0.2 >Reporter: Luca Palano >Priority: Major > Labels: web-console-configuration > > The webconsole documentation doesn't report in the "[OSGi Configuration Admin > title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]; > section, the following configuration properties: > * shutdown.timeout > * reload.timeout > Introduced by FELIX-6356, already merged on master. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FELIX-6703) Add missing conf properties in the documentation
Luca Palano created FELIX-6703: -- Summary: Add missing conf properties in the documentation Key: FELIX-6703 URL: https://issues.apache.org/jira/browse/FELIX-6703 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-5.0.2 Reporter: Luca Palano The webconsole documentation doesn't report in the "[OSGi Configuration Admin title|https://github.com/apache/felix-dev/tree/master/webconsole#osgi-configuration-admin]; section, the following configuration properties: * shutdown.timeout * reload.timeout Introduced by FELIX-6356, already merged on master. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6701) Jetty12 EE11 preparation
[ https://issues.apache.org/jira/browse/FELIX-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844216#comment-17844216 ] Paul Rütter (BlueConic) commented on FELIX-6701: Relevant Jetty discussion in [https://github.com/jetty/jetty.project/issues/11265] > Jetty12 EE11 preparation > - > > Key: FELIX-6701 > URL: https://issues.apache.org/jira/browse/FELIX-6701 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Priority: Major > > Jakarta EE 11 should be released within a couple of months, thus Jetty will > follow with a 12.1.x ([https://webtide.com/introducing-jetty-12/). > |https://webtide.com/introducing-jetty-12/).]Ideally, this will become a new > feature of the Jetty12 bundle. > What are the ideas to support this? > For the light bundle, i can imagine that the EE11 classes can be detected in > the classloader, like is done for websocket support. For the main jar, would > both EE10 and EE11 servlet classes be part of it? Or would we introduce new > classifiers for EE11 servlet? Probably, a new configuration option is needed > to specify the EE version to run. > These imports would be problematic if the EE10 classes are not available, > [https://github.com/apache/felix-dev/blob/517f9a0c89cad1866f315255568b40c568f5239d/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L34.] > > Just wondering how new (or existing 8/9, for that matter) EE specifications > would be part of the jetty12 bundle. Of course, we could already try it out > with EE9 as an exercise to ease transition to Jetty12. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6702) Make Jetty bundles EE version neutral
[ https://issues.apache.org/jira/browse/FELIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844173#comment-17844173 ] Paul Rütter (BlueConic) commented on FELIX-6702: As discussed in https://issues.apache.org/jira/browse/FELIX-6701 > Make Jetty bundles EE version neutral > - > > Key: FELIX-6702 > URL: https://issues.apache.org/jira/browse/FELIX-6702 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter (BlueConic) >Priority: Major > > As discussed in FELIX-6701, this issue asks to make the jetty bundles EE > version neutral, to make it easier to migrate to newer EE versions in the > future. > Upgrade instructions once this PR is merged: > h1. When using Jetty 5.1.12 > * org.apache.felix.jakarta.ee9.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee9.websocket.enable -> > org.apache.felix.jetty.websocket.enable > h1. When using Jetty12 1.0.4 > * org.apache.felix.jakarta.ee10.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee10.websocket.enable -> > org.apache.felix.jetty.websocket.enable > Classifiers: > * with-jetty-ee10-websockets -> with-jetty-websockets > * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] FELIX-6702 Make Jetty bundles EE version neutral [felix-dev]
paulrutter commented on PR #315: URL: https://github.com/apache/felix-dev/pull/315#issuecomment-2097615311 @cziegeler @enapps-enorman FYI, as discussed in https://issues.apache.org/jira/browse/FELIX-6701. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FELIX-6702) Make Jetty bundles EE version neutral
[ https://issues.apache.org/jira/browse/FELIX-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844172#comment-17844172 ] Paul Rütter (BlueConic) commented on FELIX-6702: See [https://github.com/apache/felix-dev/pull/315] > Make Jetty bundles EE version neutral > - > > Key: FELIX-6702 > URL: https://issues.apache.org/jira/browse/FELIX-6702 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter (BlueConic) >Priority: Major > > As discussed in FELIX-6701, this issue asks to make the jetty bundles EE > version neutral, to make it easier to migrate to newer EE versions in the > future. > Upgrade instructions once this PR is merged: > h1. When using Jetty 5.1.12 > * org.apache.felix.jakarta.ee9.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee9.websocket.enable -> > org.apache.felix.jetty.websocket.enable > h1. When using Jetty12 1.0.4 > * org.apache.felix.jakarta.ee10.websocket.enable -> > org.apache.felix.jakarta.websocket.enable > * org.apache.felix.jetty.ee10.websocket.enable -> > org.apache.felix.jetty.websocket.enable > Classifiers: > * with-jetty-ee10-websockets -> with-jetty-websockets > * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] FELIX-6702 Make Jetty bundles EE version neutral [felix-dev]
paulrutter opened a new pull request, #315: URL: https://github.com/apache/felix-dev/pull/315 See https://issues.apache.org/jira/browse/FELIX-6702. Jetty bundle * org.apache.felix.jakarta.ee9.websocket.enable -> org.apache.felix.jakarta.websocket.enable * org.apache.felix.jetty.ee9.websocket.enable -> org.apache.felix.jetty.websocket.enable Jetty12 bundle * org.apache.felix.jakarta.ee10.websocket.enable -> org.apache.felix.jakarta.websocket.enable * org.apache.felix.jetty.ee10.websocket.enable -> org.apache.felix.jetty.websocket.enable Classifiers: * with-jetty-ee10-websockets -> with-jetty-websockets * with-jakarta-ee10-websockets -> with-jakarta-websockets Updated unit tests and README.md to reflect these changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (FELIX-6702) Make Jetty bundles EE version neutral
Paul Rütter (BlueConic) created FELIX-6702: -- Summary: Make Jetty bundles EE version neutral Key: FELIX-6702 URL: https://issues.apache.org/jira/browse/FELIX-6702 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Paul Rütter (BlueConic) As discussed in FELIX-6701, this issue asks to make the jetty bundles EE version neutral, to make it easier to migrate to newer EE versions in the future. Upgrade instructions once this PR is merged: h1. When using Jetty 5.1.12 * org.apache.felix.jakarta.ee9.websocket.enable -> org.apache.felix.jakarta.websocket.enable * org.apache.felix.jetty.ee9.websocket.enable -> org.apache.felix.jetty.websocket.enable h1. When using Jetty12 1.0.4 * org.apache.felix.jakarta.ee10.websocket.enable -> org.apache.felix.jakarta.websocket.enable * org.apache.felix.jetty.ee10.websocket.enable -> org.apache.felix.jetty.websocket.enable Classifiers: * with-jetty-ee10-websockets -> with-jetty-websockets * with-jakarta-ee10-websockets -> with-jakarta-websockets -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FELIX-6701) Jetty12 EE11 preparation
[ https://issues.apache.org/jira/browse/FELIX-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844167#comment-17844167 ] Paul Rütter (BlueConic) commented on FELIX-6701: Created https://issues.apache.org/jira/browse/FELIX-6702 to track this. > Jetty12 EE11 preparation > - > > Key: FELIX-6701 > URL: https://issues.apache.org/jira/browse/FELIX-6701 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Paul Rütter >Priority: Major > > Jakarta EE 11 should be released within a couple of months, thus Jetty will > follow with a 12.1.x ([https://webtide.com/introducing-jetty-12/). > |https://webtide.com/introducing-jetty-12/).]Ideally, this will become a new > feature of the Jetty12 bundle. > What are the ideas to support this? > For the light bundle, i can imagine that the EE11 classes can be detected in > the classloader, like is done for websocket support. For the main jar, would > both EE10 and EE11 servlet classes be part of it? Or would we introduce new > classifiers for EE11 servlet? Probably, a new configuration option is needed > to specify the EE version to run. > These imports would be problematic if the EE10 classes are not available, > [https://github.com/apache/felix-dev/blob/517f9a0c89cad1866f315255568b40c568f5239d/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L34.] > > Just wondering how new (or existing 8/9, for that matter) EE specifications > would be part of the jetty12 bundle. Of course, we could already try it out > with EE9 as an exercise to ease transition to Jetty12. -- This message was sent by Atlassian Jira (v8.20.10#820010)
