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 "JWT Validation"
(→Ideas/Requirements) |
(→Ideas/Requirements) |
||
| Line 4: | Line 4: | ||
* The ability to integrate a simple Java validator | * The ability to integrate a simple Java validator | ||
* An extensible builder in which one anyone could put its set a validators => A builder requires a nature (ie workflow become project and not simple files) | * An extensible builder in which one anyone could put its set a validators => A builder requires a nature (ie workflow become project and not simple files) | ||
| + | |||
| + | |||
| + | = Current implementation = | ||
| + | |||
| + | Some students at the University of Augsburg are currently working on a validation plugin. Basically, it allows to validate a structured process model whether there might be a deadlock. Their work builds on a research paper by some guys at [http://domino.watson.ibm.com/library/cyberdig.nsf/1e4115aea78b6e7c85256b360066f0d4/df5d1d2bcb32a31b8525737900529787?OpenDocument IBM] and considers work already done in the [http://sourceforge.net/projects/wf-codegen/ Workflow Code Generation Framework]. Their schedule is to finish the conceptual design in the next weeks and the implementation until January. | ||
= Resources = | = Resources = | ||
[[EMF/MQ, MT, and VF 1.1/New and Noteworthy]] | [[EMF/MQ, MT, and VF 1.1/New and Noteworthy]] | ||
Revision as of 11:34, 4 November 2008
Ideas/Requirements
- A rule language to express constraints on the currently edited model
- The ability to integrate a simple Java validator
- An extensible builder in which one anyone could put its set a validators => A builder requires a nature (ie workflow become project and not simple files)
Current implementation
Some students at the University of Augsburg are currently working on a validation plugin. Basically, it allows to validate a structured process model whether there might be a deadlock. Their work builds on a research paper by some guys at IBM and considers work already done in the Workflow Code Generation Framework. Their schedule is to finish the conceptual design in the next weeks and the implementation until January.