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 "Eclipse Summit 2007"
(New page: == '''Background''' == JWT project will be presented at the '''Eclipse Summit Europe 2007''' which will be held from Oct. 9 - Oct. 11, 2007 in Stuttgart Region, Germany. The content for t...) |
(→'''Outline''') |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
== '''Presentation Content''' == | == '''Presentation Content''' == | ||
| − | The | + | The given presentation can be found on the project web site under http://www.eclipse.org/jwt/press/ese07/index.php. |
| − | + | == '''Proposed Outline''' == | |
| − | + | ||
| − | + | Title: Eclipse Java Workflow Tooling (JWT) | |
| − | + | ||
| − | + | Content: In our talk we will present the current work in the Java Workflow Tooling (JWT) project. The goal of the JWT project is to develop a set of tools that help to develop, deploy and test workflows. JWT is not just another modeling tool and workflow engine, but provides an adaptable framework for different graphical representations and XML notations, as well as different workflow engines. | |
| + | The JWT project aims to provide both build-time and runtime generic tools for workflow engines. | ||
| + | The Java workflow tooling is composed of two tools, the workflow editor (WE) and the workflow engine administration and monitoring tool (WAM). | ||
| + | The WE is a visual tool for creating, managing and reviewing process definitions. Straightforward and simple, WE let users quickly create workflow process definitions, check and store them for further use. Once a process definition is proved valid, it can be imported/referenced into new ones, thus shortening the time and effort needed to define the workflow process. WE provides several views: for business managers to change the control flow of a process, for technical experts to invoke services, and others. | ||
| + | The WAM on the other side is used to deploy and test a workflow in a workflow engine so to handle an engine's process definition external repository, to load some process definitions into a specific Workflow Engine, unload it, update it, instantiate it, monitor the Workflow Engines processes, perform mappings among participant definitions and real users, and among application definitions and tool agents. | ||
| + | We will also outline the achieved work so far and the plans for the future. | ||
| + | |||
| + | == '''Shown Outline''' == | ||
| + | |||
| + | As presented on the Eclipse Summit Europe Homepage (http://eclipsesummit.org/summiteurope2007/index.php?page=detail/&id=61): | ||
| + | |||
| + | The goal of the JWT project is to develop a set of tools that help to develop, deploy and test workflows. JWT is not just another modeling tool and workflow engine, but provides an adaptable framework for different graphical representations and XML notations, as well as different workflow engines. | ||
| + | |||
| + | The JWT project aims to provide both build-time and runtime generic tools for workflow engines. The Java workflow tooling is composed of two tools, the workflow editor (WE) and the workflow engine administration and monitoring tool (WAM). | ||
| + | |||
| + | We will present the goals, the existing code and the vision of the JWT project. In our talk we will also outline what work has been achieved so far and our plans for the future. | ||
| + | |||
| + | == '''JWT Integrations within development and runtime platforms''' == | ||
| + | * JWT and STP | ||
| + | * JWT for the SCOrWare project : | ||
| + | ''The SCOrWare project aims to provide a free software implementation of the recently released Service Component Architecture (SCA) specifications, as defined by the Open SOA Collaboration group. It will consists in an SOA platform comprising a runtime engine as well as eclipse-based tools. Among those JWT will provide the BPM tooling framework. The french public research-funded SCOrWare project gathers the following partners : Amadeus, Artenum, EBM WebSourcing, Edifixio, eXo platform, INRIA, INT, IRIT, Obeo and Open Wide.'' | ||
Latest revision as of 09:40, 12 October 2007
Contents
Background
JWT project will be presented at the Eclipse Summit Europe 2007 which will be held from Oct. 9 - Oct. 11, 2007 in Stuttgart Region, Germany. The content for the Summit will be a collaborative effort by all interested parties.
Submission Process Dates
- Call for talk proposals opens May 17, 2007
- Call for talk proposals closes June 29, 2007
Presentation Content
The given presentation can be found on the project web site under http://www.eclipse.org/jwt/press/ese07/index.php.
Proposed Outline
Title: Eclipse Java Workflow Tooling (JWT)
Content: In our talk we will present the current work in the Java Workflow Tooling (JWT) project. The goal of the JWT project is to develop a set of tools that help to develop, deploy and test workflows. JWT is not just another modeling tool and workflow engine, but provides an adaptable framework for different graphical representations and XML notations, as well as different workflow engines. The JWT project aims to provide both build-time and runtime generic tools for workflow engines. The Java workflow tooling is composed of two tools, the workflow editor (WE) and the workflow engine administration and monitoring tool (WAM). The WE is a visual tool for creating, managing and reviewing process definitions. Straightforward and simple, WE let users quickly create workflow process definitions, check and store them for further use. Once a process definition is proved valid, it can be imported/referenced into new ones, thus shortening the time and effort needed to define the workflow process. WE provides several views: for business managers to change the control flow of a process, for technical experts to invoke services, and others. The WAM on the other side is used to deploy and test a workflow in a workflow engine so to handle an engine's process definition external repository, to load some process definitions into a specific Workflow Engine, unload it, update it, instantiate it, monitor the Workflow Engines processes, perform mappings among participant definitions and real users, and among application definitions and tool agents. We will also outline the achieved work so far and the plans for the future.
Shown Outline
As presented on the Eclipse Summit Europe Homepage (http://eclipsesummit.org/summiteurope2007/index.php?page=detail/&id=61):
The goal of the JWT project is to develop a set of tools that help to develop, deploy and test workflows. JWT is not just another modeling tool and workflow engine, but provides an adaptable framework for different graphical representations and XML notations, as well as different workflow engines.
The JWT project aims to provide both build-time and runtime generic tools for workflow engines. The Java workflow tooling is composed of two tools, the workflow editor (WE) and the workflow engine administration and monitoring tool (WAM).
We will present the goals, the existing code and the vision of the JWT project. In our talk we will also outline what work has been achieved so far and our plans for the future.
JWT Integrations within development and runtime platforms
- JWT and STP
- JWT for the SCOrWare project :
The SCOrWare project aims to provide a free software implementation of the recently released Service Component Architecture (SCA) specifications, as defined by the Open SOA Collaboration group. It will consists in an SOA platform comprising a runtime engine as well as eclipse-based tools. Among those JWT will provide the BPM tooling framework. The french public research-funded SCOrWare project gathers the following partners : Amadeus, Artenum, EBM WebSourcing, Edifixio, eXo platform, INRIA, INT, IRIT, Obeo and Open Wide.