Get your copy today.
December 11, 2008 • 12:34 pm 0
December 8, 2008 • 10:44 am 0
December 5, 2008 • 8:18 am 0
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.
December 4, 2008 • 9:45 am 0
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.
December 1, 2008 • 9:13 pm 0
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.