Just for the history, we start the dev before the first JCR stable impl and when JCR was not like today. this is one of the reasons why the architecture is like this (based on a series of plugin used to access to heterogenous content servers).
The PersistenceManager uses those plugins to access to the different content server at the same time.The PersistenceManager is a good way to vistualize your content server into the same tree. Each content request are sent to the persistence manager which has the responsability to work with the appropriate content server. If the new Graffito goal is to access to only one content repo from your apps, yes we can simplify the architecture but the persistence manager is working right now (at least 70% stable :-) ) Of course we can improve it but it makes its job. Furthermore, it is more interesting to access to different content servers in the same time (even if there are all based on JCR). So, I'm not sure the architecture could be simplify here. What do you think about that ? Using JCR in all cases will not reduce the architecture complexity but it will reduce the work of course. br, Christophe On 1/11/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Christophe Lombart wrote: > On 1/10/07, Torgeir Veimo <[EMAIL PROTECTED]> wrote: >> On Wed, 2007-01-10 at 16:16 +0100, Christophe Lombart wrote: >>> So Please give us your point of view and we will take a decision after >>> that. >> I find it a bit diffuse what the project is all about. Is it a sandbox >> of ideas or some sort of AppFuse for web publishing? > > > > Well the main goal is the build a ECM plateform like Alfresco and many > others (but with a clean license :-) ) > > Here is the architecture : > http://incubator.apache.org/graffito/architecture.html > Is it make sense for you ? > I guess this has been discussed before, but I'm curious anyway :) Wouldn't it simplify the architecture and reduce the work if Graffito would be based on JCR only instead of supporting various store implementations? I thought JCR can already handle this. Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
