• warning: DOMXPath::query(): Invalid expression in /var/www/ictedge/sites/all/modules/print/lib/dompdf-0.5.1/include/stylesheet.cls.php on line 573.
  • warning: DOMXPath::query(): Invalid expression in /var/www/ictedge/sites/all/modules/print/lib/dompdf-0.5.1/include/stylesheet.cls.php on line 573.
  • warning: Invalid argument supplied for foreach() in /var/www/ictedge/sites/all/modules/print/lib/dompdf-0.5.1/include/stylesheet.cls.php on line 575.

Diagnosing problems with builds

Submitted by ckelley on Wed, 12/30/2009 - 16:17

After deploying a new build, you may get a message from users that the system will not assign new id's. This indicates that the AJAX capabilities, provided by DWR, are not working. Install the deployed build on your dev system and test the main Patient Registration page, using Firebugs extension to log javascript errors. If the error "DWREngine is not defined" is displayed, then there is a good chance the jsp's did not properly pre-compile - in fact, engine2,jsp may not have been compiled or copied over all all.

DWR Egine error message

Also look for the following error in the tomcat logs (localhost.yyy-mm-dd.log) -

 Jun 16, 2008 10:49:50 AM org.apache.catalina.core.ApplicationContext log INFO: Marking servlet org.apache.jsp.js.engine2_jsp as unavailable
Jun 16, 2008 10:49:50 AM org.apache.catalina.core.ApplicationContext log  SEVERE: Error loading WebappClassLoader    
delegate: false    
repositories:      
/WEB-INF/classes/  
----------> Parent Classloader:  
org.apache.catalina.loader.StandardClassLoader@17f1ba3  
org.apache.jsp.js.engine2_jsp  java.lang.ClassNotFoundException: org.apache.jsp.js.engine2_jsp         
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)  

That code indicates that the engine2.jsp file was not compiled and/or copied over to the new build war.