Note that there are some explanatory texts on larger screens.

plurals
  1. POJetty/ jasper JSP compilation exception, no stacktrace
    text
    copied!<p>I have a problem on my production machine (ubuntu oneiric) with the compilation of included JSP files. When loading a page, the following exception is logged in the output log;</p> <pre><code>2012-03-12 10:48:28.295:INFO:oejs.AbstractConnector:Started SelectChannelConnect or@0.0.0.0:23458 STARTING Mar 12, 2012 10:48:53 AM org.apache.jasper.compiler.Compiler generateClass SEVERE: Error compiling file: /tmp/jetty-0.0.0.0-23458-basej-_-any-/jsp/org/apac he/jsp/WEB_002dINF/classes/apps/aco/templates/header_jsp.java 10:48:53,880 INFO root:50 - [index/index] executeTime : 2958ms 2012-03-12 10:48:53.886:WARN:oejs.ServletHandler:/ java.lang.NullPointerException at core.helpers.BaseJSP.include(BaseJSP.java:52) </code></pre> <p>EDIT:</p> <p>The code which includes the JSP file;</p> <pre><code> if (BaseFile.exists(delegate.getTemplate())) { try { // MZ: Pass the current object as model delegate.getRequest().setAttribute("object", delegate.getRenderObject()); JspRuntimeLibrary.include(delegate.getRequest(), delegate.getResponse(), delegate.getTemplate(), delegate.getWriter(), false); // MZ: Dispatcher succeeded return true; } catch (Exception e) { // MZ: Nested template exception, should be rethrown Logger.info("Dispatcher error: " + e.getMessage() + " " + delegate.getRenderObject().getClass().getSimpleName() + " in template: " + delegate.getTemplate(), e); throw new BaseException("Dispatcher error: " + e.getMessage() + " " + delegate.getRenderObject().getClass().getSimpleName() + " in template: " + delegate.getTemplate()); } } return false; } </code></pre> <p>(The actual inclusion is done via JspRuntimeLibrary.include).</p> <p>The code worked fine before, but it may have to do with adding the lombok jar, and removing the getters and setters from several entities. In my development environment (windows) the jsp compiles without any problem.</p> <p>How do i get jetty/ jasper to print out the stacktrace/ debug information ?</p> <p>Thanks, Marius</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload