[CONF] Apache Sling Website: Apache Sling (page edited)

[confluence]

Page Edited : SLINGxSITE : Apache Sling Apache Sling has been edited by Mike Mueller (Jun 01, 2009). (View changes) Content: Apache Sling - Bringing Back the Fun Apache Sling is an innovative web framework that is intended to bring back the fun to web development. It uses all those nice cool and new technologies that make up a state-of-the-art framework. This is Apache Sling in five bullets: REST based web framework Content-driven, using a JCR content repository Powered by OSGi Scripting inside, multiple languages Apache Open Source project Welcome to Sling Apache Sling (currently in incubation) is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way. The embedded Apache Felix OSGi framework and console provide a dynamic runtime environment, where code and content bundles can be loaded, unloaded and reconfigured at runtime. As the first web framework dedicated to JSR-170 Java Content Repositories, Sling makes it very simple to implement simple applications, while providing an enterprise-level framework for more complex applications. Discussions about Sling happen on our mailing lists, see the Project Information page for more info. History Sling started as an internal project at Day Software, and entered the Apache Incubator in September 2007. See the Sling status page for more information. The name "Sling" has been proposed by Roy Fielding who explained it like this: [The name is] Biblical in nature. The story of David: the weapon he uses to slay the giant Goliath is a sling. Hence, our David's [David Nuescheler, CTO of Day Software] favorite weapon. It is also the simplest device for delivering content very fast. Who uses Sling? Being a young project, Sling does not have a large user base yet, but due to its unique features interest is growing steadily. We'll happily add more references here, let us know if you have concrete examples. The upcoming next generation of Day Software's products (CMS, collaboration tools, digital asset management, ...) is built on Sling and Jackrabbit. Getting started If you prefer doing rather than reading, please proceed to Discover Sling in 15 minutes or read through the recommended links in the Getting Started section, where you can quickly get started on your own instance of Sling. Excuse our mess while we redesign Sling has undergone an important redesign in the last few months, and we're not done updating this website yet. The status of each page is indicated by a note like this at the top of each page. Pages which do not have such a note should be considered not reviewed: the information that they contain might be out of sync with the current Sling codebase. Contents Documentation - Here you will find the documentation on Sling Development – Documentation on how to develop web applications with Sling and what tools you have at your disposal Links Wiki FAQ Project Information Use Cases for Sling Wiki Day built a Wiki system on Sling. Each Wiki page is a node (with optional child nodes) in the repository. As a page is requested, the respective node is accessed and through the applying Component is rendered. Thanks to the JCR Mapping and the resolution of the Component from the mapped Content, the system does not care for what actual node is addressed as long as there is a Content mapping and a Component capable of handling the Content. Thus in the tradition of REST, the attachement of a Wiki page, which happens to be in a node nested below the wiki page node is easily accessed using the URL of the wiki page attaching the relative path of the attachement ode. The system resolves the URL to the attachement Content and just calls the attachement's Component to spool the attachement. Digital Asset Management Day has implemented a Digital Asset Management (DAM) Application based on Sling. Thanks to the flexibility of the Content/Component combo as well as the service registration/access functionality offered by OSGi, extending DAM for new content type is merely a matter of implementing one or two interfaces and registering the respective service(s). Again, the managed assets may be easily spooled by directly accessing them. Web Content Management Last but not least, Sling offers itself very well to implementing a Web Content Management system. Thanks to the flexibility of rendering the output - remmber: the system does not care what to render, as long as the URL resolves to a Content object for which a Component exists, which is called to render the Content - providing support for Web Content authors (not PHP programmers but users out in the field) to build pages to their likings can easily be done. References 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. OSGi Sling is implemented as a series of OSGi 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.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences