Community
Participate
Working Groups
The old version of Apache Jasper we used in Juno M3 and earlier, had a copy of JDT's compiler embedded in the bundle (ECJ). The new apache jasper glassfish bundle in Juno M4 does not. One consequence of this is that JSP's won't compile using server-side Equinox unless JDT core or ECJ is present. We should look at whether this is necessary, and if so make sure it is documented in the migration guide so people are aware they need to add the extra bundle in their server setup.
See http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/tree/bundles/org.eclipse.equinox.jsp.jasper/src/org/eclipse/equinox/internal/jsp/jasper/Activator.java Currently the following code is in the activator when it starts: //disable the JSR99 compiler that does not work in OSGi; //This will convince jasper to use the JDTCompiler that invokes ecj (see JSP-21 on the glassfish bug-tracker) System.setProperty("org.apache.jasper.compiler.disablejsr199", Boolean.TRUE.toString()); This is rather scary since it is a global flag. I was hopeful that disabling it when running on Java 6 might allow org.apache.jasper.glashfish to actually use the jsr199 from the vm implementation but it did not seem to work for me.
Here is the glassfish work item: http://java.net/jira/browse/JSP-21 According to this it was resolved in May 2011. So maybe the next version of org.apache.jasper.glassfish will resolve this. For more situation I will resort to including ECJ.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
