The default fork implementation spawns multiple parallel stats/nodes/tasknodes/etc.... and activates all. The decision only takes one of the outgoing transitions.
If you see the fork not taking all available transitions you probably have one of the transitions going fairly directly into the join or the end. That is a 'bug' in jBPM 2.0 and most likely 3.0. Make sure (to see the right behaviour) to have wait states on all outgoing transitions
okay, thanx :-)
let me follow up on that and work on a model... that way i can have an example to show you.