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.
Difference between revisions of "STP/IM Component/Plug-in Structure"
< STP | IM Component
Line 7: | Line 7: | ||
|- | |- | ||
| org.eclipse.stp.im | | 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 | | org.eclipse.stp.im.edit | ||
− | | Generated by EMF | + | | Generated by [[EMF]]. Contains Java code to edit instances of STP-IM. |
|- | |- | ||
| org.eclipse.stp.im.editor | | org.eclipse.stp.im.editor | ||
− | | | + | | Generated by [[EMF]]. Basic editor to create STP-IM instances. |
|- | |- | ||
| org.eclipse.stp.im.tests | | org.eclipse.stp.im.tests | ||
− | | | + | | Generated by [[EMF]]. Automated JUnit tests for STP-IM instances. |
|- | |- | ||
| org.eclipse.stp.im.in.bpmn | | org.eclipse.stp.im.in.bpmn | ||
− | | | + | | Performs the [[STP/BPMN_Component | BPMN]]->STP-IM transformation. Implemented using the EMF-generated APIs from both metamodels. |
+ | |- | ||
+ | | org.eclipse.stp.im.in.sca | ||
+ | | Performs the [[STP/SCA_Component | SCA]]->STP-IM transformation. Implemented using the EMF-generated APIs from both metamodels. | ||
|- | |- | ||
| org.eclipse.stp.im.resources | | org.eclipse.stp.im.resources | ||
− | | | + | | Defines a common repository for resources that could be needed by STP-IM and provides extension point 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 | | 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 [[STP/BPMN_Component | BPMN]] diagrams. Provide some utility classes so it's possible to define static runtimes, based on xml configuration files. For example the predefined set of services offered by ESB could be defined in an xml file. Another exmaple of runtime, could be the set of activities offered by BPEL engine. BTW it's important to say that xml is only a way to define runtimes, but it's not the unique way, basically to define a new runtime you need only to write a plugin that use the extension point defined in this plugin and provide a class that implements the IRuntime interface. An example of runtime is provided by "org.eclipse.stp.im.runtime.jbi.smx" plugin |
|- | |- | ||
| org.eclipse.stp.im.runtime.jbi.smx | | org.eclipse.stp.im.runtime.jbi.smx |
Revision as of 00:20, 11 May 2008
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.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.resources | Defines a common repository for resources that could be needed by STP-IM and provides extension point 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. Provide some utility classes so it's possible to define static runtimes, based on xml configuration files. For example the predefined set of services offered by ESB could be defined in an xml file. Another exmaple of runtime, could be the set of activities offered by BPEL engine. BTW it's important to say that xml is only a way to define runtimes, but it's not the unique way, basically to define a new runtime you need only to write a plugin that use the extension point defined in this plugin and provide a class that implements the IRuntime interface. An example of runtime is provided by "org.eclipse.stp.im.runtime.jbi.smx" plugin |
org.eclipse.stp.im.runtime.jbi.smx | Define the set of service/servicebindings offered by servicemix, using the xml configuration file. |
org.eclipse.stp.im.tool.in.bpmneditor | Extension to the BPMN editor:
|