You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by Tobias Mattsson <to...@magnolia-cms.com> on 2011/09/26 17:09:50 UTC
Advice on integrating loosely typed non folder based WCM
Hi all,
I'm looking into using Chemistry to expose the content of Magnolia CMS over CMIS. This has proved to be non straight forward as the domain models of Magnolia and CMIS are quite different.
In Magnolia the main content element is a web page, its' a JCR node with a type that allows any number of properties without constraints. The page contains areas and within those are components, these are represented as nodes and they also allows any number of properties and additional sub nodes.
The domain models differ in two aspects,
1) Loose typing
Is it possible to expose support for arbitrary properties? Has this been done before? I read somewhere that Nuxeo has done something similar.
2) Documents with children
A web page behaves as both a document and a folder, i.e. it has content, and it has sub-pages. As I understand it, CMIS limits content streams and versioning to documents and the ability to have children to folders.
Any advice on how to approach this?
Re: Advice on integrating loosely typed non folder based WCM
Posted by Florian Müller <fl...@alfresco.com>.
Hi Tobias,
Re 1) No, CMIS does not allow arbitrary properties.
Technically, you can return any list of properties you like, but the response wouldn't be spec compliant.
It is possible to use one of CMIS' extension points to send more data (properties) to the client, but the client then has to understand this additional data.
Re 2) Documents cannot have children in CMIS.
But documents can have relationships to other documents. The parent-child semantics are not defined in CMIS, though. The client would have to know or guess it.
Florian
On 26/09/2011 16:09, Tobias Mattsson wrote:
> Hi all,
>
> I'm looking into using Chemistry to expose the content of Magnolia CMS over CMIS. This has proved to be non straight forward as the domain models of Magnolia and CMIS are quite different.
>
> In Magnolia the main content element is a web page, its' a JCR node with a type that allows any number of properties without constraints. The page contains areas and within those are components, these are represented as nodes and they also allows any number of properties and additional sub nodes.
>
> The domain models differ in two aspects,
>
> 1) Loose typing
> Is it possible to expose support for arbitrary properties? Has this been done before? I read somewhere that Nuxeo has done something similar.
>
> 2) Documents with children
> A web page behaves as both a document and a folder, i.e. it has content, and it has sub-pages. As I understand it, CMIS limits content streams and versioning to documents and the ability to have children to folders.
>
> Any advice on how to approach this?
>
>
Re: Advice on integrating loosely typed non folder based WCM
Posted by Stefane Fermigier <sf...@nuxeo.com>.
On Sep 27, 2011, at 2:34 PM, Florent Guillaume wrote:
> On Mon, Sep 26, 2011 at 5:09 PM, Tobias Mattsson
> <to...@magnolia-cms.com> wrote:
>
>> 2) Documents with children
>> A web page behaves as both a document and a folder, i.e. it has content, and it has sub-pages. As I understand it, CMIS limits content streams and versioning to documents and the ability to have children to folders.
>
> Another option besides what Florian said, if web pages are read-only
> from the client's perspective, is to expose the page content as a
> folder's rendition (renditions for folders were designed to display
> icons but can be used in a generic manner).
Another option would be to expose a node's content as a magic document named like "index.html" (like most of the web was doing int the 90's) or "index_html" (as Zope did in the early 2000's).
S.
--
Stefane Fermigier, Founder and Chairman, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier
Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314
New Nuxeo release: http://nuxeo.com/dm54
"There's no such thing as can't. You always have a choice."
Re: Advice on integrating loosely typed non folder based WCM
Posted by Florent Guillaume <fg...@nuxeo.com>.
On Mon, Sep 26, 2011 at 5:09 PM, Tobias Mattsson
<to...@magnolia-cms.com> wrote:
> Hi all,
>
> I'm looking into using Chemistry to expose the content of Magnolia CMS over CMIS. This has proved to be non straight forward as the domain models of Magnolia and CMIS are quite different.
>
> In Magnolia the main content element is a web page, its' a JCR node with a type that allows any number of properties without constraints. The page contains areas and within those are components, these are represented as nodes and they also allows any number of properties and additional sub nodes.
>
> The domain models differ in two aspects,
>
> 1) Loose typing
> Is it possible to expose support for arbitrary properties? Has this been done before? I read somewhere that Nuxeo has done something similar.
FYI Nuxeo has no arbitrary properties. They all correspond to schema
definitions and are exposed through the normal CMIS object type
mechanism.
> 2) Documents with children
> A web page behaves as both a document and a folder, i.e. it has content, and it has sub-pages. As I understand it, CMIS limits content streams and versioning to documents and the ability to have children to folders.
Another option besides what Florian said, if web pages are read-only
from the client's perspective, is to expose the page content as a
folder's rendition (renditions for folders were designed to display
icons but can be used in a generic manner).
Florent
--
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
Re: Advice on integrating loosely typed non folder based WCM
Posted by Tobias Mattsson <to...@magnolia-cms.com>.
Thanks everyone for your advice it was really helpful,
We've considered our options and decided that we will limit our CMIS integration to the DMS part of Magnolia CMS. At least for now.
// Tobias
On Sep 26, 2011, at 5:09 PM, Tobias Mattsson wrote:
> Hi all,
>
> I'm looking into using Chemistry to expose the content of Magnolia CMS over CMIS. This has proved to be non straight forward as the domain models of Magnolia and CMIS are quite different.
>
> In Magnolia the main content element is a web page, its' a JCR node with a type that allows any number of properties without constraints. The page contains areas and within those are components, these are represented as nodes and they also allows any number of properties and additional sub nodes.
>
> The domain models differ in two aspects,
>
> 1) Loose typing
> Is it possible to expose support for arbitrary properties? Has this been done before? I read somewhere that Nuxeo has done something similar.
>
> 2) Documents with children
> A web page behaves as both a document and a folder, i.e. it has content, and it has sub-pages. As I understand it, CMIS limits content streams and versioning to documents and the ability to have children to folders.
>
> Any advice on how to approach this?
>
>