Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-2460

sub-process name is not resolved upon deployment with the jbpm-console

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jBPM 3.2.7
    • jBPM 3.2.6.SP1, jBPM 3.2.5.SP5
    • Console
    • None

      Using the upload process function of the jbpm-console web app, deploy two processes with a parent-child relationship through a process-state node:

      1. childprocess.par

      <process-definition name="child">
      [...]
      </process-definition>

      2. parentprocess.par

      <process-definition name="parent">
      [...]
      <process-state name="process-state1">
      <sub-process name="child" />
      <transition to="end"></transition>
      </process-state>
      [...]
      </process-definition>

      After the two processes are deployed, the relation from the parent-process to the child-process is not properly set in the database:

      mysql> select ID_, NAME_, SUBPROCNAME_, SUBPROCESSDEFINITION_ from JBPM_NODE where CLASS_ = 'C';
      ----------------------------------------------------+

      ID_ NAME_ SUBPROCNAME_ SUBPROCESSDEFINITION_

      ----------------------------------------------------+

      78 process-state1 NULL NULL

      ----------------------------------------------------+
      1 row in set (0.00 sec)

      This is due to the fact that the jbpm4jsf part initializes the JbpmContext after the processdefinition.xml file is parsed, therefore the call to DbSubProcessResolver.findSubProcess returns null.

              aguizar_jira Alejandro Guizar (Inactive)
              rhn-support-mputz Martin Weiler (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: