Thanks David. Perhaps some others can throw some light on this. One of
the first articles on JCR I read was this rather good one by Sunil Patil
at
http://www.onjava.com/pub/a/onjava/2006/10/04/what-is-java-content-repository.html
This is a classic n-tier application using Struts, daos, dtos and JCR as
persistence.
When I saw Magnolia, I thought: good - probably a value add supplying
some front-endedness to JCR development, perhaps with tools to take most
of the labour out of the best-practice architecture in the
aforementioned article.
You might imagine my surprise when I saw that in a way, it seems *all*
front-end, using a content repository to model the presentation layer.
Am I wrong?
Charles
David Smith wrote:
Granted I haven't looked at it at all -- just seen mentions of it on
the user list here but I think Magnolia has a data module for handling
abstract data constructs.
--David
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
