]
Koen Aers commented on GPD-133:
-------------------------------
I think this is basically a problem in the console.
Tom has asked a long time ago to *not* generate a name for the transition if there is only
one and generate a name starting with the second transition. He even fixed this himself if
I remember correctly. Now I know that this strategy is debatable and that there are a
number of prominent jBPM users that prefer a default name in all cases (I think Ronald is
amongst them). I even think there is a JIRA issue to reintroduce this, but I don't
remember which one from the top of my head.
The obvious workaround is to give your transitions a name as you found out.
Note that validation is pointless because the jPDL xsd does not mandate the name for the
transition.
Regards,
Koen
with two transitions from a node, both need to be labelled, or
jbpm-console exceptions
--------------------------------------------------------------------------------------
Key: GPD-133
URL:
http://jira.jboss.com/jira/browse/GPD-133
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0.beta1
Environment: osx, macbook pro, eclipse 3.3.0, tomcat 5.0.28
Reporter: Ross McDonald
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.CR
Attachments: broken_process.xml, broken_process_exception.txt, fixed_process.xml
when there are two transitions from a node, both need to be labelled (given a name), I am
not sure if there is a validate xml option within the plugin, it would help if there was,
if both are not given a name, the jbpm-console exceptions across multiple pages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: