Architectural Question: Using Activiti In a Spring Web App

[euploid]

We have a web application built on top of Sping, Spring MVC, and Hibernate (not JPA-compliant). We would like to use Activiti for our process flow management. What would be the best way to layer Activiti given our current application architecture?

Specifically, here are some of my more technical questions:

1) I would like to keep the database used by Activiti separate from the database used in our application. The means we will have two separate database connections. How do we coordinate transactions used by Activiti with transactions in our application? Do I need to use JTA? Does Activiti support it?

2) Sharing data. Tasks in Activiti would need to access our data to determine the transition logic. What's the best way to do this?

3) Activiti doesn't support Hibernate. What changes do I need to make to our domain objects to make them work with Activiti.

Any suggestions or advice would be much appreciated.

[ronald_van_kuij]

1: yes, read the docs
2: there is no 'best way' since it depends on what you already have, but an 'easy' way would be using JPA (see the docs again)
3: If you cannot switch to JPA (see answer on two), then writing a similar layer in Activiti would be an option