[
https://issues.apache.org/jira/browse/AXIS2-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542537#comment-17542537
]
Robert Lazarski commented on AXIS2-6035:
----------------------------------------
The problem here is that Tomcat is way ahead of a lot of upstream dependencies
that are not ready yet.
Axis2 has a lot of dependencies so we can't do much but wait.
For example, I tried to run Jenkins on Tomcat 10 recently and it wasn't even
close to being ready.
That being said, I think we can shoot for 1.9 being compatible with Tomcat 10
but that is unlikely going to happen this year. I edited the issue for a 1.9
time frame.
> Axis2 libraries not compatible with Tomcat 10
> ---------------------------------------------
>
> Key: AXIS2-6035
> URL: https://issues.apache.org/jira/browse/AXIS2-6035
> Project: Axis2
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.8.0
> Reporter: Raj
> Priority: Major
>
> Apache Tomcat 10 supports the Jakarta Servlet 5.0, Jakarta Server Pages 3.0,
> Jakarta Expression Language 4.0, JakartaWebSocket 2.0 and Jakarta
> Authentication 2.0
> [specifications|https://cwiki.apache.org/confluence/display/TOMCAT/Specifications].
> There is a significant breaking change between Tomcat 9.0.x and Tomcat
> 10.0.x. The Java package used by the specification APIs has changed from
> javax... to jakarta.... It will be necessary to recompile web applications
> against the new APIs.
>
> axis2 libraries need to use jakarta packges to support tomcat 10. Not sure if
> there is already a bug for this. Can you please review this and provide an
> update if this is already work in progress and provide me estimated release
> time
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
