You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Charles Johnson <cj...@proteanit.net> on 2008/04/02 11:41:42 UTC

Magnolia and Jackrabbit

I wonder if some of you could clear up a little confusion I have? All  
documentation concerning JCR and Jackrabbit seems to approach the 
architecture from the point of view of domain object modelling. Great

Any documentation on Magnolia I've seen so far seems to only discuss 
pages and the presentation layer. Granted, I can imagine that Magnolia 
is designed as a higher level model of JCR, with emphasis on classic 
CMS, but even so, I find (so far) virtually no mention of application 
level object modelling. What gives?

Charles

Re: Magnolia and Jackrabbit

Posted by Alessandro Bologna <al...@gmail.com>.
Charles,

Magnolia is not an alternative implementation of the JCR, as far as I
know. It's a CMS built on top of Jackrabbit, and that may explains why
the documentation on Magnolia focuses on the application aspects (such
as pages and presentation layer), and not the JCR.

Alessandro


On Wed, Apr 2, 2008 at 5:41 AM, Charles Johnson <cj...@proteanit.net> wrote:
> I wonder if some of you could clear up a little confusion I have? All
> documentation concerning JCR and Jackrabbit seems to approach the
> architecture from the point of view of domain object modelling. Great
>
>  Any documentation on Magnolia I've seen so far seems to only discuss pages
> and the presentation layer. Granted, I can imagine that Magnolia is designed
> as a higher level model of JCR, with emphasis on classic CMS, but even so, I
> find (so far) virtually no mention of application level object modelling.
> What gives?
>
>  Charles
>