Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "STP/BPMN Component/STP BPMN Modeler Status"

(BPMN shapes)
 
(6 intermediate revisions by 2 users not shown)
Line 21: Line 21:
 
Stable.
 
Stable.
 
Current objects and APIs are not expected to change.
 
Current objects and APIs are not expected to change.
Additions for the missing objects might be made.
+
The EMF bpmn package will be generated from the ecore when we migrate the modeler to Eclipse-3.3: at the same time than the rest of STP.
 +
We have tested that it works and the EMF team has solved a bug uncovered then.
  
 
=== BPMN properties ===
 
=== BPMN properties ===
Line 35: Line 36:
  
 
=== Copy/Paste ===
 
=== Copy/Paste ===
Fixed but need to be tested in depth.
+
Working.
Corrupts the object model when copying objects with links. Bugzilla number:169863
+
  
 
=== Preferences ===
 
=== Preferences ===
Line 45: Line 45:
 
=== Documentation ===
 
=== Documentation ===
 
To be written.
 
To be written.
 +
 +
[[Category:BPMN]]
 +
[[Category:STP]]

Latest revision as of 07:25, 21 February 2008

Build

The BPMN modeler is built with the rest of STP starting on the 5th of December 2006. None of those builds have been published yet so no update site with the modeler is available.

You need to download the bpmn feature from a recent integration build: STP Integration build page, unzip it along an elipse installation and the GMF dependencies. This will install the modeler.

BPMN shapes

All shapes and connections are implemented. Lanes and Group support is work in progress. Add-hoc and compensation markers not implemented.

Validation

Framework is in place. Connection rules are implemented. Other rules are not implemented.

Domain Model

Stable. Current objects and APIs are not expected to change. The EMF bpmn package will be generated from the ecore when we migrate the modeler to Eclipse-3.3: at the same time than the rest of STP. We have tested that it works and the EMF team has solved a bug uncovered then.

BPMN properties

Not implemented as part of the core modeler. They can be supported as annotations of the domain model. Annotations are displayed in the properties view.

Reusing the modeler

Connections

Sequence and Messaging edges are using custom routers and connection anchors. Currently only the fastest route algorithm is well supported. Bugzilla number: (when bugzilla is back).

Copy/Paste

Working.

Preferences

All shapes can have their default background color customized. All connections can have their routing style customized. More preferences to come.

Documentation

To be written.

Back to the top