Apparently using core:process-definitions in components.xml is a developers tool: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98430 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=90206 The above threads describe that when using <components ....> | <core:jbpm> | <core:process-definitions> | <value>jbpm/mytask/processdefinition.xml</value> | </core:process-definitions> | <core:pageflow-definitions></core:pageflow-definitions> | </core:jbpm> | </components> then org.jboss.seam.core.Jbpm#installProcessDefinitions() is called each time JBoss AS is started, and an additional copy of the definition is inserted into the database even when the deployed EAR has not changed. Note that jBPM is not to be expected to check for actual changes when deploying a process; in "it's the user's code that should call the jbpmContext.deployProcessDefinition()". But... why is this considered to be a development tool? Wouldn't using jBPM with Seam be much easier if there is a common way to deploy processes? If not using core:process-definitions then maybe by embedding the jBPM web-console's org.jbpm.webapp.servlet.ProcessUploadServlet (/jbpm-console/upload or /jbpm/deployprocess)? Just curious... Arjan. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027098#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...