|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
APIAccessor | Helper class giving access to QueryDefinitionAPI , QueryRuntimeAPI ,
ManagementAPI , DefinitionAPI , RuntimeAPI and CommandAPI interfaces. |
CommandAPI | To allow developpers to write and execute its own commands packaged within its application. |
DefinitionAPI | Not supported. |
ManagementAPI | Workflow process deployment operations. |
QueryAPIAccessor | Helper class giving access to QueryDefinitionAPI and QueryRuntimeAPI interfaces. |
QueryDefinitionAPI | Getters on the workflow definition data for: packages processes activities participants As indicated by its prefix: Query, this interface could be seen as complementary to the QueryRuntimeAPI interface. |
QueryRuntimeAPI | Getters on workflow recorded data. |
RuntimeAPI | To manage process, process instance and task life cycle operations as well as to set/add/update variables within activity or instance. |
Class Summary | |
---|---|
APIConfig |
Nova Bonita Workflow APIs for handling workflow definition, deployment, execution and history.
Nova Bonita is the name of new version of Bonita v4.
"Nova" technology is based on the "Process Virtual Machine" conceptual model for processes. The Process Virtual Machine defines a generic process engine enabling support for multiple process languages (such BPEL, XPDL).
Nova Bonita is an extensible and embeddable workflow solution that can be easily deployed in both standard (JSE) and Enterprise (JEE) environments.
As a example of this, Nova Bonita provides a default JEE integration
with a EJB3 lightweight container
such Easybeans
. You can easily deploy Nova Bonita in another JEE application
server by just deploying the bonita.ear file in your
favorite application server.
Nova Bonita APIs are divided into 5 different areas:
DefinitionAPI
: to create/modify major
process elements into the engine (packages,
processes, activities, role mappers, variables by calling java methods
instead of importing xpdl files. It will allows also to
modify the execution of runtime elements such as tasks and instances.QueryDefinitionAPI
: to get
definition/static informations for elements defined in the xpdl file:
packages, processes, activities, participants, hooks, mappers,
performer assignments.RuntimeAPI
: to manage process,
instance and task life cycle operations as well as to set/updates
variables.QueryRuntimeAPI
: ManagementAPI
: to deploy workflow
processes into the engine. XPDL files and advanced entities
such hooks, mappers and performer assignments can be deployed
individually or in one shot.CommandAPI
: to allow developpers to
execute its own commands (package within the application).
Nova Bonita local vs remote applications
An utility class has been provided to unify access to Bonita APIs from both local and remote environments
and so to avoid the use of lookups in JEE deployments: org.ow2.bonita.util.AccessorUtil. Through this
class, Nova Bonita APIs can be reached in a unified way in both local and remote applications. From a
developer point of view Nova Bonita APIs are just Java POJOs.
The AccessorUtil objet will also be leveraged inside BPM artifacts such hooks, mappers or performer assignments to deal with Nova Bonita APIs.
For that to be done, the system property called "org.ow2.bonita.api-type" must be defined at client side to specify whether the APIs will be reached locally or remotely (possible values are "Standard","AutoDetect",'EJB2" and "EJB3").
There are two available methodes in the AccessorUtil class (under the org.ow2.bonita.util package):
Hereafter you will find an example on how to use the AccessorUtil class from your client application:
RuntimeAPI runtimeAPI = AccessorUtil.getAPIAccessor().getRuntimeAPI();
QueryRuntimeAPI queryRuntimenAPI = AccessorUtil.getQueryAPIAccessor().getQueryRuntimeAPI();
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |