Here are some links to other resources


About Sling

  • Sling on dev.day.com - Day's developers blog, regularly includes articles on Sling and JCR. Powered by Sling, of course.
  • Sling on Lars Trieloff's Blog - Lars regularly writes on his experiences with Sling. Most notably the mini series of three entries introducing Sling and microsling.
  • Sling links at del.icio.us - If you're a del.icio.us user, please tag Sling-related posts with both sling and jcr tags, so that they appear in that list.
  • Sling on Fisheye - code repository viewer, activity statistics, etc.
  • Sling on ohloh - activity and community statistics.
  • Sling on MarkMail - searchable mailing list archives.

Projects using Sling

  • Gert Vanthienen succeeded in installing Sling into the new Apache ServiceMix kernel and documented his experience Sling On ServiceMix Kernel

Sling Presentations and Screencasts

The following screencasts demonstrate Day Software's CRX quickstart product, powered by Sling:

From ApacheCon EU 08

From ApacheCon US 07

Technology used by Sling

JSR 170 - Content Repository for Java{tm} technology API

The specification of the repository API: JSR 170: Content Repository for Java{tm} technology API.

Apache Jackrabbit

The main purpose of Sling is to develop a content-centric Web Application framework for Java Content Repository (JCR) based data stores. Sling is implemented - with the notable exception of JCR Node Type management - purely in terms of the JCR API and as such may use any JCR compliant repository. The default implementation for Apache Jackrabbit is provided out of the box. This is also the reference implementation of the Content Repository for Java (JCR) Specification.

The OSGi Alliance

The OSGi Alliance is the specification body defining the OSGi specifications, namely the Core, Compendium, Enterprise and IoT specifications. These specifications are at the center of making Sling possible. Sling is implemented as a series of OSGi modules (called bundles) and makes extensive use of the OSGi functionality, such as lifecycle management and the service layer. In addition, Sling requires several OSGi compendium services to be available, such as the Log Service, Http Service, Configuration Admin Service, Metatype Service, and Declarative Services.

Apache Felix

While Sling does not require a specific OSGi framework implementation to run in, Sling is being developed using Apache Felix as the OSGi framework implementation. It has not been tested yet, but it is expected that Sling also operates perfectly inside other OSGi frameworks such as Equinox and Knopflerfish.