JBPM Spring Integration

Spring Integration

The default jBPM behavior is to open a transaction for each operation that is called on the service API. In a typical Spring setup, applications are accessed from the web tier and enter a transactional boundary by invoking operations on service beans. These service beans will then access the jBPM services. All these operations run typically in a single transaction (ie one transaction per request from the browser), which invalidates the standard jBPM transaction handling approach. Instead of starting and committing a transaction for every service operation, the existing transaction should be used (or a new one started if none exists).