Be the first to like this
This talk will present and demonstrate the new SOA-related Eclipse project, Mangrove - SOA Modeling Framework, part of the new Eclipse SOA top level project. Mangrove is an evolution from the Eclipse STP Intermediate Model (STP-IM), a component that served as the basis for interconnecting different editors in the SOA Tools Platform project and which has itself evolved to become the Eclipse SOA project.
Mangrove has a larger scope than STP-IM as well as exciting new features such as
synchronizing various SOA artifacts using an automatic builder
updating model information in SOA editors with runtime data from monitoring
feeding model information to deployment tools
connecting with model and service repositories
The Mangrove SOA Modeling Framework comprises the following components that support the above-mentioned features. Not all components are fully implemented and the degree of maturity varies among them. The presentation will specify the status of each component so that attendees can leave with a clear understanding of what can be used today and what is work in progress.
Core - the Core Metamodel and API: contains the SOA elements and their inter-relations, enabling the storing of distilled SOA elements used by different editors and tools.
Branches - the Transformation Plug-ins: contain the logic required to move and convert information between editors, tools and the core metamodel instance.
Phloem - the Builder: ensures the constant updating of SOA artifacts in the core as well as in the corresponding editors and tools (e.g. when saving a diagram, update the appropriate artifacts in the core while also enabling the update of the corresponding artifact in related editors or tools).
Leaves - the Editor Extensions, extensions and improvements to editors and tools for adding Mangrove-specific functionality at design time (e.g. views allowing the enrichment of certain SOA elements in the core or configuration menus for customizing the amount of information to be moved to/from the core).
Roots - the Runtime Connections: for moving information to and from runtime tools and repositories when needed in order to have a “living” core, providing a good reality snapshot. This can be useful when diagrams are out of sync or when aggregated monitoring information is required to update graphical elements. Also for generating deployment information in a common format.
The talk will present the new project focusing on parts that haven't been presented before in the context of STP-IM. It will also demonstrate using a basic SOA example how information can be transported between BPMN and SCA editors, how the builder works behind the scenes to automatically save artefacts and finally how monitoring information can be transported and presented in the SCA editor.