I've just commited an update of jbpm integration code which contains the following updates:
1. addresses bugs reported on this forum, namely MOD-75, MOD-79, MOD-58
Some methods have been moved/renamed in order to resemble as much as possible with the ORM package structure. Internally Spring Hibernate was used as much as possible which should make the code portable between different transactional environment (JTA/LocalTM).
2. beans defined inside Spring application context can be accessed from JBPM: see SpringHandler javadoc for an explanation and an example. There were several approaches suggested inside the forum - this implementation
relies on a lookup class which uses a custom BeanFactoryLocator and does not affect in anyway the jBPM context.
Please test and report back (on jira) any issues that you may found, preferably with a test that reproduces the problem. jBPM holds a reference internally to HB transaction and I suspect there might be some corner cases that are not covered by the current implementation.
Next in line is integration with version 3.1.x.
I'd like to thank all the users that have reported their problems on the forum, JIRA and posted their ideas and solutions - they made my 'job' easier.