[JBoss JIRA] Created: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
1:29 p.m.
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
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://down...
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
7:46 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-3492:
---------------------------------------
Fix Version/s: 3.0.0.CR2
Assignee: Koen Aers
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://down...
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
7:10 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Koen Aers resolved JBIDE-3492.
------------------------------
Resolution: Rejected
It is a feature:
- if only one transition, the engine expects no name when signalling to move to the next
state
- if more than one you have to be able to distinguish between them, so at least one name
is required
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://down...
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
8:08 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-3492:
-----------------------------------
I think there may still be a bug here. IIRC, you don't always get a label when you add
a second transition (eg., a reverse B->A relationship to an existing A->B one).
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://down...
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
8:33 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
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://down...
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
8:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-3492:
-----------------------------------
Well, then how about adding a label by default as well when there's an A->B and you
add the B->A in reverse... in addition to the "when adding second departing
transition, add label" case?
Granted they run in opposite directions, but shouldn't one or both have a label at
that point?
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://down...
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
11:45 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Koen Aers commented on JBIDE-3492:
----------------------------------
I used to give them both a label. But TomB gets very nervous if the produced xml is more
verbose than it needs to be. So upon his request this has been changed. I guess you would
need to convince him...
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://down...
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
12:55 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-3492:
-----------------------------------
So it's end-user expectation of function vs. pretty xml files? Aargh.
/me shakes head
Maybe I'm not the right person to voice an opinion here, since I've only just
started using jBPM last week. But IMHO I'd rather see the tool not behaving in a
(seemingly) random way w.r.t. labels than worry about the contents of the XML, especially
since the source editor has some, uh, issues with data corruption, reported in JIRAs
elsewhere.
If the point of a GUI tool is to not need to view source, then why do we care how terse
the source ends up being?
Anyway, I'll leave it with you. If you want to bring this to TomB, by all means. If
you're satisfied with the usability and (seemingly) random allocation of labels (I
know, it's not, it just seems that way at first) then I'm satisfied too.
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://down...
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
6:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3492:
--------------------------------------------
To Nick: The point of a GUI tool is not to remove the need of viewing the source - it is
for making it easier to edit the source. Readable source is important.
To Koen: correct and consistent generation of source is also important. Thus if there is a
*semantically* difference between:
<decision name="decision1">
<transition to="A"></transition>
<transition to="B" name="to B"></transition>
</decision>
and
<decision name="decision1">
<transition to="B"></transition>
<transition to="B" name="to B"></transition>
</decision>
then we need to do something since then the UI is generating the minimal xml but with
result of the xml behaving inconsistently at runtime dependent on what time the user made
the transitions
which is not obvious in the ui that it should have a difference.
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://down...
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
9:28 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Koen Aers commented on JBIDE-3492:
----------------------------------
Max, of course the two cases are semantically different. But I don't understand your
point I'm afraid... The generated name, and label is merely a default. The modeler
should change the name in whatever name he likes.
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://down...
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
10:39 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3492:
--------------------------------------------
My point is that if an user creates three nodes (A,B,C) and draws the *exact* same
transitions between them the semantics are different depending on the sequence he draws
the transitions...that is not very logical. The drawing will "graphically" look
exactly the same.
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://down...
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
11:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Koen Aers commented on JBIDE-3492:
----------------------------------
No if he draws the transitions in a different order, the drawing will be different (ie.
the label will show up at a different transition)
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://down...
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
11:42 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-3492:
--------------------------------------------
yes - but why introduce this additional complexity and not just always give them a name so
no matter which sequence I create the transitions in it will behave the same ?
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://down...
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
1:17 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-3492) When creating Transitions... sometimes you feel like a name, sometimes you don't
[
https://jira.jboss.org/jira/browse/JBIDE-3492?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-3492:
-----------------------------------
+1. Better to have consistent behaviour than to end up with this conversation in the
user's head:
"ok, I've made 3 states, now I need to connect 'em.
draw a line from a to b, draw a line from a to c... hey, that one has a label! cool, I can
label them.
draw a line from b to a... no label?
draw a line from c to a... also no label. How do I make the labels show up? Hmm. better
check the source tab to see what's going on..."
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://down...
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
6303
days inactive
6309
days old
jbosstools-issues@lists.jboss.org
13 comments
3 participants
participants (3)
-
Koen Aers (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)