Jeff Thomas created AXIS2-6088:
----------------------------------

             Summary: JSTL Imports not migrated to Jakarta / double dependency
                 Key: AXIS2-6088
                 URL: https://issues.apache.org/jira/browse/AXIS2-6088
             Project: Axis2
          Issue Type: Bug
          Components: modules
    Affects Versions: 2.0.0
            Reporter: Jeff Thomas
         Attachments: image-2025-03-22-10-48-10-594.png

In some JSPs in "modules/pwc-webapp/src/main/webapp/WEB-INF/viiews/admin" the 
JSTL imports have not been switched to jakarta.

i.e. 'listServices.jsp'
{code:java}
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %> {code}
with Jakarta this should be:
{code:java}
<%@ taglib prefix="c" uri="jakarta.tags.core" %> {code}
It looks like both required dependencies are present:
{code:java}
<dependency><!-- Not required for the Maven build, but necessary to avoid 
errors when importing the project into an IDE. -->
    <groupId>jakarta.servlet.jsp</groupId>
    <artifactId>jakarta.servlet.jsp-api</artifactId>
    <version>4.0.0</version>
    <scope>provided</scope>
</dependency> 
<dependency>
    <groupId>jakarta.servlet.jsp.jstl</groupId>
    <artifactId>jakarta.servlet.jsp.jstl-api</artifactId>
    <version>3.0.2</version>
</dependency>
<dependency>
    <groupId>org.glassfish.web</groupId>
    <artifactId>jakarta.servlet.jsp.jstl</artifactId>
    <version>3.0.1</version>
</dependency>{code}
The "jsp-api" dependency is present 2x and the 4.0.0 version doesn't belong I 
{*}think{*}:

Jakarta EE 10 uses JSTL 3.0 (currently 3.0.2):
[https://jakarta.ee/release/10/]

JSTL 4.0.0 is intended for Jakarta EE 11
[https://jakarta.ee/specifications/pages/4.0/]


!image-2025-03-22-10-48-10-594.png|width=919,height=264!



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