setting the name of a transaction to an unchanged value through the api results in an faulty exception ------------------------------------------------------------------------------------------------------ Key: JBPM-2046 URL: https://jira.jboss.org/jira/browse/JBPM-2046 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Environment: WindowsXP Reporter: Tom Eugelink Priority: Minor Setting the name of a transition to the value it already has, results in an exception: Exception in thread "AWT-EventQueue-0" java.lang.IllegalArgumentException: couldn't set name 'state2_to_join1' on transition 'Transition(state2_to_join1)'cause the from-node of this transition has already another leaving transition with the same name at org.jbpm.graph.def.Transition.setName(Transition.java:223) at nl.innovationinvestments.jbpm.Jbpm3Editor$1.invoke(Jbpm3Editor.java:131) at com.mxgraph.util.mxEventSource.fireEvent(Unknown Source) at com.mxgraph.util.mxEventSource.fireEvent(Unknown Source) at com.mxgraph.model.mxGraphModel$1.dispatch(Unknown Source) at com.mxgraph.model.mxGraphModel.endUpdate(Unknown Source) at com.mxgraph.swing.mxGraphComponent.labelChanged(Unknown Source) at com.mxgraph.swing.view.mxCellEditor.stopEditing(Unknown Source) at com.mxgraph.swing.mxGraphComponent.stopEditing(Unknown Source) at com.mxgraph.swing.mxGraphComponent$6.mouseReleased(Unknown Source) at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:273) .... The exception is quite right, the leaving transition is itself. This naturally is easily fixable, by comparing if the name is identical, but IMHO is the check not correct; it should not validate against itself. -- 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