I'm evaluating jBPM 4.1. Currently if you take for example a simple PDF file and rename the extension to BAR/PAR to indicate it's a process archive, it will get deployed without any warnings or errors!

The solution we envisage to avoid this problem is by imposing the presence of a file JBPM_LISTING in the BAR/PAR:

MyProcesses.bar/
META-INF/
JBPM_LISTING
myprocesses/
Process.jpdl.xml
Subprocess.jpdl.xml
InformationVO.class
Translations.properties

with JBPM_LISTING:

myprocesses/Process.jpdl.xml
myprocesses/Subprocess.jpdl.xml
myprocesses/InformationVO.class
myprocesses/Translations.properties

During pre-deployment, if JBPM_LISTING contains an entry for a file that doesn't exist in the PAR/BAR then it would throw a validation error. Similar behaviour if files are discovered in the PAR/BAR which aren't defined in JBM_LISTING.

Q : would it be interesting to include this kind of feature in the JBPM roadmap?