[jira] [Commented] (AXIS2-6051) Axis2 Future Roadmap in keeping up with new Java Versions

["Robert Lazarski (Jira)" <ji...@apache.org>]

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

Robert Lazarski commented on AXIS2-6051:
----------------------------------------

Tomcat 10 will run javax packages via the folder named  {{webapps-javaee. }}

This subject recently came up, see Axis2-6050.

AFAIK Tomcat does it via runtime byte code enhancement. But that won't work for long as new features go into jakarta.

The Apache Tom-ee project - which I don't use but know about from general Apache discussions - will be driving the Apache foundation as a whole to move to jakarta for support of EE 10 and MicroProfle 6.0.  That is because it has a lot of dependencies.

About JDK 17, my day job runs it exclusively and Axis2 1.8.2 runs fine on it.

Rampart will as well. My day job got all my time recently, but I will have some free time during the upcoming holidays and I am determined to get a release out asap, as my time allows.

 

> 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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org