Plugins everywhere! Joget Workflow provides an improved plugin architecture that supports both normal Java and dynamic OSGI plugins.

Plugin Types

Process Plugins

Form Plugins

Datalist Plugins

Userview Plugins

General Plugins

Development Approach

The method of developing a Joget plugin remains the same as described in Developing Plugins. However, you now have the option of using an additional feature: standard Java classes.  Standard Java classes are read directly from the classpath.

The following table highlights the different approaches:

Dynamic OSGI Plugin

Standard Java Plugin

Build as an OSGI JAR bundle

Build as a standard Java JAR

Deploy JAR using the Manage Plugins in the Web Console

Make JAR available in the Java classpath (e.g., place it under WEB-INF/lib)

Supports dynamic loading/unloading/reloading without restarting

Requires restarting the JVM for deployment or changes

Runs in isolated mode, thus, preventing library version conflict with base libraries or other plugins

May cause library version conflicts with base libraries or other plugins

More difficult to develop and test due to OSGI configuration and isolation

Easier to develop and test using normal Java classes and libraries


Java class path starts with org.joget.