Decide what to do with the modeller_bpmn module

Created on 27 March 2025, 2 months ago

Problem/Motivation

The modeller_bpmn module in the eca package is an abstract base class, used by the bpmn_io module and possibly other modules that provide modelers. If it stays in the eca package, then any module using modeler_api and bpmn_io will have to depend on eca.

Should we move this class to the modeler_api module or to the bpmn_io module? If we choose the bpmn_io module, then other modelers will have to depend on it.

Furthermore, the class is complex (1019 lines) and tightly coupled to the eca module. How we move it will depend on 🌱 Decide what to do with TargetInterface Active . I will add that as a related issue, but maybe this issue should be postponed on that one.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🌱 Plan

Status

Active

Component

Code

Created by

🇺🇸United States benjifisher Boston area

Live updates comments and jobs are added and updated live.

alpha target

Comments & Activities

Issue created by @benjifisher
Comment 2 months ago →
🇩🇪Germany jurgenhaas Gottmadingen
That abstract class has gone as part of 📌 Start moving code from the ECA module Active .

Also, the current version of modeler_api has no knowledge about the target config entities at all, it can and should not talk to them directly. The API talks to the ModelOwner plugin which knows everything about those config entities. That's why I had to remove the TargetInterface. And it all works so nicely and as expected.
Comment about 2 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024