Bug 44787

Summary: provide more error context on "java.lang.IllegalStateException: No Java compiler available"
Product: Tomcat 6 Reporter: Ralf Hauser <hauser>
Component: JasperAssignee: Tomcat Developers Mailing List <dev>
Status: RESOLVED FIXED    
Severity: enhancement CC: arminha
Priority: P2    
Version: unspecified   
Target Milestone: default   
Hardware: PC   
OS: Linux   

Description Ralf Hauser 2008-04-09 07:55:20 UTC
when manually attempting to pre-compile jsp pages, I get on debian etch 

  [jasper2] java.lang.IllegalStateException: No Java compiler available
  [jasper2]     at org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:224)
  [jasper2]     at org.apache.jasper.JspC.processFile(JspC.java:979)
  [jasper2]     at org.apache.jasper.JspC.execute(JspC.java:1135)

There appear to be 2 method variants to do this:

a) Compiler createCompiler(String className) doesn't bother to say which 
"className" it was looking for in case of a failure
b) nor does it volunteer to cite the classpath it was looking for the org.apache.jasper.compiler.JDTCompiler or org.apache.jasper.compiler.AntCompiler (or the one specified in the "options" in the future)
Comment 1 Mark Thomas 2008-04-09 14:35:31 UTC
Patches are always welcome.
Comment 2 Mark Thomas 2017-05-30 08:51:48 UTC
Fixed in:
- trunk for 9.0.0.M22 onwards
- 8.5.x for 8.5.16 onwards
- 8.0.x for 8.0.45 onwards
- 7.0.x for 7.0.78 onwards