[ 
https://issues.apache.org/jira/browse/CAMEL-17136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497395#comment-17497395
 ] 

Vladimir V. Bychkov commented on CAMEL-17136:
---------------------------------------------

Updating to Jakarta EE 8 seems not a big Probem. But man usable software 
products are not yet compatible with Jakarta EE 9/9.1. For example ActiveMQ has 
limited support of JEE 9 (now only [ActiveMQ Artemis Jakarta 
Client|https://blogs.apache.org/activemq/entry/activemq-artemis-embraces-jakarta-ee]).
 Spring Framework [declares 
support|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6]
 in Version 6.
Jetty supports JEE 9 starting with [Version 
11|https://containerjournal.com/features/jetty-project-embraces-jakarta-ee-9-specification/],
 but in Jett 10 Continuation support was removed. Continuation is used for 
example in 
[camel-jetty-common|https://github.com/apache/camel/blob/main/components/camel-jetty-common/src/main/java/org/apache/camel/component/jetty/CamelContinuationServlet.java#L165].
So, updating to Jakarta EE 9 seems (in common) impossible, but to Jakarta EE 8 
-- I want do this, if you have nothing against.

> Upgrade to Jarkarta EE APIs 
> ----------------------------
>
>                 Key: CAMEL-17136
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17136
>             Project: Camel
>          Issue Type: Dependency upgrade
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 3.x
>
>
> After the 3.14.x LTS release and when we drop Java 8, then it would be a good 
> time to migrate to Jakarta EE APIs.
> We should look at Spring Boot and Quarkus if they are supporting these newer 
> APIs as well or not. And then align when they are ready.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to