Bug 779021 (SOA-1433)

Summary: sub-process name is not resolved upon deployment with Eclipse or ant-task
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Toshiya Kobayashi <tkobayas>
Component: JBPM - within SOAAssignee: Julian Coleman <jcoleman>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP01   
Target Milestone: ---   
Target Release: 4.3 CP02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1433
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-11 11:18:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Toshiya Kobayashi 2009-08-11 14:58:12 UTC 
Affects: Release Notes
Date of First Response: 2009-08-12 06:42:50
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/326994
project_key: SOA

If you omit binding attribute for <sub-process> in <process-state> and deploy the process definition with Eclipse or org.jbpm.ant.DeployProcessToServerTask, resolving sub-process will fail. When you run the parent process with jbpm-console after the deployment, jbpm-console will show -- "org.jbpm.JbpmException" was thrown. The message is: can't create a process instance when processDefinition is null --

ProcessUploadServlet calls jbpmConfiguration.createJbpmContext() after parsing and before deploying. If jbpmContext is not created before parsing, sub-process won't be resoleved(the call to DbSubProcessResolver.findSubProcess returns null.). So the default behaviour of binding attribute(parse time resolving) will fail.

This is almost the same issue as SOA-1427. But different use case (Eclipse / ant-task) and different class (org.jbpm.web.ProcessUploadServlet)
Comment 1 Toshiya Kobayashi 2009-08-11 15:45:42 UTC 
Link: Added: This issue incorporates JBPM-2475
Comment 2 Toshiya Kobayashi 2009-08-12 04:52:28 UTC 
In addition, DeployProcessTask has the same problem. org.jbpm.ant.DeployProcessTask should be fixed, too.
Comment 3 Julian Coleman 2009-08-12 10:42:50 UTC 
Resolved in revision 3555 (4.3 branch) of:
  build-tools/builders/soa/p-consoles/jbpm/resources/jbpm-2460
  build-tools/builders/soa/p-consoles/jbpm/resources/jbpm-2460/DeployProcessActionListener.java
  build-tools/builders/soa/p-consoles/jbpm/resources/jbpm-2475
  build-tools/builders/soa/p-consoles/jbpm/resources/jbpm-2475/ProcessUploadServlet.java
  build-tools/builders/soa/p-consoles/jbpm/build.xml

Commit message:
> SOA-1427
> SOA-1433
> Copy fixes from JSF console jsf-console-3.2-soa branch for JBPM-2460 and
> JBPM-2475.

and with the updates for JBPM-2475 on the jBPM `jbpm-3.2-soa' branch.
Comment 4 Len DiMaggio 2009-09-11 11:18:02 UTC 
Note from Toshiya:

I verified that this bug was fixed and CP02 worked fine.