[JBoss jBPM] - Re: Deploying jbpm.war(3.1.3) to jboss as 4.0.5GA
by contactnagesh
I have downloaded 3.1.3. It works fine now. Below are the steps I have followed.
1. Download Jbpm 3.1.3 complete kit from the location.
http://sourceforge.net/projects/jbpm/files/
2.get <kit 3.1.3> jbpm-server\server\jbpm\deploy jbpm.war and jbpm.sar copy them to Jboss.4.0.5\default\deploy folder.
3. start the server with run.bat
4. Hitting the hibernate configuration error .
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.getMessagingSession(DbPersistenceService.java:235)
at org.jbpm.JbpmContext.getMessagingSession(JbpmContext.java:521)
at org.jbpm.msg.db.DbMessageService.(DbMessageService.java:49)
at org.jbpm.msg.db.DbMessageServiceFactory.openService(DbMessageServiceFactory.java:32)
at org.jbpm.svc.Services.getService(Services.java:136)
at org.jbpm.svc.Services.getMessageService(Services.java:172)
at org.jbpm.msg.command.CommandExecutorThread.executeCommand(CommandExecutorThread.java:112)
at org.jbpm.msg.command.CommandExecutorThread.run(CommandExecutorThread.java:79)
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)
... 14 more
5. I have removed the dom4j-1.6.1 from the jbpm.war file and redeployed again.
6. start the server with run.bat.
Now the server started successfully with jbpm examples.
[ Show ]
Nageswara Rao Chilakala added a comment - 22/Jul/09 02:32 AM - Visible to jira-users I have also tried with the Jbpm 3.1.2 . I was hitting the below exception. I have downloaded 3.1.3. It works fine now. Below are the steps I have followed. 1. Download Jbpm 3.1.3 complete kit from the location. http://sourceforge.net/projects/jbpm/files/ 2.get <kit 3.1.3> jbpm-server\server\jbpm\deploy jbpm.war and jbpm.sar copy them to Jboss.4.0.5\default\deploy folder. 3. start the server with run.bat 4. Hitting the hibernate configuration error . 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.getMessagingSession(DbPersistenceService.java:235) at org.jbpm.JbpmContext.getMessagingSession(JbpmContext.java:521) at org.jbpm.msg.db.DbMessageService.(DbMessageService.java:49) at org.jbpm.msg.db.DbMessageServiceFactory.openService(DbMessageServiceFactory.java:32) at org.jbpm.svc.Services.getService(Services.java:136) at org.jbpm.svc.Services.getMessageService(Services.java:172) at org.jbpm.msg.command.CommandExecutorThread.executeCommand(CommandExecutorThread.java:112) at org.jbpm.msg.command.CommandExecutorThread.run(CommandExecutorThread.java:79) 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) ... 14 more 5. I have removed the dom4j-1.6.1 from the jbpm.war file and redeployed again.
6. start the server with run.bat. Now the server started successfully with jbpm examples.
Please contact me if you have any deployment issues with Jbpm 3.1.3 and Jboss 4.0.5
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245187#4245187
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245187
16 years, 8 months
[JBoss jBPM] - Re: Due Date and End Date of a Task.
by shekharv
Due date signifies when a task is to be completed by. So if you have Task1 out there with Due Date for tomorrow, then it just means that it is to be done tomorrow.
Just like homework, due tomorrow, but might be submitted late, day after tomorrow. So just because a task is due in a day does not mean that it WILL be completed in a day.
End date is set when the task actually completes, or is done. This is typically set by jBPM when it is completed. Just setting the end Date would not mean that the task is completed. This is because Tasks are part of workflow, and other things need to happen on the execution level that need to be taken care of, like advancing to the next node, etc.
Do setting the end task is probably not recommended, and would not achieve much.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245183#4245183
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245183
16 years, 8 months