eXo Java Content Repository (JCR - JSR 170)

eXo Java Content Repository (JCR - JSR 170)

The main purpose of the standardized Java Content Repository is to provide a standardized, reliable intermediary layer between a custom application and a data storage.

1 Concepts

• Why use JCR
• Advantages
• JCR (JSR-170) API main concepts
• Compatibility Levels
• Using JCR
• JCR Extensions
• JCR Applications
• Node Type registration
• Registry Service
• Namespace altering
• Node types and Namespaces

2 Configuration

• eXo JCR configuration
• Multilanguage support
• Search Configuration
• Configuration persister
• JDBC Data Container config
• External Value Storages
• Workspace Simple DB storage
• Workspace Persistence Storage
• Groovy REST Services
• Auditing

3 Indexating and Searching

• Search Configuration
• Search index backup
• Searching Repository Content
• JCR Query Usecases

4 Protocols

• Web Dav
• FTP
• RMI
• CIFS(SMB)
• CIFS Quick Start

5 Third parties integration

• Kofax

6 Clustering and Replication

• How-to Persistent JCR Cluster Remote Workspace Initializer
• Configure a persistent JCR cluster
• Clustering
• Asynchronous Replication
• Replication bandwidth allocation

7 Backup

• Backup service
• Backup client
• Search index backup

8 Migration and Release Notes

• Migration to 1.7
• JCR Release notes

9 Development

• e Xo JCR Implementation
• Benchmark
• Frameworks on top of JCR
• Node Type visualization
• Locking
• Session leak detector
• Web Dav Client Libraries
• Export Import Implementation
• How to JCR import export
• How to use Checkstyle and Emma
• Unit Test Creation

10 Other Articles

• JCR Resources
• Access Control
• Access Control extension
• Deployment JCR standalone (ver 1_5)
• Open Office Add-On
• Microsoft Office plugin
• Link Producer
• Repository container life cycle
• Binary values processing
• Organization Service