All the libraries on which jPDL might have a dependency, are located in the lib directory. The actual version of those libraries might depend on the JBoss server that you've selected in the installer.
In a minimal deployment, you can create and run processes with jBPM by putting only the commons-logging and dom4j library in your classpath. Beware that persisting processes to a database is not supported. The dom4j library can be removed if you don't use the process xml parsing, but instead build your object graph programatically.
Table 4.1.
| Library | Usage | Description |
|---|---|---|
| commons-logging.jar | logging in jbpm and hibernate | The jBPM code logs to commons logging. The commons logging library can be configured to dispatch the logs to e.g. java 1.4 logging, log4j, ... See the apache commons user guide for more information on how to configure commons logging. if you're used to log4j, the easiest way is to put the log4j lib and a log4j.properties in the classpath. commons logging will automatically detect this and use that configuration. |
| dom4j.jar | process definitions and hibernate persistence | xml parsing |
A typical deployment for jBPM will include persistent storage of process definitions and process executions. In that case, jBPM does not have any dependencies outside hibernate and its dependent libraries.
Of course, hibernate's required libraries depend on the environment and what features you use. For details refer to the hibernate documentation. The next table gives an indication for a plain standalone POJO development environment.
Table 4.2.
| Library | Usage | Description |
|---|---|---|
| hibernate.jar | hibernate persistence | the best O/R mapper |
| antlr.jar | used in query parsing by hibernate persistence | parser library |
| cglib.jar | hibernate persistence | reflection library used for hibernate proxies |
| commons-collections.jar | hibernate persistence | |
| asm.jar | hibernate persistence | asm byte code library |
The beanshell library is optional. If you don't include it, you won't be able to use the beanshell integration in the jBPM process language and you'll get a log message saying that jbpm couldn't load the Script class and hence, the script element won't be available.
Table 4.3.
| Library | Usage | Description |
|---|---|---|
| bsh.jar | beanshell script interpreter | Only used in the script's and decision's. When you don't use
these process elements, the beanshell lib can be removed, but then you
have to comment out the Script.hbm.xml mapping line in the
hibernate.cfg.xml |