[
https://issues.apache.org/jira/browse/JSPWIKI-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508110#comment-17508110
]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-1170:
------------------------------------------------------
Having a separate parallel branch would be a PITA, javax.servlet package is
used throughout the entire application, so most modules would have to be kept
in sync :-/
As a workaround, Apache Tomcat provides a migration tool from javax to jakarta
namespace, perhaps we could use it through the maven exec plugin or whatever to
generate secondary artifacts for the public API and the main war, with a
jakarta namespace? Haven't used the tool myself, but maybe is worth a shot,
instead of having two separate branches, which will have to be in sync. Don't
know how it'll behave regarding dependencies, or what to do with the Dockerfile
or the portable binaries, though.
Regarding the public API, the getServletContext() method is always used to
retrieve a File/InputStream from the war, so perhaps we could deprecate that
method and provide a getInputStream( String file ) method or something like
that?
> Support of Jakarta EE 9
> -----------------------
>
> Key: JSPWIKI-1170
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1170
> Project: JSPWiki
> Issue Type: Improvement
> Reporter: Julien Gouesse
> Priority: Major
>
> Jakarta EE 9 drops the javax namespace for the jakarta namespace. Currently,
> JspWiki uses the former namespace, Engine.getServletContext() returns an
> instance of javax.servlet.ServletContext instead of
> jakarta.servlet.ServletContext. Why not providing a separate Maven artefact
> with the WAR and the JARs compatible with Jakarta EE 9 and keeping the
> current WAR and JARs in the default artefact to please everyone (which is
> what Hibernate and Wildfly do as far as I know) ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
