Java specifications most heared about in content management
Last week CMS Watch analist Adriaan Bloem published a cheat sheet with the four Java Specification Requests (JSR) most heared about in content management, a useful list:
- JSR-168, the Java Portlet Specification. This is the standard for the relation between a portlet container (portal software) and the portlets it can display. In theory, JSR-168 compliant portlets can be displayed in any JSR-168 compliant portal.
- JSR-286, version 2.0 of the same specification (with several improvements, e.g. the standardization of how portlets communicate with each other).
- JSR-170, the Content Repository API for Java. This is the definition of an API to access content repositories. Also known as JCR (the Java Content Repository). To confuse matters more, the standard only describes the API, but “JCR” is commonly used to refer to actual software. Such as Apache Jackrabbit, the JSR-170 reference implementation.
- JSR-283, version 2.0 of the same specification (which adds several functions the original specification was lacking, such as improved versioning).