Jump to: navigation, search

Difference between revisions of "STP/IM Component/Plug-in Structure"

(Undo revision 97035 by Juanjosecg.gmail.com (Talk))
Line 25: Line 25:
 
|-
 
|-
 
| 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.
+
| 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
 
| 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
+
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. 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
 
| org.eclipse.stp.im.runtime.jbi.smx
| Define the set of service/servicebindings offered by servicemix, using the xml configuration file.
+
| Define the set of service/service bindings offered by [[http://servicemix.apache.org/ | Apache ServiceMix]], using an XML configuration file.
 
|-
 
|-
 
| org.eclipse.stp.im.tool.in.bpmneditor
 
| org.eclipse.stp.im.tool.in.bpmneditor

Revision as of 00:46, 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 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 Define the set of service/service bindings offered by [| Apache ServiceMix], using an XML configuration file.
org.eclipse.stp.im.tool.in.bpmneditor Extension 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 showed in this view and you could do drag and drop on bpmn 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/servicebing need to work, in this section you're able to edit the properties defined by a particular service/servicebinding annotation.