Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] NPE due to EL 3 - <c:if test="{nonExisting}> ?

I manually patched  javax.servlet.jsp-2.3.2.jar   which was in Jetty 9.1.3.   to work around this issue.   In Jetty 9.2 I believe they will switch from glassfish to tomcat for these classes.

I could supply the patched jar it if thats the same version as in jetty 9.1.4...   

On 10/04/2014 11:16 am, "Fritz Richter" <fritz@xxxxxxxxxxxx> wrote:
Hi together,
after updating the Jetty to the newest 9.1.4 version, in order to support my Spring4/Java 8 web app, I run into a strange NPE problem. 

I get this error:
	at org.apache.jasper.runtime.HttpJspBase.service(
	at javax.servlet.http.HttpServlet.service(
	at org.apache.jasper.servlet.JspServletWrapper.service(
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(

If I am right, the problem is the el-3 library, which will treat null values in a different way. I found some issues in bug tracking systems for Tomcat, Glassfish and even in Jetty – but I was not able to figure out, how to solve this problem. 

I want to avoid writing: 
<c:if test=„${not empty nonExisting && nonExisting}“>

Is there anything I can do in order to not modify the existing JSP files?


jetty-users mailing list

Back to the top