[JBoss JIRA] Created: (GPD-234) Two Nodes with the same name
by Sven Daumann (JIRA)
Two Nodes with the same name
----------------------------
Key: GPD-234
URL: https://jira.jboss.org/jira/browse/GPD-234
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM jPDL Designer 3.1.3
Environment: Eclipse 3.3.2
Reporter: Sven Daumann
Assignee: Koen Aers
step1: Create a Node and put a transition to this Node.
step2: Rename the Node and use the name of an existing Node.
The GPD show both Nodes with Transitions.
step3: Close the diagram
step4: Reopen the diagram
problem: Only one Node is visible, the two transitions go to the one Node.
step5: Move the Node. The moving Node has no transition. Under the moved Node, the other Node is now visible, with both transitions.
Duringh rename, there is no warning, that another Node with the same name exist.
The XML data contains two Nodes.
processdefinition.xml
<?xml version="1.0" encoding="UTF-8"?>
<process-definition xmlns="" name="Test">
<start-state name="start-state1">
<transition to="node1" name="startet"></transition>
</start-state>
<node name="node1">
<transition to="node2" name="ok"></transition>
<transition to="Test" name="toTest"></transition>
</node>
<node name="node2">
<transition to="end-state1" name="ok"></transition>
<transition to="Test" name="toTest"></transition>
</node>
<task-node name="Test"></task-node>
<task-node name="Test"></task-node>
<end-state name="end-state1"></end-state>
</process-definition>
gpd.xml
<?xml version="1.0" encoding="UTF-8"?>
<root-container name="Test" width="675" height="634">
<node name="start-state1" x="375" y="272" width="132" height="36">
<edge>
<label x="5" y="-10"/>
</edge>
</node>
<node name="node1" x="374" y="353" width="132" height="36">
<edge>
<label x="5" y="-10"/>
</edge>
<edge>
<label x="5" y="-10"/>
</edge>
</node>
<node name="node2" x="378" y="448" width="132" height="36">
<edge>
<label x="5" y="-10"/>
</edge>
<edge>
<label x="5" y="-10"/>
</edge>
</node>
<node name="end-state1" x="383" y="548" width="132" height="36"/>
<node name="Test" x="172" y="347" width="132" height="36"/>
<node name="Test" x="174" y="451" width="132" height="36"/>
</root-container>
--
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
15 years, 2 months
[JBoss JIRA] Created: (GPD-133) with two transitions from a node, both need to be labelled, or jbpm-console exceptions
by Ross McDonald (JIRA)
with two transitions from a node, both need to be labelled, or jbpm-console exceptions
--------------------------------------------------------------------------------------
Key: GPD-133
URL: http://jira.jboss.com/jira/browse/GPD-133
Project: JBoss jBPM GPD
Issue Type: Bug
Affects Versions: jBPM JPDL Designer 3.1.0.beta1
Environment: osx, macbook pro, eclipse 3.3.0
Reporter: Ross McDonald
Assigned To: Koen Aers
when there are two transitions from a node, both need to be labelled (given a name), I am not sure if there is a validate xml option within the plugin, it would help if there was, if both are not given a name, the jbpm-console exceptions across multiple pages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (GPD-204) Additional Attribute for ESB Service Node
by Jeff DeLong (JIRA)
Additional Attribute for ESB Service Node
-----------------------------------------
Key: GPD-204
URL: http://jira.jboss.com/jira/browse/GPD-204
Project: JBoss jBPM GPD
Issue Type: Feature Request
Components: jpdl
Reporter: Jeff DeLong
Assigned To: Koen Aers
There are two other options of the ESBActionHandler described in the SOA_ESB_JBPM_Integration_Guide.pdf
default - optional attribute which can hold a default value if the esb MVEL expression does
not find a value set in the EsbMessage.
exceptionTransition - optional element. The name of the transition that should be taken if
an exception occurs while processing the Service. This requires the current node to have
more then one outgoing transition where one of the transition handles "exception
processing"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months