Tracking change and innovation in the enterprise software development community
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
Posted by R.J. Lorimer on Mar 07, 2008 01:45 PM
The eXo Platform team has released eXo JCR (Java Content Repository) 1.8, a JSR-170-compliant Java content repository implementation. The eXo JCR website describes the Java content repository specification in this way:The main purpose of standardized Java Content Repository is to provide standardized, reliable intermediary layer between custom applications and data storage. The documents could be stored in a relational database or in a native XML DB but your client code would not change.In a prior article about integrating JCR implementations with Spring, InfoQ had this to say about JSR-170:
Sitting on top of the data storage, JCR offers content services like granular access control, versioning, content events, full-text search and filtering among others. With an impressive expert group behind JSR-170 led by Day Software, including Content Management Systems (CMS) vendors like Vignette, Hummingbird Ltd., Stellent and the usual Java-driven solution providers like BEA Systems, IBM and Oracle, the specification is likely to become the de-facto standard for content management and document storage.The referenced InfoQ article discusses a number of implementations of the JCR spec including eXo JCR as well as Apache Jackrabbit, which is the reference implementation of the JSR-170 specification. Since the original writing of the article, both Jackrabbit and eXo JCR have experienced a number of releases and enhancements.
Hibernate without Database Bottlenecks
Create a photo album application with Project Zero and REST design principles
Scaling a Massively Multi-player Server Casestudy: Terracotta on SmartFoxServer
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
1 comment
Reply