Tag objects are documents (so that you can add metadata to them etc). Tagging actions are comparable to relations between tags and the document that you tag, and we need specialized queries on them (aggregates, cloud, etc.) which we cannot do right now just with the document database, so JPA is used for them. But we need queries between the tags, taggings, and documents, so they have to use the same database.
In the not-far future I plan to make the tags entirely managed by Nuxeo Core which will get rid of these problems. Florent On Sat, Apr 3, 2010 at 11:14 AM, Sean Radford <[email protected]> wrote: > And what is the reasoning that it needs to? > > Julien CARSIQUE wrote: >> >> Hello, >> >> Yes, it's because tagging service directly uses the repository's >> datasource. >> >> Regards, >> Julien >> >> Le 30/03/10 21:33, Sean Radford a écrit : >> >>> >>> Hi, >>> >>> Is there any reason why the tagging service is by default not >>> configured to use the unified datasource? >>> >>> Regards, >>> >>> Sean >>> >>> >> >> > > > -- > Dr. Sean Radford, MBBS, MSc > http://www.tacola.com/ > t: +44 (0)845 KEY HELP > t: +44 (0)845 539 4357 > m: +44 (0)7802 24 24 86 > > _______________________________________________ > ECM mailing list > [email protected] > http://lists.nuxeo.com/mailman/listinfo/ecm > To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm > -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
