Bugzilla – Full Text Bug Listing
| Summary: | Property Editor: Call Activity | ||
|---|---|---|---|
| Product: | [SOA] BPMN2Modeler | Reporter: | Robert Brodt <bbrodt> |
| Component: | UI | Assignee: | Robert Brodt <bbrodt> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| URL: | https://issues.jboss.org/browse/JBPM-3250 | ||
| Whiteboard: | |||
Fixed |
Create a custom property editor (implemented either as a popup dialog or a Property Sheet Tab) for Call activity (reusable sub-process). -> independent* and waitForCompletion* are boolean: dropdown true/false or checkbox -> data input / output mapping Brian Fitzpatrick added a comment - 22/Aug/11 1:44 PM Based on the EMF model and the BPMN2 specification, it appears that: Data input/output mapping should happen the same as it works with the SequenceFlow for inputs and outputs waitForCompletion is apparently in CompsensateEventDefinition, so the boundary events (getBoundaryEventRefs() on the CallActivity) should enable us to grab those and display the properties from those Brian Fitzpatrick added a comment - 22/Aug/11 4:42 PM - edited Ok, after doing some more digging in the EMF models for BPMN2... 1. I'm going to do a two-pronged approach and create an extensible property page for generic Activity objects and then extend it for Call Activity. This ensures that if additional custom Activities get added in the future, we have a model to follow for consistency. 2. My initial thoughts appear to be wrong about where to get the data input and output mappings from. Instead of from the lists of DataInputAssociation and DataOutputAssociation objects, it looks like the InputOutputSpecification object available through getIoSpecification() will offer the right list of DataInputs and Outputs and data sets. 3. It appears that to get to the waitForCompletion kinds of settings, we need to go through the BoundaryEvents to get the list of EventDefinitions to see if any of those has properties to set (like CompensateEventDefinition, which has waitForCompletion).