Hot off the presses is the latest release for JBoss DNA [1].  Our Getting Started document [2] and Reference Guide [3] were both completely rewritten to be more thorough and better reorganized.  Among the features are even better JCR compatibility, a RESTful web service for accessing and changing repository content (via RESTEasy), a new configuration system that leverages a configuration repository, an read-only SVN connector, a faster federation connector with a fork-join algorithm, an improved connector framework, and updated connectors and sequencers.  That's just some of what's in the release.

JBoss DNA is a JCR implementation that provides access to content stored in many different kinds of systems. A JBoss DNA repository isn't yet another silo of isolated information. Rather it's a JCR view of the information you already have in your environment: files systems, databases, other repositories, services, applications, etc.
To your applications, JBoss DNA looks and behaves like a regular JCR repository. Using the standard JCR API, applications can search, navigate, version, and listen for changes in the content. But under the covers, JBoss DNA gets its content by federating multiple back-end systems (like databases, services, other repositories, etc.), allowing those systems to continue "owning" the information while ensuring the unified repository stays up-to-date and in sync.

Thanks to the whole JBoss DNA team for their hard work on this release.  The team has grown steadily over the last 6 months - we're now at 10 contributors that are all stellar.  With 0.5 under our belt, our next release will be focusing on passing the remaining parts of the JCR TCK (Level 1 and Level 2, plus some optional features).  As always, if you're interested in helping, please join the dna-dev@lists.jboss.org list or pop into our IRC room (irc.freenode.net#jbossdna).

Regards,

Randall