incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Wechner <michael.wech...@wyona.com>
Subject Re: Why the Webdav-/Graffito-/FileSystemServer interfaces?
Date Sat, 26 Aug 2006 20:58:20 GMT
Edgar Poce wrote:

> Hi,
>
>  I'm working in a project that uses j2, we plan to keep using it in
> the near future and we'd like to use the cms features described in
> graffito's web page. I browsed the sources and I have the same doubt
> that started this thread.
>
>  I don't understand what's the purpose of the webdav\filesystem\ojb
> servers. I think one of the purposes of jcr is to provide that layer
> on top of existing repositories. Moreover, most of the services the
> graffito api provides seem overlapped with jcr.
>
>  My understanding is that most CMS features belong to a layer on top
> of jcr. Is there any reason for not using jcr as the only api to
> interact with the repository and build services on top of it? 


well, it might depend on how much one believes in JCR as one fits all 
solution.

Even if JCR is a great thing, it might not fit all purposes and one
might be glad to have an alternative entry point, but I cannot really judge
because I do not Graffito well enough

Just my 2 cents

Michi

>
>  In any case, if there's the intention of building a repository that
> works as a hub of plugged server implementations, why not to build
> that integration layer as a JCR implementation leaving the CMS unaware
> of that?.
>
> thanks in advance,
> edgar
>


-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org
+41 44 272 91 61


Mime
View raw message