bug 413267: [proposal] soa.winery
https://bugs.eclipse.org/bugs/show_bug.cgi?id=413267
diff --git a/soa.winery/BMWi_4C_M-Gef.jpg b/soa.winery/BMWi_4C_M-Gef.jpg
new file mode 100644
index 0000000..f185eff
--- /dev/null
+++ b/soa.winery/BMWi_4C_M-Gef.jpg
Binary files differ
diff --git a/soa.winery/overview.png b/soa.winery/overview.png
index 6feaecb..7bcfe09 100644
--- a/soa.winery/overview.png
+++ b/soa.winery/overview.png
Binary files differ
diff --git a/soa.winery/proposal.html b/soa.winery/proposal.html
index cf9d291..8fe84dd 100644
--- a/soa.winery/proposal.html
+++ b/soa.winery/proposal.html
@@ -20,7 +20,7 @@
<body>
<p>
The Winery project is a proposed open source project under the <a
- href="http://www.eclipse.org/projects/project_summary.php?projectid=soa">SOA
+ href="http://www.eclipse.org/projects/project_summary.php?projectid=Technology">Technology
Top Level Project</a>.
</p>
@@ -68,29 +68,34 @@
<h2>Out of Scope</h2>
<p>
-Winery offers a BPMN modeler, which supports modeling executable processes for managing application topologies.
-This puts a full support of the complete BPMN language out of scope.
+Winery offers extension points to include other web-based plan modelers.
+Besides the BPMN4TOSCA plan modeler, the development of other web-based plan modeling tools is out of scope.
</p>
<p>
-Workflow engines typically execute BPEL, therefore BPMN4TOSCA has to be converted to BPEL.
+Besides other languages, BPMN and BPEL may be used to describe executable processes.
+Therefore, BPMN4TOSCA should be to be converted to plain BPMN and to plain BPEL.
+The conversion of BPMN4TOSCA to plain BPMN is in scope of this project.
A conversion of BPMN processes to BPEL processes is not in the scope of this project.
-This part may be done under the hood of the <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.mangrove">Mangrove</a> or <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.bpel">BPEL</a> project.
+This part might be pursued under the hood of the <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.mangrove">Mangrove</a> or <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.bpel">BPEL</a> project.
</p>
<h2>Description</h2>
-<img src="overview.png" height="203px" />
+<img src="overview.png" height="300px" />
<p>
-Winery consists of four parts: (1) Type and template management, (2) topology modeler, (3) BPMN4TOSCA plan modeler, and (4) the repository.
+Winery consists of four parts: (1) the type and template management, (2) the topology modeler, (3) the BPMN4TOSCA plan modeler, and (4) the repository.
</p>
<p>
-The <em>type and template management</em> enables managing all TOSCA types and templates can be managed. This includes node types, relationship types, policy types, artifact types, and artifact templates.
+The <em>type, template and artifact management</em> enables managing all TOSCA types, templates and related artifacts. This includes node types, relationship types, policy types, artifact types, artifact templates, and artifacts such as virtual machine images.
</p>
<p>
The <em>topology modeler</em> enables to create service templates. Service templates consist of instances of node types (node templates) and instances of relationship types (relationship templates). They can be annotated with requirements and capabilities, properties, and policies.
</p>
<p>
-The <em>BPMN4TOSCA plan modeler</em> offers web-based creation of BPMN models with the TOSCA extension BPMN4TOSCA. That means the modeler supports the BPMN elements and structures required by TOSCA plans and not the full set of BPMN. From technology perspective, the BPMN Modeler uses the same techniques as the topology modeler.
+The <em>BPMN4TOSCA plan modeler</em> offers web-based creation of BPMN models with the TOSCA extension BPMN4TOSCA.
+That means the modeler supports the BPMN elements and structures required by TOSCA plans and not the full set of BPMN.
+The <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.stardust">Stardust</a> project offers a <a href="http://wiki.eclipse.org/Stardust/Enhancing_and_Embedding_Stardust/Browser_Modeler">Browser Modeler</a>, which supports BPMN.
+In the context of Winery, this modeler will be extended to support BPMN4TOSCA.
</p>
<p>
The <em>repository</em> stores TOSCA models and allows managing their content. For instance, node types, policy types, and artifact templates are managed by the repository. The repository is also responsible for importing and exporting CSARs, the exchange format of TOSCA files and related artifacts.
@@ -99,13 +104,13 @@
<h2>Relationship with other Eclipse Projects</h2>
<p>
-<a href="http://www.eclipse.org/projects/project_summary.php?projectid=eclipse.orion">Orion</a> offers software development in the browser. It is split into a client and a server. The server part is language agnostic and offers user management and <a href="http://wiki.eclipse.org/Orion/Server_API">APIs</a> to create workspaces and to work with files. Winery's backend currently does not offer any user management. The file storage part of the backend could be replaced by the Orion server, which would bring user management and text-based editing of stored data with the Orion client.
+<a href="http://www.eclipse.org/projects/project_summary.php?projectid=eclipse.orion">Orion</a> offers software development in the browser. It is split into a client and a server. The server part is language agnostic and offers user management and <a href="http://wiki.eclipse.org/Orion/Server_API">APIs</a> to create workspaces and to work with files. Winery�s backend currently does not offer any user management. Winery's file storage could be replaced by an interface to the Orion server, which would bring user management and text-based editing of stored data with the Orion client.
</p>
<p>
The Eclipse project <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.stardust">Stardust</a> provides a comprehensive Business Process Management Suite, which includes a Web-based BPMN modeling component and a workflow execution engine.
-Integration with Winery is not viable, because the Web-based modeling component is tightly coupled with their runtime engine.
-In the context of Winery, we develop a web-based modeling framework, which is instantiated as TOSCA topology modeler and a BPMN4TOSCA modeler.
-Winery does not depend on any BPMN runtime engine.
+We use the Web-based BPMN modeling component as basis for the BPMN4TOSCA plan modeler.
+</p>
+<p>
Plans of arbitrary tools (including Stardust, the <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.bpel">BPEL Designer</a>, the <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.bpmn2-modeler">BPMN2 Modeler</a>, and the <a href="http://www.eclipse.org/projects/project_summary.php?projectid=soa.jwt">Java Workflow Tooling</a>) can be imported.
</p>
<p>
@@ -122,10 +127,12 @@
<h2>Initial Contribution</h2>
<p>
-The initial contribution fully supports TOSCA v1.0:
+The initial contribution covers three parts of winery:
+(1) the type and template management, (2) the topology modeler, and (3) the repository.
+In its current state, Winery fully supports TOSCA v1.0:
TOSCA elements can be created, edited, exported as CSAR, and imported from CSARs.
Service Templates can be graphically modeled, whereby the modeler offers the node types and relationship types stored in the backend.
-Based on this state, the next step is to build the BPMN4TOSCA plan modeler based on the framework defined by the topology modeler.
+The BPMN4TOSCA Plan Modeler is not part of the initial contribution, but will be developed as part of the Winery project.
</p>
<p>
The backend-code is written in Java and JSPs.
@@ -139,7 +146,8 @@
It is intended to dual-license Winery under the Apache License 2.0 and the Eclipse Public License 1.0.
</p>
<p>
-None known. All libraries used in the initial code contribution have licenses approved by the Eclipse Software Foundation.
+There are no known other legal issues.
+All libraries used in the initial code contribution have licenses approved by the Eclipse Software Foundation.
</p>
<h2>Committers</h2>
@@ -191,6 +199,12 @@
</tr>
</table>
+<h2>Acknowledgement</h2>
+<p>
+The initial code contribution has been supported by the <a href="http://www.bmwi.de/EN/root.html">Federal Ministry of Economics and Technology</a> as part of the <a href="http://www.cloudcycle.org/en/">CloudCycle</a> project (01MD11023).
+</p>
+<img src="BMWi_4C_M-Gef.jpg" width="165px"></img>
+
<h2>Changes to this Document</h2>
<table>
@@ -199,6 +213,13 @@
<th>Change</th>
</tr>
<tr>
+ <td>29-07-2013</td>
+ <td><ul>
+ <li>BPMN4TOSCA is retargeted to be built upon Stardust's Browser Modeler</li>
+ <li>Clarified text</li>
+ </ul></td>
+ </tr>
+ <tr>
<td>01-07-2013</td>
<td>Document created</td>
</tr>
