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:
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?
I would go for testing if there is a processdefinition file. I do not like adding a dirtectory structure in a directory structure (which a zip actually is, albeit compressed)