I considered a parallel convoy.  I don't want to start an instance of
my orchestration till file A and file B are present.  Also, several
copies of file B could be dropped to my in folder replacing the
previous before file A is dropped. The same for the opposite scenario,
several copies of file A, then finally one copy of file B.  So, only a
single copy of file A and file B will be mapped to a single file C.


With out using an orchestration I tried using 2 receive ports going to
the same folder to pickup file A and fileB.  Then I created a send port
that subscribes to my receive ports as follows:  BTS.ReivePortName ==
FileA_ReceivePort AND BTS.ReivePortName == FileB_ReceivePort.  Send
port also has a map  to transform file A and file B to a single file C.
After considering the principles of publish/subscribe a little more I
can see why this doesn't work either.
Ken

[ Post a follow-up to this message ]