[jboss-jira] [JBoss JIRA] Resolved: (GPD-20) refactor naming strategy

[Koen Aers (JIRA)]

     [ https://jira.jboss.org/jira/browse/GPD-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koen Aers resolved GPD-20.
--------------------------

    Resolution: Out of Date


> refactor naming strategy
> ------------------------
>
>                 Key: GPD-20
>                 URL: https://jira.jboss.org/jira/browse/GPD-20
>             Project: jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>            Assignee: 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

-- 
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