[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't

[Koen Aers (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12446289#action_12446289 ] 

Koen Aers commented on JBIDE-3492:
----------------------------------

You get a label if there is more than one *leaving* transition from a particular node.  I don't necessarily think this is the best approach (ie. I think it is best that every transition gets a name and that used to be the behavior), but it is most certainly how my benevolent dictator wanted things ;-)

> When creating Transitions... sometimes you feel like a name, sometimes you don't
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-3492
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3492
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jbpm
>    Affects Versions: 3.0.0.cr1
>            Reporter: Nick Boldt
>            Assignee: Koen Aers
>             Fix For: 3.0.0.CR2
>
>
> Sorry for the Mounds/Almond Joy reference in the issue title. The actual problem is that when creating Transitions with the jBPM Graphical Process Designer, sometimes you get labels, and sometimes you don't... seemingly at random. Sometimes when I create two-way references I get one label, or two, or none.
> 		<transition to="end-state2"></transition>
> vs.
> 		<transition to="end-state1" name="to end-state1"></transition>
> --
> Tested with JBoss Dev Studio Version: 2.0.0.CR1, Build id: R200812221144
> Steps to repro:
> 1. Install JBDS.
> 2. download http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://downloads.sourceforge.net/jbpm/jbpm-installer-3.3.0.GA.jar
> 3. `java -jar jbpm-installer-3.3.0.GA.jar`. I installed into ~/jbpm-3.3.0.GA
> 4. New > Other > Process Project
> 5. Go into src/main/jpdl/simple and open processdefinition.xml with jBPM Graphical Process Designer
> 6. Add a couple nodes, then connect them to the existing flow, or create a new flow from scratch.
> 7. Switch to Source tab. I had this: 
> <?xml version="1.0" encoding="UTF-8"?>
> <process-definition  xmlns="urn:jbpm.org:jpdl-3.2"  name="simple">
> 	<start-state name="start-state1">
> 		<transition to="state1"></transition>
> 	</start-state>
> 	<state name="state1">
> 		<transition to="fork1"></transition>
> 	</state>
> 	<fork name="fork1">
> 		<transition to="end-state2"></transition>
> 		<transition to="end-state1" name="to end-state1"></transition>
> 	</fork>
> 	<end-state name="end-state1"></end-state>
> 	<end-state name="end-state2"></end-state>
> </process-definition>
> In this case, I created 4 Transitions and only one was given a default name, "to end-state1".

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