STP/IM Component/Plug-in Structure

The following is a list of the plug-ins currently available in the SVN repository and their description.

Plug-in Name	Description
org.eclipse.stp.im	Generated by EMF. Can be seen as the core plug-in, as it contains the STP-IM metamodel description (model/stpmodel.ecore).
org.eclipse.stp.im.edit	Generated by EMF. Contains Java code to edit instances of STP-IM.
org.eclipse.stp.im.editor	Generated by EMF. Basic editor to create STP-IM instances.
org.eclipse.stp.im.tests	Generated by EMF. Automated JUnit tests for STP-IM instances.
org.eclipse.stp.im.feature	Contains the feature.xml file for deployment in the Eclipse platform.
org.eclipse.stp.im.in.bpmn	Performs the BPMN->STP-IM transformation. Implemented using the EMF-generated APIs from both metamodels.
org.eclipse.stp.im.in.sca	Performs the SCA->STP-IM transformation. Implemented using the EMF-generated APIs from both metamodels.
org.eclipse.stp.im.out.sca	Performs the STP-IM transformation-> SCA. Implemented using the EMF-generated APIs from both metamodels.
org.eclipse.stp.im.resources	Defines a common repository for resources that could be needed by STP-IM and provides extension points for exporting and importing these resources into this repository. At the moment this plug-in provides the dialog to manage datasources.
org.eclipse.stp.im.runtime	Defines the concept of Intermediate Model Runtime: A runtime defines a set of services/service bindings to drag and drop on Activities on BPMN diagrams. It provides utility classes to make possible the definition of static runtimes, based on XML configuration files. For example the predefined set of services offered by an ESB or the set of activities offered by BPEL engine could be both rutimes, defined in XML files. It's important to make clear that XML is only a way to define runtimes, but it's not the unique way. To define a new runtime, you only need to write a plug-in that uses the extension point defined in this plug-in and provide a class that implements the IRuntime interface. Examples of this are org.eclipse.stp.im.runtime.bpel and org.eclipse.stp.im.runtime.jbi.smx for BPEL and JBI, respectively.
org.eclipse.stp.im.runtime.jbi.smx	Defines the set of Service/ServiceBindings offered by Apache ServiceMix, using an XML configuration file.
org.eclipse.stp.im.runtime.bpel	Defines the set of Service/ServiceBindings offered by BPEL, using an XML configuration file.
org.eclipse.stp.im.tool.in.bpmneditor	Provides the following extensions to the BPMN Editor: Provided Technology Section in properties view, this section is used to choose a particular runtime for BPMN Pool. Intermediate Model View. When you choose a runtime for a Pool the set of service service bindings provided by this, are shown in this view and you could do drag and drop on BPMN Activity elements. Provided Intermediate Model Section. Once you drag and drop a Service/ServiceBinding on a BPMN element, this will create an annotation on BPMN Element containing the properties this Service/ServiceBinding needs to work on the runtime. In this section you're able to edit the properties defined by a particular Service/ServiceBinding annotation.

Thanks to Andrea Zoppello who provided some of these descriptions at stp-dev.