Connecting all outgoing branches of a decision or fork directly to end or stop nodes shows that the decision or fork is unnecessary.
将某个decision或fork的所有传出分支直接连接到各个结束或停止节点，这意味着这个决策或fork是不必要的。
However, such a solution should be used with care in models that contain both types of branching, i.e., forks and decisions, to avoid suddenly closing a fork with a merge or a decision with a join.
但是，在同时包含两类分支(即fork和decision)的模型中，使用此类解决方案应十分谨慎，以避免在不经意间用一个join关闭一个fork或用一个merge关闭一个decision。
Decision and merge are always mapped to several input and output criteria-one for each branch, while fork and join correspond to a single output and input criterion, respectively.
Decision和merge始终映射到多个输入和输出条件，每个分支对应一个条件，而fork和join则分别对应于一个输出和输入条件。
For alternative branching, an identical pattern results where the fork is replaced by a decision and the join is replaced by a merge.
为了进行可选分支，会产生一个相同的模式，在其中fork被替换为decision,join被替换为merge。
Gateway form using decision, fork, merge, and joins is often more readable for models that only model control flow.
网关形式使用decision、fork、merge和join元素，对于只包含控制流的模型而言，此形式通常更易于理解。
If we replace the inclusive decision and fork with two exclusive decisions, the process would only have one sequential execution path.
如果我们将包含性decision和fork替换为两个独占性decision，该流程将只有一条后续执行路径。
We already showed the decision/merge mapping in the MultiMethod project, so this part will concentrate on the fork/join mapping.
我们在 MultiMethod项目中已经介绍了decision/merge映射，因此该部分将集中讨论一下fork/join 映射。
If both branches are triggered, the inclusive decision leads to a parallel execution of Task 2 and Task 3 in the same way as a fork.
如果全部触发这两个分支，则包含性决策将导致Task2和Task3并行执行，其效果与fork类似。
This cyclic dependency between the join and the decision, and the join and the fork (where the join must be executed before the decision or fork and vice versa) is the reason why a deadlock occurs.
join和decision以及join和fork之间的这种循环依赖关系(其中join必须在decision或fork之前执行，反之亦然)便是发生死锁的原因。
We describe solutions based on gateway pairs that are built with the decision, merge, fork, and join modeling elements.
我们基于用decision、merge、fork和join建模元素构建的网关对来描述解决方案。
The difference between the behavior of the fork and the inclusive decision lies in the number of unsynchronized cycles that are triggered when the fork and the inclusive decision execute.
fork和inclusivedecision之间的行为差异在于，在执行fork和inclusive decision时所触发的未同步循环的数目不同。
The upper branch of the inclusive decision connects to a third cyclic process fragment with a merge preceding a fork.
inclusive decision 最上方的分支使用fork 之前的merge连接到第三个循环流程片断。
The third cycle starts in the fork preceding the end node, and leads back to the join following the decision.
第三个循环从结束节点之前的 fork中开始，并引回decision之后的 join。
All inputs of the decision and the merge, as well as of the fork and join, must be connected.
decision和merge以及fork和join之间的所有输入都必须连接在一起。
Cyclic deadlocks through join-fork and join-decision pairs.
因join -fork和join - decision对导致的循环死锁。
The fork corresponds to the and Rule, the inclusive decision corresponds to the or Rule, and the decision corresponds to the XOR Rule.
fork对应于ANDRule,inclusivedecision对应于or Rule，而decision则对应于XOR Rule。
And having arrived at this Spartan decision Mr. Welland firmly took up his fork.
做出这一大无畏的决定之后，韦兰先生又坚定地拿起了餐叉。
And having arrived at this Spartan decision Mr. Welland firmly took up his fork.
做出这一大无畏的决定之后，韦兰先生又坚定地拿起了餐叉。
应用推荐