Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365995 - Unable to set message flow(s) on choreography task
Summary: Unable to set message flow(s) on choreography task
Status: RESOLVED FIXED
Alias: None
Product: BPMN2Modeler
Classification: SOA
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 normal (vote)
Target Milestone: 0.0.1-M2   Edit
Assignee: Robert Brodt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-08 04:44 EST by Gary Brown CLA
Modified: 2012-01-31 07:46 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Brown CLA 2011-12-08 04:44:58 EST
Build Identifier: 

When selecting a choreography task, the properties view no longer provides the means to associate a message flow with the choreography task.


Reproducible: Always

Steps to Reproduce:
1. Create a choreography
2. Select the default ChoreographyTask
3. Select the properties view - no means of setting message flows
Comment 1 Gary Brown CLA 2012-01-31 07:46:33 EST
Message flow is now automatically created as a result of creating/associating a message with the participant band on the choreography task.

Only issue (which probably needs a validation rule) is to ensure that if the participants associated with a choreography task are changed, at the message flow participants are checked for consistency - i.e. a message flow associated with a choreography task must share common participants.