Release Notes for ModeShape 3.3.0.Final

This document outlines the changes that were made in ModeShape 3.3.0.Final. We hope you enjoy it!

What's new

3.3.0.Final provides a fast, elastic, distributed hierarchical database that clients work with via the standard JCR 2.0 (JSR-283) API. ModeShape 3 is a major upgrade over 2.x and offers significant improvements in performance and scalability, while retaining all of ModeShape 2's JCR-related features. ModeShape 3 has complete integration with JBoss EAP 6.1, allowing deployed components to simply lookup and use repositories managed by ModeShape's service.

This release addesses 47 issues, most of which are bug fixes in lots of areas. Overall, clustering and indexing has been improved, and a new chained binary store is available to allow client applications to dictate in which of several stores a particular binary value should be stored.

This release also upgrades to EAP 6.1.0.GA. As with 3.2, the artifact name for BOM for use in applications has been renamed from 'modeshape-bom-jbossas' (used in 3.0 and 3.1) to 'modeshape-bom-jbosseap' (in 3.2 and 3.3). This is to remain consistent and to help reinforce that ModeShape 3.2 works on EAP 6.1 now and not on JBoss AS7.1.1.


ModeShape 3.3.0.Final has these features:

All of the JCR 2.0 features previously supported in 2.x are currently supported:

Accessing the Repository


Reading Repository Content

Writing Repository Content

Query / Search

Importing/Exporting Repository Content

Node Types

Repository Metadata under System Node

Other JCR Optional Features

Content Storage Options

Binary Storage Options

ModeShape also has features that go beyond the JCR API:

ModeShape Federation Connectors

ModeShape Sequencers

ModeShape Deployment/Access Models

Other ModeShape features

Bug Fixes, Features, and other Issues

The following are the bugs, features and other issues that have been fixed in the 3.3.0.Final release:



Feature Request