My proposition is to extend evaluation of condition when selecting leaving transitions

<decision condition-evaluation="strict|first-matching|???">
....
</decision>

condition-evaluation (or similar attribute) meaning:

• strict - all conditions are evaluated, lets name N as number of conditions which evaluates to true. If N != 1 jBPM raise exception. Transitions without conditions are not allowed
• first-matching - jBPM evaluates conditions and leave when find first which evaluate to true. If there is no such transition jBPM raise exception. Transitions without conditions are allowed and evaluates to true.
• ??? (I don't no how to name it) - this is default and makes that jBPM behaves as described in current documentation : "So first, all transitions with a condition are evaluated. If one of those evaluate to true, that transition is taken. If no transition with a condition resolves to true, the default transition (=the first one) is taken"

It will be very helpful during development and testing.