[
https://issues.apache.org/jira/browse/FELIX-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843678#comment-17843678
]
Paul Rütter (BlueConic) commented on FELIX-6701:
------------------------------------------------
I'm not sure if i follow; when Jetty 12 would release EE11 support, and Felix
HTTP uses that new Jetty version, the current codebase will still use EE10.
Unless the dependency on
[https://mvnrepository.com/artifact/org.eclipse.jetty.ee10/jetty-ee10-servlet]
would get replaced with jetty-ee11-servlet, and the code would start using ee11
[https://github.com/apache/felix-dev/blob/517f9a0c89cad1866f315255568b40c568f5239d/http/jetty12/src/main/java/org/apache/felix/http/jetty/internal/JettyService.java#L34.]
as well.
But that would mean that using a new Felix Jetty12 version would automatically
"upgrade" one to EE11, which i don't think is desired.
Also, having properties like `org.apache.felix.jetty.ee10.websocket.enable`
doesn't make sense.
Since Jetty 12 can handle multiple EE versions, i think it would make more
sense to accomodate this in the Jetty12 bundle and leave it up to the consumer
to specify which EE version to use. But that would require some code changes i
would assume.
What do you think?
> 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)
