Join problem

[armita]

I have the attached process definition and "FF Join" acts in a strange way. If I execute the "UploadMediaFile" first, everything is OK, but if "UploadMetadata" executes first, it does not wait for "UploadMediaFile" and executes the join right away.
any thoughts?

<?xml version="1.0" encoding="UTF-8"?>

<process-definition xmlns="" name="mediaprocess">


 <swimlane name="actor">
 <assignment class="ca.cbc.mediagateway.MGWAssignmentHandler"></assignment>
 </swimlane>


 <start-state name="start">
 <transition to="fork1"></transition>
 </start-state>


 <fork name="fork1">
 <transition to="UploadMediaFile"></transition>
 <transition to="UploadMetadata" name="to upload meta data"></transition>
 <transition to="UploadThumbnails" name="to upload thumbnails"></transition>
 </fork>

 <join name="join1">
 <transition to="Maven"></transition>
 </join>

 <task-node name="UploadMediaFile">
 <task name="UploadMediaFile" swimlane="actor"></task>
 <transition to="FF Join"></transition>
 </task-node>

 <task-node name="UploadMetadata">
 <task name="UploadMetadata" swimlane="actor"></task>
 <transition to="fork2"></transition>
 </task-node>

 <task-node name="UploadThumbnails">
 <task name="UploadThumbnails" swimlane="actor"></task>
 <transition to="join3"></transition>
 </task-node>

 <node name="Maven" async="true">
 <action class="ca.cbc.mediagateway.handler.MavenHandler" async="true"></action>
 <transition to="MediaBin"></transition>
 </node>

 <node name="MediaBin" async="true">
 <action class="ca.cbc.mediagateway.handler.MediaBinHandler"></action>
 <transition to="EPT"></transition>
 </node>

 <node name="EPT" async="true">
 <action class="ca.cbc.mediagateway.handler.EPTHandler"></action>
 <transition to="Finito la commedia"></transition>
 </node>

 <task-node name="FlipCallback">
 <task name="FlipCallback" swimlane="actor" ></task>
 <transition to="join1"></transition>
 </task-node>

 <node name="UploadToFlipFactory">
 <action class="ca.cbc.mediagateway.handler.UploadToFlipFactoryHandler" async="true"></action>
 <transition to="FlipCallback"></transition>
 </node>

 <fork name="fork2">
 <transition to="join3"></transition>
 <transition to="FF Join" name="to UploadToFlipFactory"></transition>
 </fork>

 <node name="StoreThumbnail">
 <action class="ca.cbc.mediagateway.handler.StoreThumbnailHandler" async="true"></action>
 <transition to="join1"></transition>
 </node>

 <join name="FF Join">
 <transition to="UploadToFlipFactory"></transition>
 </join>

 <join name="join3">
 <transition to="StoreThumbnail"></transition>
 </join>


 <end-state name="Finito la commedia"></end-state>


</process-definition>

[kukeltje]

forks/joins have to be fully nested, from what I quickly scanned they are not in your case

[armita]

"kukeltje" wrote:
forks/joins have to be fully nested, from what I quickly scanned they are not in your case

What does that mean to be fully nested

[kukeltje]

All transitions from a fork have to end in the same join. If there is no additional fork in between it has to be the join they encounter.

Fork 1

Join 1

Fork 2

Join 2

is ok

Fork 1

Join 2

Fork 3

Join 1

is not

[kukeltje]

even

fork 1

fork 2

join 2

join 1

is ok

(fork/join 2 is fully inside fork1/join1

[armita]

This is my process graph. Based on what you kindly explained I guess it is not fully nested. Is there a workaround to make it nested?
http://picasaweb.google.com/lh/photo/Mz7FzmzWwgYywwhI1b-cnQ?authkey=Gv1sRgCKmBjfD-hr6rhgE&feat=directlink

[kukeltje]

yes.... and I think you can see that yourself as well.. it's very, very easy...


remove the right join (why is that there anyway) of the two that are on the same line and put an additional fork after the first one, but before the uploadmediafile and uploadmetadata