An open-source, federated content repository

ModeShape 3.4.0.Final is available

We’re happy to announce that ModeShape 3.4.0.Final is now available. This release contains lots of bug fixes and several new features, including:

  • The new JDBC metadata connector will dynamically project database schema information (e.g., catalogs, tables, columns, indexes, keys, etc.) as nodes in your repository.
  • Store binary files in a Cassandra column-oriented database via the CassandraBinaryStore.
  • Use ACLs to control access to nodes and subtrees

This release also has some useful enhancements, including:

  • WebDAV service now supports PROPFIND (MODE-941) and and PROPPATCH (MODE-984)
  • The file system connector is now pageable, so it can efficiently project directories with lots of files and folders (MODE-1982)

See our release notes for detail on all the changes in this release.

Access control

The initial support JCR 2.0’s access control management feature allows you to define for individual nodes one or more access control lists (ACLs) that define the privileges that specific users have. To do this, simply add the “mode:accessControllable” mixin to a node and then use the Session’s AccessControlManager to add ACLs for each principal. (A principal can be the name of user or group that is known to the authentication system.) If a node has no ACLs, then the ACLs on the nearest ancestor applies; if no ancestor has any ACLs, then the node can be accessed as usual. Thus, an authenticated session will only be able to access nodes for which they have the appropriate role (e.g., read, write, admin, etc.) and if the ACLs grant the session appropriate permissions.

We’ve categorized this new features as a “technology preview” so that people can give it a try and help us stabilize the functionality, but to also suggest that it’s too early to use this feature in production. Also, checking ACLs does add a little overhead to ModeShape’s existing permission  logic, but we’ve made sure that only repositories in which ACLs are created will have this overhead. That means that if you don’t use this feature, you won’t see any of the ACL-related overhead.

ModeShape and EAP

As with 3.3.0.Final, this release works atop EAP 6.1.0.GA. And we have new quickstarts that show how easy it is to use ModeShape when deployed this way (you can also download them from our downloads page). See this discussion post for background on what deploying on top of EAP means for community users.

Get the release

The artifacts are in the JBoss Maven repository (and hopefully will appear in Maven Central soon) and on our downloads page. Our getting started guide has instructions, ModeShape 3 documentation and JavaDoc are available, and our code is on GitHub. Join us on our forums or IRC channel to ask questions, and please log any issues in our JIRA.

Once again, we had a lot of help this release from our community members that reported, fixed issues, and contributed fixes and features! Thanks to the whole community for a job well-done!

Filed under: features, jcr, releases, rest

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

ModeShape is

a lightweight, fast, pluggable, open-source JCR repository that federates and unifies content from multiple systems, including files systems, databases, data grids, other repositories, etc.

Use the JCR API to access the information you already have, or use it like a conventional JCR system (just with more ways to persist your content).

ModeShape used to be 'JBoss DNA'. It's the same project, same community, same license, and same software.



%d bloggers like this: