Description of problem: The hibernate.cfg.xml for war distributions for tomcat-7 is different from the one for jbossas7 and was8. The JNDI name say "java:comp/env/jdbc/jbpm" for tomcat. But say "java:comp/env/jdbc/dashbuilder" for others. And the configuration is also inconsistent since the hibernate.cfg.xml is maintain in dashbuilder project. Two hibernate.cfg.xml jbpm-dashboard/jbpm-dashboard-distributions/src/main/tomcat7/WEB-INF/etc/hibernate.cfg.xml dashboard-builder/modules/dashboard-webapp/src/main/webapp/WEB-INF/etc/hibernate.cfg.xml So I think we might need to remove such differencies. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fixed. No need for having a different data source name on Tomcat. The tomcat's specific hibernate.cfg.xml has been removed and the data source name has been changed to "jdbc/dashbuilder" in order to be consistent with all the other assemblies. Github commit (master): https://github.com/droolsjbpm/jbpm-dashboard/commit/8076f9f0c487e9dd556e639ecd2e6bfea66a0a0a Github commit (6.2.x): https://github.com/droolsjbpm/jbpm-dashboard/commit/15b87252b62109dde5bd932217b3d7cf6e252df6
Ok, verified with BPM Suite 6.1.0 ER3. Dashbuilder now uses single hibernate.cfg.xml across all distributions.