Return-Path: X-Original-To: apmail-sling-commits-archive@www.apache.org Delivered-To: apmail-sling-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 35FD3C0F5 for ; Sat, 19 May 2012 22:34:36 +0000 (UTC) Received: (qmail 65215 invoked by uid 500); 19 May 2012 22:34:36 -0000 Delivered-To: apmail-sling-commits-archive@sling.apache.org Received: (qmail 65150 invoked by uid 500); 19 May 2012 22:34:36 -0000 Mailing-List: contact commits-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list commits@sling.apache.org Received: (qmail 65143 invoked by uid 99); 19 May 2012 22:34:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 May 2012 22:34:36 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 May 2012 22:34:34 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 876DC23889BF for ; Sat, 19 May 2012 22:34:14 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r818349 - in /websites/staging/sling/trunk/content: ./ index.html Date: Sat, 19 May 2012 22:34:14 -0000 To: commits@sling.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120519223414.876DC23889BF@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Sat May 19 22:34:14 2012 New Revision: 818349 Log: Staging update by buildbot for sling Modified: websites/staging/sling/trunk/content/ (props changed) websites/staging/sling/trunk/content/index.html Propchange: websites/staging/sling/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Sat May 19 22:34:14 2012 @@ -1 +1 @@ -1340579 +1340584 Modified: websites/staging/sling/trunk/content/index.html ============================================================================== --- websites/staging/sling/trunk/content/index.html (original) +++ websites/staging/sling/trunk/content/index.html Sat May 19 22:34:14 2012 @@ -81,11 +81,10 @@

Apache Sling - Bringing Back the Fun!

-

{tm}Apache Sling{tm} is an innovative web framework that is intended to +

Apache Sling™ is an innovative web framework that is intended to bring back the fun to web development.

Discussions about Sling happen on our mailing lists, see the Project Information page for more info.

-

Apache Sling in five bullets points

  • REST based web framework
  • @@ -95,11 +94,8 @@ bring back the fun to web development.
  • Apache Open Source project
-

Apache Sling in a hundred words

-

Apache Sling is a web framework that uses a Java Content Repository -, such as [Apache Jackrabbit|http://jackrabbit.apache.org/] -, to store and manage content.

+

Apache Sling is a web framework that uses a Java Content Repository, such as [Apache Jackrabbit|http://jackrabbit.apache.org/], 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 @@ -110,29 +106,25 @@ runtime.

Java Content Repositories, Sling makes it very simple to implement simple applications, while providing an enterprise-level framework for more complex applications.

-

News

{excerpt-include:News|nopanel=true} * all news...

-

History

Sling started as an internal project at Day Software , and entered the Apache Incubator in September 2007. As of June, 17th, 2009 Apache Sling is a top level project of the Apache Software Foundation.

The name "Sling" has been proposed by Roy Fielding who explained it like this:

-

{quote} -[The name is](the-name-is.html) - 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.

+
+

[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. {quote}

-

Who uses Sling?

See Who is using Sling on our public wiki.

-

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] @@ -146,7 +138,6 @@ page.

the information that they contain might be out of sync with the current Sling codebase. {note}

-

Contents

-

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 @@ -175,7 +164,6 @@ happens to be in a node nested below the 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 @@ -183,7 +171,6 @@ the service registration/access function 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 @@ -192,9 +179,7 @@ URL resolves to a Content object for whi 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 @@ -202,7 +187,6 @@ implemented - with the notable exception 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 @@ -210,7 +194,6 @@ lifecycle management and the service lay 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 @@ -221,7 +204,7 @@ such as [Equinox|http://www.eclipse.org/ .

- Rev. 1076286 by bdelacretaz on Wed, 2 Mar 2011 16:45:58 +0000 + Rev. 1340584 by fmeschbe on Sat, 19 May 2012 22:34:10 +0000
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project