What exactly do you mean with task node with a subprocess?
thank you for your reply and please accept my apologies for mixing up a term. It is indeed not a task node, which cannot hold a sub-process, but a process-state-node as exemplified by the following snippet.
<process-state name="subProcessStateNode"> <sub-process name="childProcessName"></sub-process> <transition to="nextNode"></transition> </process-state>
The child as well as the parent process are persisted to the database, but the column _subprocessdefinition in the table jbpm_node doesn't hold a valid entry for the node "subProcessStateNode".
You must deploy first the subprocess and later deploy the process, i did it and work it fine.
I thought about that as well - and it would make sense, but I'm doing that already.
I'm using the ant deploy task:
<target name="deploy-process-definition"> <taskdef name="deploypar" classpathref="ant.classpath" classname="org.jbpm.ant.DeployProcessTask"> </taskdef> <deploypar cfg="resources/hibernate_ant.cfg.xml"> <fileset id="processDefinition" dir="resources/processDefinition"> <include name="subProcess.par" /> <!-- is referenced by the later --> <include name="superProcess.par" /> </fileset> </deploypar> </target>
Additionally I was using Seam build-in process deployment mechanism, but it lead to the same issues.
Is there a better way of deploying process descriptions without using ant?