PUBLIC MARKS from holyver with tags java & doc

There are several approaches that I could take when discussing the JCR. In this article, I examine the features offered by the JSR-170 specification from a developer's perspective, focusing on the available API and the interfaces that allow a programmer to efficiently use the JSR-170 repository in designing a content application. As an artificial example, I'll implement a trivial back end for a Wikipedia-like encyclopedia system, called JCRWiki, with support for binary content, versioning, backup, and search. I use Apache Jackrabbit, an open source implementation of JSR-170, to develop this application.

The Java Content Repository specification (JSR-170) focuses on "content services," where these not only manage data, but offer author based versioning, full-text searches, fine grained access control, content categorization and content event monitoring. Programmers can use repositories in many ways just like a JDBC connection accesses a database: programmers obtain a connection to a repository, open a session, use the session to access a set of data, and then close the session. The JCR specification has multiple levels of compliance; the most simple level offers read-only access to a repository, XPath-like queries, and some other elements, while other levels of the specification offer a SQL-like query syntax, write capabilities, and more advanced features.

Now that Apache Geronimo has earned Java™ 2 Platform, Enterprise Edition (J2EE) 1.4 certification and has reached version 1.1.1, many developers will be moving away from building their software on top of more restrictive platforms. Specifically, there have been a number of articles and tutorials written lately describing migrating away from the JBoss application server to Apache Geronimo. This installment of The Geronimo renegade column describes many advantages of doing so.