| Summary: | Initial participant set on a ChoreographyTask should be the initiating participant | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [SOA] BPMN2Modeler | Reporter: | Gary Brown <gary> | ||||
| Component: | UI | Assignee: | Robert Brodt <bbrodt> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | Flags: | bbrodt:
iplog+
|
||||
| Version: | unspecified | ||||||
| Target Milestone: | future | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Gary Brown
One other point - the initiating participant ref property uses the 'toString()' value of the Participant, rather than the name. It would be cleaner if this field either used the name, or some composite string made up of the name and id (for cases where possibly the name has not been defined)? Created attachment 209274 [details]
Patch to provide a solution
Provides the initial participant based on the first participant set. This does not mean the user cannot change the initiating participant to another participant, however in most cases the user would set the initiator first, and therefore this change reduces the work by the user in most situations.
Thanks Gary, I've applied the patch. |