[
https://jira.jboss.org/browse/JBPM-2830?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu updated JBPM-2830:
------------------------------
Attachment: JBPM-2830.patch
When there is no id, deploy failed.
When there is only id, set id as process definition name.
When there is both id and name, set id as key, set name as name.
(BPMN) In Latest source jbpm uses the name instead of the id for
processes
--------------------------------------------------------------------------
Key: JBPM-2830
URL:
https://jira.jboss.org/browse/JBPM-2830
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4
Reporter: Sebastian Rühl
Fix For: jBPM 4.5
Attachments: JBPM-2830.patch
In Latest source jbpm uses the name instead of the id for processes...
In my opinion this is the wrong behaviour as the name of a process will be converted to a
id.
So if you want to start a process via:
executionService.startProcessInstanceByKey("process4711") it will throw a
exception.
Example Process for this:
<process id="process4711" name="Could be a very long description and
is not used to IDENTIFY">
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira