Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Tomcat 7 for UI?

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Tomcat 7 for UI?

Chronological Thread 
  • From: "Bryan E. Wooten" <>
  • To: "" <>
  • Subject: [grouper-users] Tomcat 7 for UI?
  • Date: Tue, 8 Apr 2014 17:31:27 +0000
  • Accept-language: en-US

So I tried to deploy the Grouper UI on Tomcat 7 (My co-worker needs Tomcat 7 for his app and we are sharing a test VM) and ran into some issues.


ServletException in '/WEB-INF/jsp/dynamicTile.jsp': JasperException:/WEB-INF/jsp/dynamicTile.jsp (line: 34, column: 6) "${uiException.class.simpleName}" contains invalid _expression_(s): javax.el.ELException: Failed to parse the _expression_ [${uiException.class.simpleName}]

org.apache.jasper.JasperException: /WEB-INF/jsp/dynamicTile.jsp (line: 34, column: 6) "${uiException.class.simpleName}" contains invalid _expression_(s): javax.el.ELException: Failed to parse the _expression_ [${uiException.class.simpleName}]


This seems to be related to this:


Servlet 3.0 API

Apache Tomcat 7 supports Java Servlet 3.0, JavaServer Pages 2.2 and _expression_ Language 2.2 specifications. The changes between versions of specifications may be found in the Changes appendix in each of specification documents.

In JSP pages that use wildcard import syntax the new classes added in Servlet API may conflict with ones in web applications. For example, if package "a" contains class Part, the following JSP page will cease to compile in Tomcat 7:

<%@page import="a.*"%>
<% Part page = new Part(); %>

That happens because implicit import of javax.servlet.http.* and explicit import of a.* will provide conflicting definitions of class Part that was added in Servlet 3.0. The solution is to use explicit import, import="a.Part".


I see that the include.jsp used by the dynamicTile.jsp uses wild cards.

Is there a fix for this? Or an easy work around?





Archive powered by MHonArc 2.6.16.

Top of Page