Just to come back on this... the way in which Isis picks up its metadata is
pluggable (the FacetFactory internal API).
Most of the metadata comes from the domain objects themselves, of course,
with those domain objects providing the implementation of state management,
at least. But we also bring
Thank you for your response, there are 2 problems which comes to my mind
when I think of Apache Isis as a platform. This question may not be
applicable to this group as such still for people interested can have a
look,
1) How do I manage schema per tenant using DDD? Since the metadata is
derived
If a customer wants to have it's data in a separate db I would always
deploy a dedicated webapp instance alongside. It's going to be a messy
architecture if multiple instances of the same webapp (I reckon you are
aiming for scalability too) must access multiple databases or database
instances.
Use Case:
Consider I am creating a platform where Multiple Organization with Users
belong to each organization should not see each other's data.
For example, Customer1 having 10 Users and Customer2 having 2 user sign in
to our Apache Isis generated app, now customer1 prefers to isolate the data
Hi Sunand,
Because we needed more sophistication we've gone for option 3 and not
implemented 1 and 2 but Datanucleus should be able to support those
scenarios [1]. What use case are your trying to solve?
Cheers,
Jeroen
[1]
Hi,
We have Isis-Security module as an addon which provides multi-tenancy
feature. Presently multi-tenancy as I understand is with respect to
associating an user to a tenant and assigning roles and permissions. "*Each
user can be associated with a particular tenancy, and Isis can then be
