[
https://issues.apache.org/jira/browse/FELIX-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843684#comment-17843684
]
Paul Rütter (BlueConic) commented on FELIX-6701:
------------------------------------------------
Hmm, ok, then i misunderstood earlier. Then it would have been better to name
the configuration option for websockets
`org.apache.felix.jetty.websocket.enable` and
`org.apache.felix.jakarta.websocket.enable`. and the classifiers
`with-jetty-websockets` and `with-jakarta-websockets` instead.
That way, no additional configuration would be needed when Felix HTTP Jetty 12
would upgrade to EE11, except for users of the light bundle (which of course
would need to include the EE11 bundles instead of EE10).
Should we change this in a new release?
> 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)
