yes my bad.
something i fixed. i only ran the unit test suite without building the webapp.
i'll fix it right away.
Awesome :) I'll look for what the patch was - I figured it must be something simple, my workaround was to put an evil hack in the code.
My current challenge is around this:
Caused by: org.hibernate.TransactionException: Could not register synchronization for container transaction at org.hibernate.transaction.CMTTransaction.begin(CMTTransaction.java:45) at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1236) at org.jbpm.persistence.db.DbPersistenceService.beginTransaction(DbPersistenceService.java:105) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:97) at org.jbpm.persistence.db.DbPersistenceService.getTaskMgmtSession(DbPersistenceService.java:276) at org.jbpm.JbpmContext.getTaskMgmtSession(JbpmContext.java:441) at org.jbpm.JbpmContext.getTaskList(JbpmContext.java:188) at org.jbpm.webapp.bean.ParticipantBean.getPersonalTaskInstances(ParticipantBean.java:22)
Are you seeing these?
That's my bad...I'll check in the new hibernate file to remove the CMT attributes.
i've beat you to it :-)
in my env, the web app is working again. the NoClassDefFoundError (i hate those:-), the ant target configuration problem and the CMT stuff are updated in CVS.
let me know if you experience any other problems.
i'll only be able to look at them tomorrow cauzzz i'm gnggg tzz zzzzzzzzzzzzzzzzzzzzzzzz
Looks like Tom already fixed it...thanks Tom. I didn't realize until today that the CMT config won't work with the webapp.
no prob. keep it up.
in the restructuring, i'll give some thought on how we can support multiple variations of these configurations without having to maintain them all.
any ideas in this regard is appreciated