[
https://issues.apache.org/jira/browse/AXIS2-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895902#comment-17895902
]
Christian Ortlepp commented on AXIS2-6051:
------------------------------------------
I did some work on the following Issues:
* https://issues.apache.org/jira/browse/AXIS2-6054
* https://issues.apache.org/jira/browse/AXIS2-6044
* https://issues.apache.org/jira/browse/AXIS2-6043
* https://issues.apache.org/jira/browse/AXIS2-6042
* https://issues.apache.org/jira/browse/AXIS2-6041
* https://issues.apache.org/jira/browse/AXIS2-6040
Since most of these Issues were created a long time ago I don't think that we
will get any feedback from the original authors. [~robertlazarski] maybe you
can provide some feedback if/when you find the time.
Furthermore, I think that AXIS-5689 is not really actionable since they did not
attach the actual report, and the information that was provided is quite
sparse. Also since it has been created almost 10 years ago I think it is save
to say that we will not get this report anymore.
I'll try to look into the Intellij Plugin Issue later, most other issues
unfortunately require more knowledge of SOAP/Axis than I possess at the moment.
[~cskpsp] as I understand [~robertlazarski] this Issue mostly depends on
Rampart and the other outstanding issues being fixed before the 2.0.0. There is
nothing one really can do to progress this specific issue, we can only try to
advance the 2.0.0. release as a whole. If you want to help with that, feel free
to contribute or provide feedback on any of those outstanding issues.
> 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
> Assignee: Robert Lazarski
> Priority: Major
> Fix For: 2.0.0
>
>
> 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
