Ad hoc controller exception java.lang.Exception: state2jrxml.js runtime ... "XML" is not defined.

Summary

Installing Tomcat from the Debian or RPM package can result in missing some required components, resulting in an XML is not defined exception.

Symptoms

In some Debian and RedHat environments, we've received reports of the ad-hoc editor throwing the following exception, despite a (seemingly) successful installation of JasperServer:

ad hoc controller exception

java.lang.Exception: state2jrxml.js runtime [135] "XML" is not defined.

at com.jaspersoft.ji.adhoc.service.AdhocEngineServiceImpl.generateJRXML(AdhocEngineServiceImpl.java:450)

at com.jaspersoft.ji.adhoc.service.AdhocEngineServiceImpl.saveARU(AdhocEngineServiceImpl.java:809)

at com.jaspersoft.ji.adhoc.action.AdhocAjaxController.save(AdhocAjaxController.java:565)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:616)

at org.springframework.web.servlet.mvc.multiaction.MultiActionController.invokeNamedMethod(MultiActionController.java:473)

at

Causes

In such cases, it was discovered that Tomcat was installed from a Debian package (or an RPM in RedHat environments), and some required components had not been included.

Resolutions

Users were able to correct this issue by installing Tomcat from a tarball obtained via the Apache web site instead, and deploying JasperServer within that installation.