Order of process definitions for component org.jboss.seam.co

[appendix]

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

[norman.richards]

In a production application you should probably consider deploying process definitions directly to the database using the jbpm tools rather than using the developer convenience mechanism seam provides. You probably don't want new versions of the process created every time your redeploy the app or restart the app server.

[gavin.king]

In a production application you should probably consider deploying process definitions directly to the database using the jbpm tools rather than using the developer convenience mechanism seam provides.

Yes, definitely.

[appendix]

Thank you!
I didn't really see it as a pure convenience mechanism of seam (maybe there should be a hint in the documentation).

Unfortunately the issue described in the last paragraph of my initial post weren't resolved by using org.jbpm.ant.DeployProcessTask.
Anyway, I'll move on to the JBPM forum.

Thanks, Kurt