Hi Clint,
The internal Activity Model is currently not exposed via public Java API. The reason is that it is the internal process definition structure used by the process engine. I am a bit reluctant about exposing it. I see two problems:
- The process definition is structurally not 100% aligned with BPMN. Example: boundary events are nested inside the scope they are attached to instead of being siblings of the scope they are attached to as in BPMN. And concerns like isScope, isAsync, isExclusive are proprietary process engine internal implementation details.
- I want to reserve the possibility of changing this dramatically (for the better of course J)
So if you want to expose a process definition model as JSON Document through the REST Api, I would be in favor of not exposing the proprietary process engine internal structures but rather parsing the BPMN 2.0 Xml and returning a Structure that is aligned with BPMN 2.0.
FYI: What we do in cockpit is we have a client-side Javascript based parser for BPMN 2.0 XML (https://github.com/camunda/camunda-bpmn.js) which we can use for obtaining all activities from the BPMN 2.0 XML. Then we use the activity instance tree that can be obtained via public API and is structurally aligned with the BPMN 2.0 XML and map the runtime state of a process instance to the process definition.
http://docs.camunda.org/api-references/rest/#!/process-instance/get-activity-instances
Cheers,
Daniel Meyer
--
You received this message because you are subscribed to the Google Groups "camunda BPM platform internal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to camunda-bpm-d...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.