Skip to main content
Jump to: navigation, search

STP/IM Component/STP Internal Model Discussion

This page aims to serve as a starting point for a discussion on the internal representation of artefacts in Eclipse STP. It is envisaged that several editors will be used separately or in coordination in order to create SOA entities and architectures. Examples of such editors include

  • SCA Editor
  • JBI Editor
  • BPMN editor
  • BPEL editor

Each editor uses its own internal (meta-)model corresponding to its underlying foundation (SCA, JBI etc).

Internal Models (e.g. SCA and JBI)

This subsection presents a very simplified and limited subset of the (meta-)models for SCA and JBI.

SCA-model.png TODO: a few words describing the SCA model. JBI-model.png TODO: a few words describing the JBI model.

Consistent Representation in STP

It is desirable that there be a consistent representation of the main artefacts created or used in Eclipse STP. A Service for instance should be available to architects and developers using either editor / technology. In particular, a service appearing in the logical architecture designed with SCA should be rendered "accessible" in the JBI editor or indeed in the BPMN or BPEL editors. It should be "same service" that is used everywhere across STP. We should aim to have minimum redundancy in the design process.

Model Transformation

Back to the top