Release Notes for ModeShape 4.4.0.Final
This document outlines the changes that were made in ModeShape 4.4.0.Final.
We hope you enjoy it!
This release addresses 18 bugs and 12 enhancements, most notably:
Wildfly 9 support. Starting with this version, the ModeShape AS kit can be run both on Wildfly 8 and Wildly 9.
Support for large collections of flat nodes. This is a long outstanding enhancement which allows large number of children (>500k)
to be stored under the same parent node. See MODE-2109 and our documentation
for more information.
Enhanced look & feel for the Repository Explorer web application, together with a number of bug fixes.
New example of how to use and embed a custom authorization and authentication provider in your own application.
The example can be found here
ModeShape 4.4.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, multi-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
- 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
- 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
- Full-Text Search
Importing/Exporting Repository Content
- System View Import/Export
- Document View Import/Export
- 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
- 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
- File system
- 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
- 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)
- 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.4.0.Final release:
- MODE-2498 - Indexing properties from ancestor node types multiple times results in a query failing to find a result.
- MODE-2497 - German character sharp S not handled correctly by query parser
- MODE-2494 - SQL2: AssertionError on multiple joins with isChildNode
- MODE-2495 - Transactional changes not propagated correctly when using user transactions shared by multiple threads
- MODE-2492 - DDL Parser fails when table contains VARCHAR column with DEFAULT value
- MODE-2493 - ModeShape managed transactions can cause NPEs if they're rolled back after a failed commit
- MODE-2490 - NullPointerException when executing queries with order by two nullable fields
- MODE-2491 - LOWER operand on a multi-value propetry does not match in WHERE clause
- MODE-2470 - Errors identified in ddl sequencer
- MODE-2471 - Bug in infinispan cache configuration for leveldb
- MODE-2473 - QueryResultIterator.skip throws NoSuchElementException
- MODE-2474 - WildFly kit binary store not read when store-name is defined
- MODE-2476 - Teiid Sequencer fails upon multiple sequencing requests
- MODE-2477 - Static VDBs doesn't get sequenced
- MODE-2485 - Infinispan lock timeout exceptions should not break repository GC jobs
- MODE-2484 - Possible Infinispan deadlock when processing binary values
- MODE-2480 - Broken dependency in modeshape-tomcat-jsf-example
- MODE-2401 - Nodetype is queryable as supertype when noquery is set
- MODE-2467 - Modeshape-explorer: add mixin when clicking refresh
- MODE-2445 - Failed to import SalesForce Metadata
- MODE-2496 - Custom authentication providers in the AS kit should always be invoked first, before the built-in container providers
- MODE-1460 - SchematicEntryLiteral should use suppress return values flags when calling put internally
- MODE-2489 - Make mime-type detection configurable allowing either no detection, name or content-based detection
- MODE-2488 - Add support for Wildfly 9
- MODE-2481 - Improve the memory footprint of the structures which hold a parent's child references
- MODE-2482 - Support multi-valued properties in document view export
- MODE-2459 - Enhance web-explorer ergonomic
- MODE-2345 - Improve statistics for events
- MODE-2469 - The maximum number of threads performing sequencing and text extraction operations should be configurable
- MODE-2109 - Support nodes with a very large number of unordered and uniquely-named children
- MODE-2064 - Support JSR-333 (aka, "JCR 2.1") API
- MODE-1226 - Allow nodes (and subgraphs) to be detached from the session and reattached to another session
- MODE-1447 - Store binary files in Hadoop
- MODE-1718 - Connector to ModeShape
- MODE-2316 - Add flag/setting/switch to reindex nodes synchronously when adding new indexes at runtime
- MODE-2407 - Improve initial indexing process by limiting tree traversal
- MODE-2327 - Support leading & trailing spaces in node names and paths
- MODE-1459 - Connect to and use remote ModeShape server
- MODE-1814 - Create separate GitHub repository for qualification (e.g., "smoke") tests
- MODE-2479 - Upgrade to ISPN 7.2.3 or newer to avoid LIRS eviction bug
- MODE-2472 - Update Apache Tika version to 1.8
- MODE-1682 - Create durable persistent repositories for testing multiple versions of ModeShape
- MODE-2483 - Create an example showing a custom authentication provider implementation