jbpm.war does not deploy in JBoss 4.0.5.GA ------------------------------------------ Key: JBPM-772 URL: http://jira.jboss.com/jira/browse/JBPM-772 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM 3.1.3 Environment: JBoss 4.0.5.GA from jems-installer-1.2.0.BETA3.jar with EJB profile. Reporter: David Owens Assigned To: Tom Baeyens If you copy the jbpm.sar folder and the jbpm.war folder from the jbpm-3.1.3 starter kit into a JBoss 4.0.5.GA deploy directory, it will not deploy. You get this error message: 18:51:20,421 INFO [SchedulerThread] runtime exception while executing timers org.hibernate.HibernateException: Could not parse configuration: hibernate.cfg.xml at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1418) at org.hibernate.cfg.Configuration.configure(Configuration.java:1352) at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:90) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:68) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:90) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:74) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:78) at org.jbpm.persistence.db.DbPersistenceService.getSchedulerSession(DbPersistenceService.java:254) at org.jbpm.JbpmContext.getSchedulerSession(JbpmContext.java:529) at org.jbpm.scheduler.impl.SchedulerThread.executeTimers(SchedulerThread.java:104) at org.jbpm.scheduler.impl.SchedulerThread.run(SchedulerThread.java:71) Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1408) ... 10 more Which is caused by a ClassCastException from the SAXReader. After removing the dom4j-1.6.1.jar from jbpm.war\META-INF\lib the war will deploy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira