Hello, I reported this as a concern about the default handling of NullPointerException a while back, but unfortunately it got no attention. I'd like to know what's the reason for this behavior, and maybe if it could be made configurable in the future. I'm copying the bug description here: Any exception that may happen during field evaluation (either direct field expression or scriptlet method) always propagate up the stack, aborting the report, except NullPointerException. It's obvious that all values should be tested for null, but the programmer may forget to do all the needed tests sometimes, or the data which was expected to exist is missing. Such situations that cause NPE's get silently evaluated to null. I don't know the reason behind this explicit exception swallow, but I'd like my reports to abort on any exception that may arise, including NPE's, and I dare to say that's what most programmers would expect (at least the Java ones, that may frequently deal with scriptlets, where such exceptions are far more likely). I'm currently running my local report tests on custom JasperReports 4.0.0 build with NPE catch blocks removed, no issues. I suggest the creation of new report option (probably report-wide), like 'When NullPointerException on evaluation', with values 'Evaluate to null' (default, to keep backward compatibility) and 'Propagate'. Bug URL, with sample report: http://jasperforge.org/projects/jasperreports/tracker/view.php?id=5203 Thanks!