Skip to content

Plugin development guide

AlekseyAleev edited this page Aug 3, 2012 · 1 revision

One of the main genesis extension points is ability to provide new kinds of execution steps to workflow engine.

This is possible via genesis plugin mechanism.

To introduce new execution step to genesis one should provide implementations for following components (workflow engine description) :

  • Plugin context - main configuration of the plugin, responsible for creating and configuring other components
  • Step definitions and step builders - components responsible for interpretation of execution definition from template dsl
  • Actions - single action performed inside particular step
  • Action executors - components responsible for actual executing workflow step
  • Step coordinator factory - component responsible for mapping workflow actions to appropriate executor

Module and packaging

It's recommended to packaged plugin as a jar file. For genesis being able to discover plugin it should be put into execution classpath.

"internal-api" and "api" modules should be used during development, but should not be distributed with plugin package.

Specific guides

Clone this wiki locally