Hi Cyril,
Thanks for the feedback.
As I understood from Activiti forums and jiras, Activiti developers propose
to use one of the following approaches:
(1) Use multiple Activiti engine instances (one engine per tenant)
(2) Filter Activiti operations using tenant IDs (this is the second
approach p
Hi,
+1 for second approach, as it is compliant with the mediation philosophy
and it shows WSO2 can quickstart activiti integration using soa principles
and it let us use activiti as a pluggable engine. This will allow bps to
upgrade to any upcoming activiti version if needed.
as for the futur, we
As chathura has mentioned, we should not modify the activiti code or
database schemas. That way, we have the ability to switch to latest version
of activiti engine at each release which enables us to obtain all the bug
fixes available from the parent project.
Regards
Nandika
On Wed, Feb 12, 2014
Hi all,
I am integrating the Activiti engine with BPS to provide BPMN support. One
of the major issues we have to address in this effort is to provide
multi-tenancy support, which is not directly supported by Activiti.
I think we have two approaches for this:
(1) Modify the DB schemas used by Ac
