Release Notes for ModeShape 4.2.0.Final This document outlines the changes that were made in ModeShape 4.2.0.Final. We hope you enjoy it! What's new ------------------------------------------------------------------- 4.2.0.Final provides a fast, elastic, distributed hierarchical database that clients work with via the standard JCR 2.0 (JSR-283) API. ModeShape 4 is a major upgrade over 3.x and offers significant improvements in clustering, performance, query, and events. All JCR 2.0 features are supported, and ModeShape 4 has complete integration with Wildfly 8, allowing deployed applications to simply lookup and use repositories managed by ModeShape's service. ModeShape 4.2.0.Final is licensed under the Apache Software License, 2.0. This release addresses 36 bugs and 9 enhancements, including several related to our Teiid and DDL sequencers. Our Wildfly kit now integrates directly with Wildfly's security services meaning that if a security domain is configured to use caching, ModeShape will take full advantage of this whenever session authentication operations are performed. Also, the local index provider now exposes several MapDB configuration options allowing for advanced performance tuning when this provider is used. Features ------------------------------------------------------------------- ModeShape 4.2.0.Final has these features: - ModeShape uses Infinispan for all caching and storage, giving a powerful and flexible foundation for creating JCR repositories that are fast, scalable, and highly available. Infinispan offers a great deal of storage options (via cache loaders), but using Infinispan as a distributed, mulit-site, in-memory data grid provides incredible scalability and performance. - Strongly consistent. ModeShape is atomic, consistent, isolated and durable (ACID), so writing applications is very natural. Applications can even use JTA transactions. - Fast. ModeShape 4 is just plain seriously fast, and performance is all-around faster than earlier version. - Larger content. ModeShape 4 can store and access the content so that a node can have hundreds of thousands (or more!) of child nodes (even with same-name-siblings) yet still be incredibly fast. Additionally, repositories can scale to many millions of nodes and be deployed across many processes. - Simplified configuration. There is no more global configuration of the engine; instead, each repository is configured with a separate JSON file, which must conform to a ModeShape-specific JSON Schema and can be validated by ModeShape prior to use. Repository configurations can even be changed while the repository is running (some restrictions apply), making it possible to add/change/remove sequencers, authorization providers, and many other configuration options while the repository is in use. - Elastic. Add processes to scale out, without having to have a single coordinator. - Deploy, start, stop and undeploy repositories while the engine is running and while and other repositories are still in use. - Sessions immediately see all changes persisted/committed by other sessions, although transient changes made by the session always take precedence. - Monitoring API with over a dozen metrics. - Sequencing SPI that uses the JCR API to get at the content being processed and create/update the derived content. Sequencers can also dynamically register namespaces and node types. Now it's easy to create custom sequencers. - Connector SPI that defines how external systems are accessed and optionally updated to project the external information into the repository as regular nodes. - Simple API for implementing custom MIME type detectors. ModeShape still has a built-in Tika-based detector that determines MIME types using the filename extensions and binary content. - Simple API for implementing custom text extractors, which extracts from binary values searchable text used in full-text searches and queries. - Ability to store binary values of any sizes, with a separate facility for storing these on the file system, in Infinispan caches, in relational DBMSes (via JDBC), and in MongoDB. Custom stores are also possible. - Public API interfaces and methods that were deprecated in 2.7.0.Final (or later) have been removed. There weren't many of these; most of the ModeShape API remains the same as 2.x. - Integration with JBoss Wildfly 8. ModeShape runs as an integrated subsystem within Wildfly, and the Wildfly tooling can be used to define and manage repositories independently of each other and while the server is running. - Local and remote JDBC drivers for issuing JCR-SQL2 queries and getting database metadata via the JDBC API - Use the RESTful API to talk to ModeShape repositories from non-Java and non-local applications - Use the CMIS API to talk to ModeShape repositories - Use WebDAV to mount ModeShape repositories as file servers - Visual repository explorer web application All of the JCR 2.0 features previously supported in 2.x are currently supported: Accessing the Repository - RepositoryFactory access - JNDI registration of Repository - JAAS Authentication - Servlet Authentication - Custom Authentication Namespaces - Session Remapping - Permanent Addition/Deletion Reading Repository Content - Traversal Access - Direct Access - Same-Name Siblings - Multi-Value Properties - All Property Types Supported - Property Type Conversion Writing Repository Content - Create/Update/Delete Nodes - Create/Update/Delete Properties (Through Parent Nodes) - Moving, Copying, Cloning - Adding/Removing Mixins - Referential integrity enforcement Query / Search - XPath - JCR-SQL - JCR-SQL2 - JCR-QOM - Full-Text Search Importing/Exporting Repository Content - System View Import/Export - Document View Import/Export Node Types - Inheritance Among Node Types - Discovering available Node Types - Discovering the Node Types of a Node - Discovering the Definition of a Node Type - Property Constraints - Automatic Item Creation - Predefined standard Node Types - Custom Node Type Registration (CND-Based and and JCR 2.0 API Template-Based) Repository Metadata under System Node - Permanent Namespace Mappings - Node Types (Built-In and User-Registered) - Active Locks Other JCR Optional Features - Observation - Locking - Versioning - Shareable nodes - Access controls - Even journal Content Storage Options - In-memory (local, replicated, and distributed) - Relational databases (via JDBC), including in-memory, file-based, or remote - LevelDB - File system - Cassandra - Cloud storage (e.g., Amazon's S3, Rackspace's Cloudfiles, or any other provider supported by JClouds) - Remote Infinispan Binary Storage Options - File system - JDBC database - Infinispan - MongoDB - Chained binary stores ModeShape also has features that go beyond the JCR API: ModeShape Federation Connectors - File system connector (read and write) - Git repository connector (read-only) - CMIS reposiotry connector (read and write, tech preview) - JDBC metadata connector (read-only) ModeShape Sequencers - Compact Node Definition (CND) Sequencer - DDL Sequencer - Image Sequencer - Java Source Sequencer - Java Class Sequencer - MP3 Sequencer - MS Office Sequencer - Text Sequencers (Delimited and Fixed Width) - XML Sequencer - XML Schema Document (XSD) Sequencer - Web Service Definition Lanaguage (WSDL) 1.1 Sequencer - Zip File Sequencer (also WARs, JARs, and EARs) - Teiid Relational Model Sequencer - Teiid VDB Sequencer ModeShape Deployment/Access Models - JNDI-Based Deployment - Deploy as a subsystem in JBoss Wildfly, with access to repositories via @Resource injection - Deploy to other containers using ModeShape's JCA adapter - Access through two RESTful Services (the 2.x-compatible API and a new improved API) - Access through WebDAV Service - Access through CMIS Service - Access through visual repository explorer web application - Local and remote JDBC drivers for accessing ModeShape content through JDBC API and JCR-SQL2 queries - Embedded (in Server or JEE Archive) Deployment - JTA support, allowing Sessions to participate in XA and container-managed transactions - OSGi-Compatible Archives Other ModeShape features - Repository-wide backup and restoration - Explicitly-defined indexes - Automatic MIME type detection of binary content - Asynchronous sequencing operations, within completion notified via events Bug Fixes, Features, and other Issues ------------------------------------------------------------------- The following are the bugs, features and other issues that have been fixed in the 4.2.0.Final release: Bug - [MODE-2391](https://issues.jboss.org/browse/MODE-2391) - Optimization feature cannot triggered by enabling the document-optimization-child-count-target in Wildfly configuration - [MODE-2390](https://issues.jboss.org/browse/MODE-2390) - Possible NPE when reindexing node-type indexes - [MODE-2393](https://issues.jboss.org/browse/MODE-2393) - Reindexing nodes should remove existing values from indexes - [MODE-2392](https://issues.jboss.org/browse/MODE-2392) - LocalIndexProvider seems to do extensive work at every startup, even if shutdown properly - [MODE-2395](https://issues.jboss.org/browse/MODE-2395) - JCR Session not seeing changes made on a different thread when using ModeShape 4.1.0.Final - [MODE-2397](https://issues.jboss.org/browse/MODE-2397) - Repository Explorer does not work with a JSON configuration/connector - [MODE-2396](https://issues.jboss.org/browse/MODE-2396) - Incorrect settings of flags in DDL Sequencer for view creation - [MODE-2399](https://issues.jboss.org/browse/MODE-2399) - ModeShape EAP/WF subsystem incorrectly handles default initial content - [MODE-2430](https://issues.jboss.org/browse/MODE-2430) - JCR string properties are truncated when storing them into Infinispan - [MODE-2431](https://issues.jboss.org/browse/MODE-2431) - Heap is slowly used up when versionable mixin is enabled - [MODE-2416](https://issues.jboss.org/browse/MODE-2416) - Fix incorrect smartGWT dependency - [MODE-2417](https://issues.jboss.org/browse/MODE-2417) - Event listener throwing RepositoryException - [MODE-2414](https://issues.jboss.org/browse/MODE-2414) - ACLs not checked during hasNode - [MODE-2412](https://issues.jboss.org/browse/MODE-2412) - DB binary stores limit extracted text to 1000 characters - [MODE-2413](https://issues.jboss.org/browse/MODE-2413) - Exporting system view of node federated using FileSystemConnector throws IOException - [MODE-2418](https://issues.jboss.org/browse/MODE-2418) - NodeNotFoundInParentException when concurrently accessing a node - [MODE-2382](https://issues.jboss.org/browse/MODE-2382) - Indexmanager seems to get into inconsistent state when trying to define an index on a nonexistent nodeType - [MODE-2383](https://issues.jboss.org/browse/MODE-2383) - Reduce number of artifacts published into Maven repository - [MODE-2429](https://issues.jboss.org/browse/MODE-2429) - broken link in documentation to XSD Sequencers - [MODE-2428](https://issues.jboss.org/browse/MODE-2428) - ACLs not checked when updating properties - [MODE-2386](https://issues.jboss.org/browse/MODE-2386) - Node Iterator generated from Node.getNodes(relPath) returns unexpected child of different type - [MODE-2384](https://issues.jboss.org/browse/MODE-2384) - CMIS web application does not work with clustering configuration - [MODE-2385](https://issues.jboss.org/browse/MODE-2385) - Reordering multi-valued reference/weak reference property doesn't work - [MODE-2251](https://issues.jboss.org/browse/MODE-2251) - Better handle referential integrity problems when removing nodes in the web-explorer - [MODE-2367](https://issues.jboss.org/browse/MODE-2367) - Error to access contents of older versions via CMIS - [MODE-2426](https://issues.jboss.org/browse/MODE-2426) - GIT connector not refreshing federated nodes - [MODE-2425](https://issues.jboss.org/browse/MODE-2425) - Modeshape 4.0+ no longer supports PATH set queries - [MODE-2424](https://issues.jboss.org/browse/MODE-2424) - Cannot add mixin to a locked node - [MODE-2405](https://issues.jboss.org/browse/MODE-2405) - Exploded webapps in ModeShape EAP/WF kit not deploying - [MODE-2404](https://issues.jboss.org/browse/MODE-2404) - Indexes defined in "/jcr:system/mode:indexes" don't reflect ModeShape configuration - [MODE-2344](https://issues.jboss.org/browse/MODE-2344) - Credentials become corrupted after logging out from the Repository Explorer - [MODE-2401](https://issues.jboss.org/browse/MODE-2401) - Nodetype is queryable as supertype when noquery is set - [MODE-2403](https://issues.jboss.org/browse/MODE-2403) - Unexpected behavior from like operand - [MODE-2402](https://issues.jboss.org/browse/MODE-2402) - WF kit should not persist binaries on the FS is no such store is configured - [MODE-2409](https://issues.jboss.org/browse/MODE-2409) - invoking of the checkin() method in clustered mode throws an org.modeshape.jcr.cache.NodeNotFoundInParentException - [MODE-2408](https://issues.jboss.org/browse/MODE-2408) - JCRMODIFYACCESS_CONTROL privilege not working as intended Enhancement - [MODE-2411](https://issues.jboss.org/browse/MODE-2411) - ModeShape not using EAP's security layer - [MODE-2388](https://issues.jboss.org/browse/MODE-2388) - Enable DDL Sequencer to parse data type array dimensions - [MODE-2360](https://issues.jboss.org/browse/MODE-2360) - Add support for CMIS document hashing - [MODE-2400](https://issues.jboss.org/browse/MODE-2400) - DDL Sequencer support for Teiid creating global temporary tables - [MODE-2350](https://issues.jboss.org/browse/MODE-2350) - Update the OracleDdlParser to support multiple ADD/MODIFY statements during ALTER table Feature Request - [MODE-2394](https://issues.jboss.org/browse/MODE-2394) - Update Vdb Sequencer in line with latest changes to Teiid vdb schema - [MODE-2387](https://issues.jboss.org/browse/MODE-2387) - MapDb configuration settings for LocalIndexProvider Task - [MODE-2410](https://issues.jboss.org/browse/MODE-2410) - Clarify ambigous method in the connector's DocumentWriter API - [MODE-2406](https://issues.jboss.org/browse/MODE-2406) - Upgrade to WildFly 8.2