sub-process name is not resolved upon deployment with ant-task(DeployProcessTask) --------------------------------------------------------------------------------- Key: JBPM-2481 URL: https://jira.jboss.org/jira/browse/JBPM-2481 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Toshiya Kobayashi Assignee: Alejandro Guizar Fix For: jBPM 3.2.7 If you omit binding attribute for <sub-process> in <process-state> and deploy the process definition with org.jbpm.ant.DeployProcessTask, 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 -- DeployProcessTask 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 message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira