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/IM Component/Discussion on STP IM and JWT"

(Collaboration Scope)
Line 7: Line 7:
  
 
== Collaboration Scope ==
 
== Collaboration Scope ==
 +
The STP-IM elements that correspond to process/workflow editors in STP (e.g. BPMN, BPEL) as well as to architecture definition editors and platforms in STP (e.g. JBI and SCA). For the purpose of the collaboration with the JWT project, the elements corresponding to the process/workflow part are of particular interest.
 +
So far the discussions between the two teams have focused primarily on the following subjects:
 +
- deeper understanding of the general design of STP-IM and JWT metamodels
 +
- identification of points of interest for collaboration
 +
- definition of first practical steps to achieve interoperability
 +
 +
=== Current understanding ===
 +
 +
=== Follow-up Actions ===
  
 
== Discussion Threads ==
 
== Discussion Threads ==

Revision as of 12:01, 9 January 2008

Preliminary

The STP Intermediate Metamodel (STP-IM) is a "bridge" between STP editors and its elements have the role of conceptual transport between different development spaces with the purpose of capturing as much common SOA design information as possible.

Similarly, the Java Workflow Tooling project defines a metamodel as part of its mission to unify different workflow definition languages. This metamodel provides a consistent and complete set of elements to respond to the needs of a generic workflow editor and engine while at the same time covering most current workflow languages and standards.

Given the similarities in the needs and purposes of STP-IM and JWT, discussions have been initiated with the aim to improve communication, sharing and collaboration between the two projects. This page is intended as a living space where information on the status of this collaboration is kept up to date.

Collaboration Scope

The STP-IM elements that correspond to process/workflow editors in STP (e.g. BPMN, BPEL) as well as to architecture definition editors and platforms in STP (e.g. JBI and SCA). For the purpose of the collaboration with the JWT project, the elements corresponding to the process/workflow part are of particular interest. So far the discussions between the two teams have focused primarily on the following subjects: - deeper understanding of the general design of STP-IM and JWT metamodels - identification of points of interest for collaboration - definition of first practical steps to achieve interoperability

Current understanding

Follow-up Actions

Discussion Threads

Back to the top