Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Problem with JSTL and Jetty running under OSGI

9.3.0 is very old now. (the entire 9.3.x series is on security maintenance atm and isn't being updated anymore)

There are a number of quirks throughout the 9.3.0 series related to JSTL and the need (or not) for the WEB-INF/lib/ to contain the appropriate jstl jar files (or not).
The 9.4.x series on the other hand is much cleaner in this regard.  Have you tried a more recent / stable version of Jetty?

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Wed, Jan 16, 2019 at 11:00 AM Tom Hoffman <purduetom90@xxxxxxxxx> wrote:
I'm using version jetty-9.3.0.v20150612 in an OSGI environment, with v2.5 of the Servlet specification. I've inherited a mass/mess of old Java Servlet code that works, that is replete with security issues. I'm trying to address some of the XSS issues by using JSTL. I've added the required JSTL directive at the top of the JSP files: 

 <%@ taglib uri="" prefix="c" %>

But when I first access this jsp page, it fails and I see the following in the error log: 

2019-01-08 20:44:44,606 qtp1697835528-134 WARN org.eclipse.jetty.servlet.ServletHandler -   org.apache.jasper.JasperException: /jsp/applicationsChoice.jsp(1,63) PWC6188: The absolute uri: cannot be resolved in either web.xml or the jar files deployed with this application
        at org.apache.jasper.compiler.DefaultErrorHandler.jspError(

I've seen many old references that suggest there was at one point in time issues with JSTL and the Jetty 9.x release. Is this old information? Can someone supply a pointer or two?

Tom Hoffman

jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top