Jbpm.jar contains some of the default profiles that can be imported into a user configuration file.
This makes it easy for users to choose which features to include or exclude. And the configuration information includes implementations, so users can import only those profiles that work, and when changes are made to the configuration file we release.
The configuration file can be imported into the user's jbpm.cfg.xml:
Jbpm.default.cfg.xml
Jbpm.identity.cfg.xml
Jbpm.jbossremote.cfg.xml
Jbpm.jobexecutor.cfg.xml
Jbpm.tx.hibernate.cfg.xml
Jbpm.tx.jta.cfg.xml
Jbpm.default.cfg.xml: Includes default configurations, such as services, hibernate configuration (from Jbpm.hibernate.cfg.xml configuration), Hibernate session factory, business calendar, and more.
A standard Java configuration looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration>
<import resource="jbpm.default.cfg.xml" />
<import resource="jbpm.tx.hibernate.cfg.xml" />
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<import resource="jbpm.jobexecutor.cfg.xml" />
</jbpm-configuration>
In a JTA environment, replace Jbpm.tx.hibernate.cfg.xml with Jbpm.tx.jta.cfg.xml.
If you want to customize any part of these configurations, you can replace the reference section with custom content in Jbpm.cfg.xml.
Jbpm.jar also contains the following hibernate mapping profiles:
Jbpm.execution.hbm.xml
Jbpm.history.hbm.xml
Jbpm.identity.hbm.xml
Jbpm.repository.hbm.xml
Jbpm.task.hbm.xml
Jbpm.jpdl.hbm.xml
All of these map the Java domain model to a relational database.
Jbpm.jar also contains other profiles:
Jbpm.task.lifecycle.xml
Jbpm.variable.types.xml
Jbpm.wire.bindings.xml
Jbpm.jpdl.activities.xml
Jbpm.jpdl.eventlisteners.xml
How to start parsing from a configuration file, reference
* Class Org.jbpm.pvm.internal.env.JbpmConfigurationParser
* Resource Modules/pvm/src/main/resources/jbpm.wire.bindings.xml
* Package modules/pvm/src/main/java/org/jbpm/pvm/internal/wire/binding