Jump to: navigation, search

Difference between revisions of "STP/IM Component/STP Internal Model Discussion"

Line 8: Line 8:
 
Each editor uses its own internal (meta-)model corresponding to its underlying foundation (SCA, JBI etc).
 
Each editor uses its own internal (meta-)model corresponding to its underlying foundation (SCA, JBI etc).
  
The following subsections present a very simplified and limited subset of the (meta-)models for SCA and JBI.
 
  
== SCA ==
+
== Internal Models (e.g. SCA and JBI) ==
[[Image:SCA-model.png]]
+
This subsection presents a very simplified and limited subset of the (meta-)models for SCA and JBI.  
  
== JBI ==
+
[[Image:SCA-model.png]]
 +
TODO: a few words describing the picture.
 
[[Image:JBI-model.png]]
 
[[Image:JBI-model.png]]
 +
TODO: a few words describing the picture.
 +
 +
== Consistent Representation in STP==

Revision as of 09:40, 21 June 2007

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 picture. JBI-model.png TODO: a few words describing the picture.

Consistent Representation in STP