Issue 14869: Does CallChoreography need a MessageFlowAssociation? (bpmn2-ftf) Source: International Business Machines (Dr. Stephen White, wstephe(at)us.ibm.com) Nature: Revision Severity: Significant Summary: Choreographies contain Message Flow. The CallChoreographyActivity will call another Choreography or a GlobalChoreographyTask, both of which have there own Message Flow. There are similar relationships to Participant. A CallChoreographyActivity has a ParticipantAssociation, so it should also have a MessageFlowAssociation or should not have the ParticipantAssociation. Resolution: The Message Flow within the called Choreography will not be used or interact within the calling Choreography, so no mapping is required. Thus, there is no change required to the specification. Disposition: Closed, No Change Revised Text: Actions taken: December 16, 2009: received issue October 21, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 16 Dec 2009 21:13:38 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Steve White Company: IBM mailFrom: wstephe@us.ibm.com Notification: No Specification: BPMN 2.0 Beta Section: 12 FormalNumber: DTC-09-08-14 Version: Beta RevisionDate: Aug 09 Page: 325 Title: Does CallChoreography need a MessageFlowAssociation? Nature: Revision Severity: Significant test: 3qw8 B1: Report Issue Description: Choreographies contain Message Flow. The CallChoreographyActivity will call another Choreography or a GlobalChoreographyTask, both of which have there own Message Flow. There are similar relationships to Participant. A CallChoreographyActivity has a ParticipantAssociation, so it should also have a MessageFlowAssociation or should not have the ParticipantAssociation.