Last week the Eclipse board accepted the project proposal "Java Workflow Toolbox (JWT)" as a new subproject under the Eclipse Technology project. AgilPro will probably be the courner stone of this upcoming project and the project leads of AgilPro are in the advisory board and among the project leads of Eclipse JWT.
In JWT which is supported by companies and institutes like ObjectWeb, JBoss and TIBCO, the interoperability between workflow editors and workflow engines is the key point. Currently, if an application is working with one process engine it is not easily possible to switch to another one. A set of generic APIs is necessary to achieve this generalicity.
AgilPro with its basis on EMF and GEF will be adapted to be conform to an interface which will be defined in the context of the JWT project.
Florian Lautenbacher
JWT project lead
AgilPro administrator
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Last week the Eclipse board accepted the project proposal "Java Workflow Toolbox (JWT)" as a new subproject under the Eclipse Technology project. AgilPro will probably be the courner stone of this upcoming project and the project leads of AgilPro are in the advisory board and among the project leads of Eclipse JWT.
In JWT which is supported by companies and institutes like ObjectWeb, JBoss and TIBCO, the interoperability between workflow editors and workflow engines is the key point. Currently, if an application is working with one process engine it is not easily possible to switch to another one. A set of generic APIs is necessary to achieve this generalicity.
AgilPro with its basis on EMF and GEF will be adapted to be conform to an interface which will be defined in the context of the JWT project.
Florian Lautenbacher
JWT project lead
AgilPro administrator