refactor naming strategy ------------------------ Key: JBPM-202 URL: http://jira.jboss.com/jira/browse/JBPM-202 Project: JBoss jBPM Issue Type: Task Components: Graphical Process Designer Reporter: Koen Aers Assigned To: Koen Aers 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type. 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though. 3) use the following naming strategy for end states: {end, end2, end3, end4, ...} 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name. 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot