[
https://issues.apache.org/jira/browse/AXIS2-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656144#comment-17656144
]
Jeff Thomas commented on AXIS2-6051:
------------------------------------
Hi Robert, thanks for the answer :)
The current state of things with TomEE I think is TomEE 9 which is not yet
released and is based on the superceded Tomcat 10.0 level and a Jakarta EE 9
stack.
Unfortunately I haven't been able to find anything about plans for a TomEE
version which supports Tomcat 10.1 and Jakarta EE 10 - which would better align
with Spring 6.
I am a bit wary of relying on the bytecode migration tool from Tomcat since
Axis2 is just a part of our larger project - in my own tests at creating a
Jakartaized version of Axis 1.8 / Axiom 2 it is very tricky to get all the
puzzle pieces aligned. Also Jetty is not yet fully supporting the Jakarta EE
stack so a chunk of the integration tests must be disabled.
JDK 17 is probably about as far as we can currently take Axis2 because in JDK
19 the security manager is removed and I believe that there is a lot of Axis2
code that relies upon it.
Rampart unfortunately keeps falling farther behind. :( the Axis2 1.8.3-SNAPSHOT
(master) is now using Axiom 2 so I think Rampart has to catch up there as well.
> Axis2 Future Roadmap in keeping up with new Java Versions
> ---------------------------------------------------------
>
> Key: AXIS2-6051
> URL: https://issues.apache.org/jira/browse/AXIS2-6051
> Project: Axis2
> Issue Type: Wish
> Affects Versions: 1.8.0
> Reporter: Jeff Thomas
> Priority: Major
>
> Related to AXIS2-6035.
> Hi Robert/Andreas/Axis2 Support,
> just a general question about the realistic future of Axis2 (and by extension
> Axiom/Rampart) in keeping up with the quickly changing Java releases.
> We are getting a lot of push from our customers (and our own internal wish to
> use modern java features) to move to java 17+ ... we are hitting more and
> more walls with things like:
> * java modules
> * javax -> jakarta migration // this is a big one!
> ** jakarta.activation
> ** jakarta.validation
> ** jakarta.jms
> ** jakarta.mail
> ** jakarta.jws
> ** jakarta.jaxb
> ** ...
> * Tomcat 10 +
> * and related stuff like
> ** ActiveMQ Artemis (jakarta.jms)
> ** removal of SecurityManager in JDK 19+
> ** etc.
> The sort of general feeling is that unfortunately we are getting pulled
> towards a state of complete incompatibility between Axis2 and current
> supported JVMs / other Frameworks.
> Maybe you can give a bit of feedback about the roadmap for Axis2 and
> addressing the growing gap in dependencies? (and would welcome any info
> about Axiom/Rampart along the same lines). Good or bad news doesn't
> matter...would appreciate having some concrete statement to address our own
> internal planning about the way forward. :)
> Appreciate any info you can provide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
