[ https://jira.jboss.org/jira/browse/JBPM-2475?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated JBPM-2475: ------------------------------------ Description: 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. was: 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. 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 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

[ https://jira.jboss.org/jira/browse/JBPM-2475?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2475: ----------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Component/s: Runtime Engine Open jBPM context before parsing in both deploy task and upload servlet. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2475?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2475: ----------------------------------- Attachment: mylyn-context.zip -- 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

[ https://jira.jboss.org/jira/browse/JBPM-2475?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-2475: ----------------------------------- Summary: sub-process name is not resolved upon deployment with Eclipse or Ant task (was: sub-process name is not resolved upon deployment with Eclipse(ProcessUploadServlet)) -- 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