You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Juan Pablo Santos RodrÃguez (Jira)" <ji...@apache.org> on 2024/12/19 22:25:00 UTC
[jira] [Commented] (JSPWIKI-1170) Support of Jakarta EE 9
[ https://issues.apache.org/jira/browse/JSPWIKI-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907214#comment-17907214 ]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-1170:
------------------------------------------------------
https://github.com/weberjn/jspwiki/tree/jakarta has now been merged into https://github.com/apache/jspwiki/tree/jakarta. Thanks [~weberjn] for all the work that's been put into this!
Tests are passing now, but xmlrpc issue still persists, we still have to decide what to do with it.
> 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
> Attachments: jakarta-1.patch, jakarta.patch, jspwiki.zip
>
>
> 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.10#820010)