I suggest to have different sessions, one or N for persistent processes and one or N for non persistent processes.

What kind of things do you want to do with JTA in non persistent processes. If the process is non persistent it will not use any JTA resource and for that reason you will need to code that integration with JTA in the application side.

Cheers

On Thu, Mar 7, 2013 at 2:59 PM, Giovanni Marigi <gmarigi@redhat.com> wrote:

Hi,
we have inside the same jbpm engine different processes, some need to be persisted on DBMS and others don't.
Is it possible during the starting phase of a process define (ksession creation for example) if it must be persited or not?

Moreover is it possible to have a process without persistence but "attached" to JTA?

Thanks a lot.

Best Regards,
Giovanni

--
Giovanni Marigi
Red Hat - JBoss Consultant -
email: gmarigi@redhat.com
Mobile: +39 3423175986
Office: +39 0687502315

Red Hat Italy
Via Andrea Doria 41m
00192 Roma - Italy
www.redhat.com

Prima di stampare, pensa all'ambiente ** Think about the environment before printing
_______________________________________________
jbpm-dev mailing list
jbpm-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev

- MyJourney @ http://salaboy.com

- Co-Founder @ http://www.jugargentina.org
- Co-Founder @ http://www.jbug.com.ar

- Salatino "Salaboy" Mauricio -