Bugzilla – Full Text Bug Listing
| Summary: | Apply XML structure to extension activity model | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Tobias Liefke <eclipse> |
| Component: | BPEL | Assignee: | BPEL Model Inbox <bpel.model-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 340654 | ||
| Bug Blocks: | |||
I propose to introduce a new container for the extension activity:
<sequence name="..."> - SequenceImpl
<extensionActivity> - ExtensionActivityContainerImpl (extends Activity)
<myActivity> - MyActivityImpl (extends ExensionActivityImpl)
...
</myActivity>
</extensionActivity>
</sequence>
The ExtensionActivityContainer would add only one feature: "activity".
It could delegate the activity methods (like get/setName()) to the contained extension activity then.
I would like to propose a patch, but thats not possible before the model is synchronized with the code (see #340654).
|
Build Identifier: Current implementation of mapping between XML nodes and EMF objects for extension activities: <sequence name="..."> - SequenceImpl <extensionActivity> - MyActivityImpl (extends ExtensionActivityImpl) <myActivity> - Must be handled by MyActivityImpl, but is not directly connected ... </myActivity> </extensionActivity> </sequence> This leads to many problems, especially when synchronizing the design view with the XML view, as all other model elements are connected as mirror of the XML structure. Reproducible: Always