Child pages
  • Tips for cleaning up org.apache.jasper.compiler.Parser issues
Skip to end of metadata
Go to start of metadata

It was decided for 2.9 that we'd *like* to try to clean up the 2 org.apache.jasper.compiler.Parser required workarounds that we have in Sakai if the time and scripts are available to do so.

In order to do this we'll need:

  • Some type of script (regex) to find all of the files that have these issues in them
  • Someone to go in and manually (or maybe automatically) fix the problems
  • People to test that the tools still function correctly and no other issues are present. If there are still problems, the scripts that detect issues may need to be updated.

These 2 workarounds are mentioned on Install Tomcat 7 / 8:


  • This was introduced in Tomcat 7.0.5
  • The bug that references this is:
  • Summary: "Enforce the rules in the JSP specification for parsing the attributes of custom
    and standard actions that require that the attribute names are unique within an
    element and that there is whitespace before the attribute name."
    Bad: <% @include file="/jsp/discussionForum/includes/dfAreaInclude.jsp"%>
    Good: <%@ include file="/jsp/discussionForum/includes/dfAreaInclude.jsp"%>

Bad: <eg:foo att1="1"att2="2"att3="3">
Good <eg:foo att1="1" att2="2" att3="3">

  • No search and replace suggested yet


Bad: <mytags:tag value="<%= "hi!" %>" /> (Double outside, double inside)
<mytags:tag value='<%= "hi!" %>' /> (Single outside, double inside)
<mytags:tag value="<%= \"hi!\" %>" /> (Double outside, escaped double inside)
<mytags:tag value='<%= \"name\" %>' /> (Escaped double inside, single outside)

  • No labels

1 Comment

  1. Matt, did you do any work on this?