Hello,
I have a problematic example of an activity I try to express. The
activity gets an ID parameter (categoryID) which splits the process
into two transitions. Each one loads an Item entity. After trying to
load them it shall be checked, if the 'extraItem' exists. If so, it is
used with the (always existing) defaultItem. If not, only the
defaultItem is processed.
please take a look at this activity:
http://groups.google.com/group/umlforum/web/ProblemActivity.gif?hl=en
I assume a mistake in the diagram, but I don't know how to solve it.
The problem is that the loading actions are parallel and get
synchronised _after_ the decision whether the extraItem exists or not.
Although the decision node needs both tokens to get a result it is not
a synchronisation so I think the course is wrong at that point. But if
I do the synchronisation first there could arise a deadlock, because
an extraItem does not have to exists so that this thread is only
terminated - it would not lead into the join-node.
Can anyone give me a hint for correcting the diagram?
--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to
umlf...@googlegroups.com.
To unsubscribe from this group, send email to
umlforum+u...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/umlforum?hl=en.