Hi, I'm using a process definition (parent.jpdl.xml) which contains a task node with a sub-process (child.jpdl.xml) with seam. The Jbpm component is configured in components.xml: | <component class="org.jboss.seam.core.Jbpm"> | <property name="processDefinitions"> | child.jpdl.xml | parent.jpdl.xml | </property> | </component> | I realized that it's crucial that all child process definitions are listed before the process definition of any parent process, since Seam is deploying the process definitions in the order they are listed in components.xml. I just wonder, if this is the desired behavior or if more sophisticated deployment strategies are planned or already implemented? Additionally the nodes of the parent process are not deployed completely correct, since both process definitions are persisted within one database transaction and therefore the parent process cannot refer to the child process for its nodes, but this looks like an jbpm/hibernate issue. Any comments on that? Thanks, Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987525#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...