What does ModeShape offer that JackRabbit doesn't?

Viewed 13040

I just familiarized myself with Apache JackRabbit. I've done a little multi-user repository for document management.

If anybody used both of them, could you please answer these questions ?

  1. Is ModeShape somehow linked to JBoss ? I don't have much experience with JBoss AS or any other JBoss tools. I see a support for tomcat, but a lot of JBossy stuff

  2. Documentation says that future releases should have UI integration, is it far future ? What kind of UI integration would it be ? Is there something that uses ModeShape as it is in case of Hippo CMS with JackRabbit ? It's a shame that Gatein doesn't use it.

  3. How does JackRabbit compare to ModeShape in regard to fulltext search, indexing and the overall processing of text content ?

  4. How about CMIS support ? I see an unresolved issue MODE-650. Jackrabbit is supported by OpenCMIS (Apache chmistry), even for secondary types in near future.

  5. What about support/utils libraries, for developer convenience when working with Nodes

I'm interested in any other comparison comments, thank you

3 Answers

Documentation of modeshape seems better. The folks at Jackrabbit provide limited documentation, when compared to other apache projects. I suppose that if you need fancy (enterprise) features, they want you to pay for it. Also note that you are almost forced to used a sql database as backend. Because almost all other backends are 'not intended for production use'. Compare to modeshape who just comes out and says it:

This is in fact the main purpose of ModeShape: provide a JCR implementation that provides access to content stored in many different kinds of systems, including the federation of multiple systems. A ModeShape repository isn't yet another silo of information, but rather it's a JCR view of the information you already have in your environment: files systems, databases, other repositories, services, applications, etc. ModeShape can help you understand the systems and information you already have, through a standard Java API

I'd rather prefer this clarity than letting people search their doc and google for information that doesn't exist.

Related