6.2. Package

As introduced in section 3.1 (Conceps), the package element within an XPDL file contains: processes, participants, datafields..... Multiple processes can be deployed. These processes can share participants and datafields.

Deploying processes implies to deploy at leat a package (ie. the XPDL file that contains the package element). Package is the unit of deployment.

The notion of package concerns also the scope for the deployed java classes (for hooks, mappers and performer assignments). If these classes are deployed at same time of the package deployment, these classes are dependant on the package and visible for all processes of the package (and there activities). The undeployment of the package will undeploy all these classes. Classes could be also deployed at global level and acceded by the processes/activities of all the packages.

QueryDefinitionAPI gives access to all deployed and undeployed package informations with the default environment configuration.

6.2.1. LifeCycle

A package has its own life cycle:

  • Deployed: after the deployment operation (calling the Management API) state of the package is deployed.

  • Undeployed: when undeploy() operation is performed the state of the package becomes undeployed. An 'undeployed-package-handler' is then called. With the default environment configuration, recorded data for deployed package are archived (history).