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

Jeff Thomas commented on AXIS2-6051:
------------------------------------

Hi Robert, I am trying to catch up on your changes so far to the Axis2 for 
jakarta / new Axiom 2.0.0-SNAPSHOT..

A question... is the change in SoapEnvelopeImpl to 'createName(String, String)' 
correct? :) 

I had previously: 
{{return new PrefixedQName(uri, localName, null);}}
 
and your version has:
{{return null;}}
 
Not sure if this is related to some of the AXIS-6051 problems in the code 
comments?
---
 
There are some things I noticed to consider:

* Jakarta Servlet 6 Specification needs to be updated in all web.xml files
{code:java}
<web-app xmlns="https://jakarta.ee/xml/ns/jakartaee";
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
         xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee 
https://jakarta.ee/xml/ns/jakartaee/web-app_6_0.xsd";
         version="6.0">{code}

* Tomcat 10.1 required (which you have already switched to in 'clustering') - 
Servlet 6.0 Spec support ([https://tomcat.apache.org/whichversion.html)]


* Jetty 12.0 introduces Servlet 6.0 Spec support 
([https://eclipse.dev/jetty/download.php)]  - NOTE: The artifact names change 
here - see migration notes 
([https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-migration-11-to-12)]
 (EE9 to sync with Spring 6) - NOTE: artifact names on that page are wrong - 
one too many "jetty"s - correct as shown here
{code:java}
<dependency>
  <groupId>org.eclipse.jetty.ee9</groupId>
  <artifactId>jetty-ee9-webapp</artifactId>
  <version>${jetty.version}</version>
</dependency>
<plugin>
  <groupId>org.eclipse.jetty.ee9</groupId>
  <artifactId>jetty-ee9-maven-plugin</artifactId>
  <version>${jetty.version}</version>
</plugin>
<plugin>
  <groupId>org.eclipse.jetty.ee9</groupId>
  <artifactId>jetty-ee9-jspc-maven-plugin</artifactId>
  <version>${jetty.version}</version>
</plugin>{code}
 
I previously did the 10->11 migration which was no big deal...but I still have 
not cracked the 11->12 migration :( migrated tests but get 404 error in 
testkits during TestSuites
NOTE: Migration 11-> 12: * JettyServer replace HandlerList with 
ContextHandlerCollection)
 * New API Request/Response

 
Spring 5 to 6 for JEE9 and Jakarta Support 
([https://www.baeldung.com/spring-boot-3-spring-6-new#jakarta-ee-9)] - Axiom 
too? 
 
Cheers, Jeff

> 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: 1.8.3
>
>
> 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

Reply via email to