User development, A new message was posted in the thread "Upgrade from JBPM3 to JBPM4 woes": http://community.jboss.org/message/523982#523982 Author : Ronald van Kuijk Profile : http://community.jboss.org/people/kukeltje Message: --------------------------------------------------------------   As mentioned in some blogs (and some docs to, not sure), the way of interacting with jBPM changed a lot. Instead of knowing the internal model, you are supposed to interact with the engine through services.     This is only partly true. ActivityBehaviour is for implementing custom nodes (als you could in jBPM3). ActionHandlers were used in more places than this. ContextInstance can also not be 1:1 mapped toActivityExecution, but in some places it is the replacement (from my head)     The JbpmTemplate has been broken for several years. It has never been compatible with 3.2 and to be honest, it provided little advantage (just like at the time the HibernateTemplate provided little advantage).   Wanna use 4? Use the Spring integration provided by 4. Do *not* try to (ab)use the old spring template. Migration of this is unfortunately a manual task.   Cheers,   Ronald -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/523982#523982