developer toolbox

http://incubator.apache.org/sling/site/architecture.html

Architecture of Sling

• OSGi — The Sling application is built as a series of OSGi bundles and makes heavy use of a number of OSGi core and compendium services
• Sling API — To implement Content based Web Applications with Sling, a an API has been defined, which extends the Servlet API and provides more functionality to work on the content
• Request Processing — Sling takes a unique approach to handling requests in that a request URL is first resolved to a resource and only based on the resource then select the actual servlet or script to handle the request.
• Resources — The central mantra of Sling is the Resource, which represents the resource addressed by any request URL. It is the resource, which is first resolved when handling a request. Based on the resource, a first servlet or script is then looked up to actually handle the request.
• Servlets and Scripts — Servlets and Scripts are handled uniformly in that they are represented as resources themselves and are accessible by a resource path.
• Launchpad — Sling uses a very thin launcher to integrate with an existing servlet container launching Sling as a Web Application or providing a main class to represent a standalone Java Application.

prvi put pročitao o sling-u na ovom h-online članku:

Apache Sling 5 slung into the wild

The Apache Sling developers have announced the release of Apache Sling 5. The project, currently in the Apache Incubator, aims to allow developers to manage and update content on the web using a REST style interface. The developers suggest applications such as wikis, digital asset management and web content management as appropriate uses for Sling. To that end, it comes as a standalone application for getting started and a web application which can be dropped into a web container. Sling is composed of OSGi bundles and includes Apache Jackrabbit as a JSR-170 compliant Java Content Repository.

Rather than manipulate files and folders "behind" the server, with Sling, all administration and development is done with REST style calls. The documentation shows how the Sling server can be configured using only the curl command to upload and manipulate the server. Uploads can include server-side scripts for execution. A web based management console allows a developer to control the OSGi bundles that make up the Sling server and which other bundles are loaded into its embedded Apache Felix OSGi service platform.

Apache Sling 5 is licensed under the Apache Licence 2.0, and is available to download now.

http://incubator.apache.org/sling/site/getting-and-building-sling.html

napravio ~/.m2/settings.xml

sling$ export MAVEN_OPTS=-Xmx256m
sling$ mvn -s /dev/null clean install