[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sandesha-dev
Subject:    [jira] [Commented] (AXIS2-6051) Axis2 Future Roadmap in keeping up with new Java Versions
From:       "Artur Linhart (Jira)" <jira () apache ! org>
Date:       2023-03-12 6:59:50
Message-ID: JIRA.13515105.1671635037000.145136.1678604400235 () Atlassian ! JIRA
[Download RAW message or body]


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

Artur Linhart commented on AXIS2-6051:
--------------------------------------

As an experience of the long-year user of Axis2 I must say, we came on our projects \
to the final conclusion we have to remove completely the usage of Axis2 framework and \
replace it with Spring WS and one from the final reasons of this decision is the \
long-term lack of support of the jakarta.* libraries, since our business logic is \
based heavily on Spring and we have to move to newest Spring (6) version because of \
security reasons, in Spring 6 no old javax.* approach seems to be possible because a \
lot of conflicts coming from the parallel usage of jakarta.* and javax.* libraries in \
the same war file. I think, we will not be the only ones by this decision and it is \
unfortunate, Axis2 will from what I guess, really lose users in the long-term because \
this unfinished migration. I think, because of this operational risk, nobody will \
choose Axis2 in the today's versions for a new project.

> 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


[prev in list] [next in list] [prev in thread] [next in thread]