What about using different workspaces for each subcriber?
2011/10/20 Ardaman Grewal <[email protected]> > I am trying to design and implement a version-able document system that is > meant for multiple subscribers of the system. Data for each subscriber has > to be isolated from each other. A Web app will provide REST API for the > client applications to access data. Web app will also handle some of the > security and subscription aspects of the subscribing users. I have been > considering Jackrabbit for data management and versioning backed by a > relational database. For the web app, thinking of hosting it in Tomcat. > Hopefully, the following figure comes through properly formatted. In case > it > doesn't, it shows a web app which layers a REST api on top of multiple > (separate) JR repositories. > > Is this a correct approach? Is Jackrabbit intended to be used like this or > am I in the weeds? Any other suggestions. > > Thank you very much. > > > > +-----------+ > | | > +------+ | | > +--------------+ > +------>|Repo A|<---------->| Web |<--------> | Subscriber A | > | +------+ | App | +--------------+ > | | Exposes | > | | REST | +--------------+ > | +------+ | Svcs |<--------> | Subscriber B | > +------>|Repo B|<---------->| | +--------------+ > | +------+ | | > | | | > | +-----------+ > \|/ > +------------+ > | one or more| > | RDMS Store | > +------------+ >
