The eXo Platform team has released eXo JCR (Java Content Repository) 1.8. The eXo JCR product is a JSR-170-compliant Java content repository implementation.
Liferay Portal, a Java-based open source enterprise portal and content management system (CMS), recently released version 4.4. InfoQ spoke with Liferay CTO Michael Young to learn more about this release and about Liferay in general.
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR), and has released version 1.4 after over 9 months of hard work. In the 1.4 release are 220 new features, improvements, and bug fixes since the 1.3 release, making 1.4 the largest release to date.
It's a good time for Java Content Repositories. The second version of the JCR API has been released for public review as JSR-283 and, at the same time, JCR 1.0 has been doing well. InfoQ took the opportunity to speak with David Nuescheler, CTO of Day Software and the spec lead for JSRs 283 and 170.
In this latest InfoQ article, Costin Leau introduces JSR 170 (Java Content Repositories) and how to integrate it with Spring Modules' JCR module, whose main objective is to simplify development with the JSR-170 API in a similar manner to that of the ORM package from the main Spring distribution.
Alfresco has released version 2.0 of their Enterprise Content Management (ECM) system. InfoQ sat down with Ian Howells of Alfresco to talk about ECM systems and Alfresco.
The eXo Platform recently announced new versions of their Portal and ECM products at JavaPolis. InfoQ sat down with Benjamin Mestrallet of eXo Platform to talk about the new products. eXo is targetting the products to simulate a web operating system that fits enterprise needs.
Two new articles are out bolstering the documentation on using JSR-170, the Java Content Repository API. The first is a practitioner's perspective which has an informative FAQ and the second is an in-depth look at versioning and observation using JackRabbit.
This week Roy Russo announced the creation of the Portlet Repository Protocol (PRP) which seeks to create a common web service API that can be used to communicate with portlet repositories. This would allow any portal vendor to browser repositories and download/update portlets like developers currently do when browsing/installing/updating plugins for their IDE of choice.
The Java Content Repository (JCR) API provides a standard way to access content repositories. Content repositories is a superset of a traditional data repository that adds features such as full text searching and storing of structured/unstructured data. OnJava has released a new article by Sunil Patil detailing the installation, configuration, and usage of a Version 1.0 implementation.
BEA has announced the completion and delivery of WebLogic Platform 9.2 (Server, Portal, and Integration) that are designed to provide a unified foundation for BEA's SOA 360 platform. Kodo 4.1, Workshop, and Workshop Studio also had new releases. InfoQ summarized the new features in WL Server and Portal.
Nuxeo has announced that the next version of its ECM product will be based entirely on Java, using JBoss SEAM, EJB 3, and JBoss. The move is interesting for a company claiming to be "the biggest Zope-focused company in the world." InfoQ spoke to Nuxeo's engineering team to find the why and how of their move.
The 'unofficial Ruby on Rails blog' looks at twenty different content management systems created in Ruby on Rails.
IBM has announced Websphere Portal Server 6.0, it's entry level Portal offering which includes a Portlet design tool, basic SSO, personalization-rules, configurable security policies, built in search, the ability to host multiple distinct sites off one instance, WSRP, and JSR 168 Portlets. InfoQ spoke to IBM to find out more about Portal development in the enterprise.
Version 2.0 of the Portlet Specification (JSR 286) has been released for public review. The reference implementation for this JSR will be the Apache Pluto project. The new Portlet Specifications will add functionality that was not addressed in the first version specification.