Mahesh: This is a good point, however, the fact that BC2 is a sub-collaboration of BC1 is a design time construct. At run-time everything happens as if there was only one collaboration definition. So BT1 should be identified with BC1 as the intend of the sender is to execute BC1 and not BC2. In particular, the CPA is established with BC1 and not BC2. The CPA is not transitive with respect to collaboration composition. If you have a CPA on BC1 it does not mean that you also have (implied) a CPA on BC2. Hope that helps. Jean-Jacques Dubray____________________ Chief Architect Eigner Precision Lifecycle Management 200 Fifth Avenue Waltham, MA 02451 781-472-6317 jjd@eigner.com www.eigner.com >>-----Original Message----- >>From: Mahesh [mailto:mahesh@gridnode.com] >>Sent: Wednesday, December 25, 2002 8:56 PM >>To: ebxml-dev@lists.ebxml.org; nandini.ektare@sun.com >>Subject: [ebxml-dev] Request for help in BPSS >> >>Hi all, >> >> I am having a small doubt in implementation of BPSS. Please >>can you help me in below described sinerio. I got struck with this. >> >> Say if you have two BinaryCollaboration 'BC1','BC2'. And >>'BC1' >>and 'BC2' are linked through CollaborationActivity 'CA1'. If 'BC1' is >>started >>and the 'Start' element is pointing to CollaborationActivity 'CA1' which >>will >>inturn start the 'BC2' , and 'BC2' will start some BusinessTransaction >>'BT1', >>which will send a request document to Responder. >> >> So how will the Responder side Workflow engine know that this >>Request is due to the 'BC1',because the ebMS layer will carry 'Service' >>and >>'Action' >>fields which holds values 'BC2' and 'BT1' respectively and it does not >>carry >>anything >>which says this Request document is due to 'BC1'. Please give me some clue >>to go forward. >> >>Hoping for ur replay, >>Thanks in advance. >> >>regards, >>Mahesh >>email: mahesh@gridnode.com >> >> >> >> >>---------------------------------------------------------------- >>The ebxml-dev list is sponsored by OASIS. >>To subscribe or unsubscribe from this elist use the subscription >>manager: <http://lists.ebxml.org/ob/adm.pl> ---------------------------------------------------------------- The ebxml-dev list is sponsored by OASIS. To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.ebxml.org/ob/adm.pl>
<<attachment: winmail.dat>>