Joe Darcy, JDK Engineer at Oracle, proposed a consolidation of the Mercurial (Hg) repositories for JDK 10 OpenJDK to a single repository that sparked a debate over scalability, performance, and other difficulties.
Last week Adobe Systems announced it was purchasing Day Software for $240 million. The deal combines Day’s JSR-170/238 based content management and digital asset management products with Adobe’s Flex, Flash and AIR in a move to corner the web content market. In addition to being a lead company for the JSR-170/238 specifications, Day also contributes to Apache Jackrabbit and Sling.
This article by Benjamin Mestrallet and Tugdual Grall provides an overview of the eXo platform, the Portlet 1.0 (JSR 168) and Portlet 2.0 (JSR 286) specifications. Topics covered include new features in the eXo Web 2.0 Portal, new capabilities in the Portlet 2.0 API, Inter-portlet communication, the eXo Java Content Repository, eXo Enterprise Content Management and the eXo business model.
InfoQ.com is a next generation web portal combining the latest advancements in portal technology and web development. In this presentation, Alexandru Popescu and Floyd Marinescu walks through the good, the bad, and the ugly of building InfoQ.com; from initial (lack of) requirements, designs, implementation choices, and deployment issues, and all the lessons learned along the way.
In this interview, Day CTO and JCR Spec Lead David Nuescheler discusses the benefits of JCR, the Java Content Repository standard, the difference between an API such as Atom/Atom Publishing protocol and JCR, JCR's connection to REST, and Apache Sling, a new kind of Web framework.
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.
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.
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.
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.
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.
Exo and Objectweb have announced the release of their Java Content Repository JCR 1.0 open source product (an implementation of JSR 170) as well as ECM (Enterprise Content Management) 1.0 tools, part of the eXo portal platform which also includes a JSR 168 compliant portal server.
Day Software has released version 1.2 of Day Content Repository Extreme (CRX). CRX is a content repository implementing the new Content Repository for Java Technology (JCR) standard. This release adds Apache Derby support, Active/Passive Clustering, and full JSR 170 compliance. InfoQ spoke to Day CTO David Nuescheler to get more information.
Magnolia, the CMS that InfoQ itself uses, has released version 3 of its open-source Enterprise Content Management System (ECM) today. Main new features include workflow, versioning, JSR-168 support, single-sign-on, scheduled content publishing, a browser-based template-designer, a deployment packager and a new UI.