[
http://jira.magnolia-cms.com/browse/DOCU-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antti Hietala updated DOCU-131:
-------------------------------
Description:
With Magnolia CMS rel 4.4 we have experimental support for ModeShape. ModeShape
is an alternative JCR implementation to Jackrabbit. Document both repositories
in {{/administration/repositories}} (new node).
* Declare status of ModeShape support: experimental, slow, improvements
expected in ModeShape 2.5.
* Explain the benefits and limitations of each repository
* How to download, install and run Magnolia with ModeShape. For Jackrabbit the
same is already documented in
[installation|http://documentation.magnolia-cms.com/administration/installation.html].
* Migrating content from Jackrabbit to ModeShape and vice versa. Do [standard
migration
mechanisms|https://docs.google.com/Doc?docid=0AbdnFchPQx8cZGdkeHQzM3FfMjk4bTZnYmdyZ2c&hl=en]
work?
* Be consistent on terminology. Now that we have two viable JCR _repositories_,
stop calling Magnolia workspaces "repositories". Very confusing.
Resources
* Jozef Chocholáček: [How To Make Magnolia CMS
Shaped|http://community.jboss.org/wiki/HowToMakeMagnoliaCMSShapedTomcatversion].
Installation and configuration. Usable but under construction!
* Jan: [M&M Magnolia and
ModeShape|http://weblogs.java.net/blog/rah003/archive/2011/01/03/mm-magnolia-and-modeshape]
* Jan: [Magnolia and
ModeShape|http://weblogs.java.net/blog/rah003/archive/2011/01/29/magnolia-and-modeshape]
* Boris: [ModeShape - a unified content bus for
Magnolia?|http://www.betterfasterbigger.com/2010/01/modeshape-unified-content-bus-for.html]
* Wiki: [Concept - ModeShape repository
backend|http://wiki.magnolia-cms.com/display/DEV/Concept+-+ModeShape+repository+backend]
was:
With Magnolia CMS rel 4.4 we have experimental support for ModeShape. ModeShape
is an alternative JCR implementation to Jackrabbit. Document both repositories
in {{/administration/repositories}} (new node).
* Declare status of ModeShape support: experimental, slow, improvements
expected in ModeShape 2.5.
* Explain the benefits and limitations of each repository
* How to download, install and run Magnolia with ModeShape. For Jackrabbit the
same is already documented in
[installation|http://documentation.magnolia-cms.com/administration/installation.html].
* Migrating content from Jackrabbit to ModeShape and vice versa. Do [standard
migration
mechanisms|https://docs.google.com/Doc?docid=0AbdnFchPQx8cZGdkeHQzM3FfMjk4bTZnYmdyZ2c&hl=en]
work?
* Be consistent on terminology. Now that we have two viable JCR _repositories_,
stop calling Magnolia workspaces "repositories". Very confusing.
Resources
* Jozef Chocholáček: [How To Make Magnolia CMS
Shaped|http://community.jboss.org/wiki/HowToMakeMagnoliaCMSShapedTomcatversion].
Installation and configuration. Usable but under construction!
* Jan: [M&M Magnolia and
ModeShape|http://weblogs.java.net/blog/rah003/archive/2011/01/03/mm-magnolia-and-modeshape]
* Jan: [Magnolia and
ModeShape|http://weblogs.java.net/blog/rah003/archive/2011/01/29/magnolia-and-modeshape]
* Boris: [ModeShape - a unified content bus for
Magnolia?|http://www.betterfasterbigger.com/2010/01/modeshape-unified-content-bus-for.html]
> ModeShape
> ---------
>
> Key: DOCU-131
> URL: http://jira.magnolia-cms.com/browse/DOCU-131
> Project: Documentation
> Issue Type: Task
> Security Level: Public
> Components: content
> Reporter: Antti Hietala
> Assignee: Antti Hietala
>
> With Magnolia CMS rel 4.4 we have experimental support for ModeShape.
> ModeShape is an alternative JCR implementation to Jackrabbit. Document both
> repositories in {{/administration/repositories}} (new node).
> * Declare status of ModeShape support: experimental, slow, improvements
> expected in ModeShape 2.5.
> * Explain the benefits and limitations of each repository
> * How to download, install and run Magnolia with ModeShape. For Jackrabbit
> the same is already documented in
> [installation|http://documentation.magnolia-cms.com/administration/installation.html].
> * Migrating content from Jackrabbit to ModeShape and vice versa. Do [standard
> migration
> mechanisms|https://docs.google.com/Doc?docid=0AbdnFchPQx8cZGdkeHQzM3FfMjk4bTZnYmdyZ2c&hl=en]
> work?
> * Be consistent on terminology. Now that we have two viable JCR
> _repositories_, stop calling Magnolia workspaces "repositories". Very
> confusing.
> Resources
> * Jozef Chocholáček: [How To Make Magnolia CMS
> Shaped|http://community.jboss.org/wiki/HowToMakeMagnoliaCMSShapedTomcatversion].
> Installation and configuration. Usable but under construction!
> * Jan: [M&M Magnolia and
> ModeShape|http://weblogs.java.net/blog/rah003/archive/2011/01/03/mm-magnolia-and-modeshape]
> * Jan: [Magnolia and
> ModeShape|http://weblogs.java.net/blog/rah003/archive/2011/01/29/magnolia-and-modeshape]
> * Boris: [ModeShape - a unified content bus for
> Magnolia?|http://www.betterfasterbigger.com/2010/01/modeshape-unified-content-bus-for.html]
> * Wiki: [Concept - ModeShape repository
> backend|http://wiki.magnolia-cms.com/display/DEV/Concept+-+ModeShape+repository+backend]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
