Bug 779021 (SOA-1433) - sub-process name is not resolved upon deployment with Eclipse or ant-task
Summary: sub-process name is not resolved upon deployment with Eclipse or ant-task
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1433
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBPM - within SOA
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-11 14:58 UTC by Toshiya Kobayashi
Modified: 2009-09-11 11:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-11 11:18:02 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1433 0 Major Closed sub-process name is not resolved upon deployment with Eclipse or ant-task 2012-11-09 10:09:36 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.