Java Conent Repository - Jackrabbit

Resources

Wiki: http://en.wikipedia.org/wiki/Content_repository_API_for_Java
JSR 170: http://jcp.org/en/jsr/detail?id=170
JSR 170 API: http://www.day.com/maven/jsr170/javadocs/jcr-1.0/index.html
JSR 283 (JCR 2.0): http://jcp.org/en/jsr/detail?id=283 (in progress)
Jackrabbit: http://jackrabbit.apache.org/
List of Jackrabbit components: http://jackrabbit.apache.org/jackrabbit-components.html

Introduction

Jackrabbit implements JSR 170 and JSR 283.

• Wrap JCR to make it a WebDAV server so that WebDAC client can access it.
  Actually it is a fully featured WebDAV server backed by the JCR repository.
  Address for default repository: http://your_ip:your_port/repository/default/
  It seems that this method only exposes the file and directories in JCR. If you want more fine-grained access, use JCR remoting instead.
  Also see: http://jackrabbit.apache.org/standalone-server.html#StandaloneServer-WebDAVaccess
  http://jackrabbit.apache.org/jackrabbit-web-application.html
• JCR remoting
  Provides more fine-grained content access.
  Address for all workspaces of JCR repository: http://your_ip:your_port/server
  Also see: http://jackrabbit.apache.org/jackrabbit-web-application.html
• RMI access
  http://jackrabbit.apache.org/standalone-server.html#StandaloneServer-RMIaccess
• local access
  Through JNDI or servlet context.

Installation problem

When I tried to install Jackrabbit on gridfarm machine which uses NFS V3, I got problem described in this bug report (http://issues.apache.org/jira/browse/JCR-1605). Basically it says Jackrabbit needs some features that are not implemented in NFS prior to V4.