A list of differences between traditional BPM and jBPM :
* Traditional BPM process engines focus only non-technical people while jBPM process engines focus technical and non-technical people both.
* jBPM is easily embeddable into a Java project while traditional BPM systems require a separate server to be installed which makes it difficult to integrate into the Java software development cycle.
* jBPM supports for multiple process languages while the view of BPM is not yet stabilized. There are currently many different interpretations of BPM, which result in big fragmentation in the market.
* jBPM has very flexible transaction management. If the application uses a JDBC connection in the Java environment, then jBPM uses that JDBC connection to perform its task. If our application uses hibernate then, jBPM can use the same hibernate session factory. If our application runs in an enterprise environment, then jBPM can bind with the surrounding JTA transaction while BPM doesn't support these things.
