An open-source, federated content repository

JBoss AS 5.0.0 is JEE 5 certified (officially)

JBoss AS 5.0.0 was released late last week, and now it’s officially certified as Java EE 5 compatible. Congratulations to the JBoss AS team!

Get your copy today.

Filed under: news

Apache Jackrabbit 1.5.0 released

The Apache Jackrabbit project announced today that version 1.5.0 has been released and is available. There are a number of pretty substantial improvements and changes in this release. For all the details, check out Jukka’s blog.

Congratulations to the Jackrabbit team!

Filed under: jcr, news, repository

JBoss AS 5.0.0.GA is available

Great news from JBoss – AS 5.0.0.GA has been released. It’s been a long time coming. Dimitris made the announcement, and Sacha describes what this means for the whole of JBoss.

This really is a watershed event, since the new Microcontainer has such an amazing framework for assembling all kinds of services and technologies. All the cool stuff that Bob is doing with JBoss Rails (1.0 Beta2 earlier this week) is just one example.



Filed under: news

AtomPub, REST, repositories … and Starbucks?

InfoQ has a great article on how REST and AtomPub work, using a “Starbucks” example. (Via Joel Amoussou.)

One thing this article does well is explain how representations can contain URIs for followup activities (e.g., what can be done next with a resource). In addition to the “next” used in the article, activities might include undoing the last change, or “publishing” some artifact. This works extremely well when coupled with some sort of state transition (process) engine on the back end and allows clients to “discover” the process, even when that process changes! And note that the process might include lifecycle changes and/or workflow.

Now, how does REST and AtomPub relate to JBoss DNA and JCR repositories? Well, it’s always useful to have a REST API into a JCR repository. For the most part, I think a generic repository library like JBoss DNA will provide a generic REST interface. After all, working with a JCR repository doesn’t have a lot of process – it’s mostly just simple get/post/put/delete operations on the nodes (resources). But AtomPub only defines three levels (services, collections, and entries), and this doesn’t really map well to a hierarchical repository. (Yes, I could conceive of several different mappings, but the question is whether any of them really are useful.)

So while a content repository system might not provide a generic AtomPub, a domain that uses a JCR repository may very well want to use AtomPub to allow clients to work with the domain’s content. Consider a SOA governance repository, which may have multiple collections (e.g., “services”, “published services”, “news”, “policies”, etc.), and workflow (e.g., uploading a service, publishing a service, etc.). Here, AtomPub can be mapped to the SOA governance domain pretty easily, but this mapping is probably different than other domains.

It would be nice if JBoss DNA could have a generic “AtomPub” facility that is content-driven: specify the collections (maybe defined as queries), map the entities to workflow processes, etc. But that’s getting ahead of ourselves. First things first.

Filed under: rest, techniques, tools

JBoss DNA is on Ohloh

The JBoss DNA project is now on Ohloh, which offers a pretty cool analysis of open source projects. If you’re a user, have a look and give us a vote. Or, if you’re a contributor, go to the contributors list and click on your name to claim your commits.

According to their analysis, we have 140K lines of code containing almost 74K lines of Java and 52K lines with comments. Oh, and remember that they’re including all the test resource files and DocBook source, which is why they’ve listed the languages to include Flex, XML Schema, JavaScript, CSS, etc. Here are the latest stats:

Filed under: tools

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.