[
https://jira.jboss.org/jira/browse/JBPM-2830?page=com.atlassian.jira.plug...
]
Sebastian Rühl commented on JBPM-2830:
--------------------------------------
:)
Another example is, that you can have more than one process in a bpmn.xml
So what happens if these have the same name... you will run in trouble...
therefore there is the id attribute which gurantees that this id will be unique...
My Problem with this is, that I use the process id for a file lookup.
Since the name should be human readable, you have to deal with whitespace etc...
I don't know why this is changed upstream... In 4.3 the correct behaviour is
implemented. (identifieing process with id attribute)
(BPMN) In Latest source jbpm uses the name instead of the id for
processes
--------------------------------------------------------------------------
Key: JBPM-2830
URL:
https://jira.jboss.org/jira/browse/JBPM-2830
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Sebastian Rühl
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/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira