1 of 1 people found this helpful
I believe you're right, the only way to change persistence of task service is to have custom JPA provider that will take care of the storage in JCR. It's not pluggable as it is in case of runtime engine.
Well... maybe an improvement idea for jBPM6? To make the persistence (and other stuff) pluggable? E.g. notifications, so they could be not only in e-mail form, but SMS, instant messages, ...
just looked once again into it and what could be worth trying is to extend TaskPersistenceManager that encapsulates use of EntityManager inside task service. Maybe it will be possible to simply change implementation of that using with new implementation of TaskSessionFactory.
Regarding improvements, feel free to create jira issues for them.