Bug 44787 - provide more error context on "java.lang.IllegalStateException: No Java compiler available"
Summary: provide more error context on "java.lang.IllegalStateException: No Java compi...
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 6
Classification: Unclassified
Component: Jasper (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: default
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-09 07:55 UTC by Ralf Hauser
Modified: 2017-05-30 08:51 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
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