Grouper Users - Open Discussion List

["Bryan E. Wooten" <>]

That’s what we are going to do. This is not that big a deal for us. I was just curious if someone else had run into this and had any easy fix.

 

Thanks,

 

Bryan

 

From: Chris Hyzer [mailto:]
Sent: Tuesday, April 08, 2014 11:38 AM
To: Bryan E. Wooten;
Subject: RE: Tomcat 7 for UI?

 

Can you have multiple tomcats on one machine (e.g. fronted by an apache with one domain name), and Grouper can use tomcat6?  I think when you bounce a tomcat, or redeploy an app, or if an app runs out of memory, you don’t want to affect other apps.

 

I haven’t looked at tomcat7 for Grouper yet, if we can wait until 2.3 then we don’t have to worry about the admin UI if it goes away J

 

Chris

 

From: [] On Behalf Of Bryan E. Wooten
Sent: Tuesday, April 08, 2014 1:31 PM
To:
Subject: [grouper-users] Tomcat 7 for UI?

 

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:

 

https://tomcat.apache.org/migration-7.html#Servlet_3.0_API

 

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:

<>

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

 

Thanks,

Bryan