[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2604) Saving a JPM4 process in Eclipse looses the transitions condition and script nodes
[
https://jira.jboss.org/jira/browse/JBPM-2604?page=com.atlassian.jira.plug...
]
Achim Heynen commented on JBPM-2604:
------------------------------------
This bug appears in other situations, too. I found the following ones:
- fields of decision handlers get removed
- fields of custom tasks get removed
You do not have to save the file necessarily. Switching from diagram to source mode has
the same impact.
This bug is critical for our current project, because it makes the graphical mode of the
GPD nearly useless. Each time you move or edit something you have to check if the existing
tasks have lost their sub-nodes.
Saving a JPM4 process in Eclipse looses the transitions condition and
script nodes
----------------------------------------------------------------------------------
Key: JBPM-2604
URL: https://jira.jboss.org/jira/browse/JBPM-2604
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: GPD
Affects Versions: jBPM 4.1
Environment: Running Eclipse Ganymede Version: 3.4.2 Build id: M20090211-1700.
JBPM 4.1 Tools.
Reporter: Paul Smith
Fix For: jBPM 4.x
Attachments: batchAccountListSyncSAP-processdefinition.xml
Running the JpdlConverterTool over a JBPM3.2 process xml file correctly converts the
file. However if you open the file using GPD, move one of the nodes and then save the file
then all of the transition nodes condition and script nodes disappear. I have attached a
process that this can be tested with.
--
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