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 209BFD01A for ; Fri, 27 Jul 2012 19:55:07 +0000 (UTC) Received: (qmail 56808 invoked by uid 500); 27 Jul 2012 19:55:07 -0000 Delivered-To: apmail-sling-commits-archive@sling.apache.org Received: (qmail 56758 invoked by uid 500); 27 Jul 2012 19:55:07 -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 56750 invoked by uid 99); 27 Jul 2012 19:55:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jul 2012 19:55:07 +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; Fri, 27 Jul 2012 19:55:05 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 248BB23889E1 for ; Fri, 27 Jul 2012 19:54:22 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r827229 - in /websites/staging/sling/trunk/content: ./ documentation/the-sling-engine/the-sling-launchpad.html Date: Fri, 27 Jul 2012 19:54:22 -0000 To: commits@sling.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120727195422.248BB23889E1@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Fri Jul 27 19:54:21 2012 New Revision: 827229 Log: Staging update by buildbot for sling Modified: websites/staging/sling/trunk/content/ (props changed) websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html Propchange: websites/staging/sling/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Jul 27 19:54:21 2012 @@ -1 +1 @@ -1352785 +1366516 Modified: websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html ============================================================================== --- websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html (original) +++ websites/staging/sling/trunk/content/documentation/the-sling-engine/the-sling-launchpad.html Fri Jul 27 19:54:21 2012 @@ -136,11 +136,11 @@ stop -- -Stop a (remote) Sling application is running. Uses option -j to define the address of the Sling instance to stop. Note, that the Sling application terminates after stopping the (remote) Sling instance. +Stop a (remote) Sling application is running. Uses option -j to define the address of the Sling instance to stop. Note, that the Sling application tesrminates after stopping the (remote) Sling instance. -j - host ":" port +[ host ":" ] port The socket address to listen on for control connections (start or to use as the remote endpoint for the control connection (status and stop. If this parameter has no arguments or is not specified, the address defaults to any free port on localhost/127.0.0.1. If only the port is specified localhost/127.0.0.1 is used as the host part of the address. @@ -207,10 +207,10 @@

Suggestions: Do not allow the control port to be opened on an externally visible interface. Using the localhost/127.0.0.1 is just sufficient. - Make sure only legitimate users have access to the installation folder of Sling ($\{sling.home}).

+ Make sure only legitimate users have access to the installation folder of Sling (${sling.home}).

Servlet Parameters

The Web Application does not require specific servlet parameters. Those which are specified are used to overwrite any properties with the same name from the sling.properties file. One exception to this rule is the sling.home parameter, which is used to set the value of the sling.home property. If no parameter with this name is defined the Sling home directory is derived from the context path at which the Sling Web Application is registered.

-

The sling.home folders for Sling Web Applications without the sling.home servlet parameter are all located in the sling folder in the current working directory as reported by the user.dir system property. The name of the actual directory is derived from the Web Application Context Path by replacing all slash characters / by underscore characters \*. For the root context a single underscore character \* is used.

+

The sling.home folders for Sling Web Applications without the sling.home servlet parameter are all located in the sling folder in the current working directory as reported by the user.dir system property. The name of the actual directory is derived from the Web Application Context Path by replacing all slash characters / by underscore characters _. For the root context a single underscore character _ is used.

Examples:

@@ -222,15 +222,15 @@ - + - + - +
rootsling/\_sling/_
/slingsling/\_slingsling/_sling
/sling/instance1sling/\*sling\*instance1sling/_sling/instance1
@@ -246,21 +246,21 @@ root -/var/sling/\_ +/var/sling/_ /sling -/var/sling/\_sling +/var/sling/_sling /sling/instance1 -/var/sling/\*sling\*instance1 +/var/sling/_sling/instance1

sling.properties

The sling.properties file contains the initial setup of the Sling Application and the OSGi framework. Some of the parameters are required and should not be modified without a very good reason. Some parameters may be freely modified to your needs. Please see the inlined comment in the sling.properties file installed when Sling is first started.

-

One thing to note is, that the sling.properties file is a simple Java Properties file with support for property references. That is, the value of properties may refer other property values by means of the well known $\{name} notation. Such property references may even be cascaded as in

+

One thing to note is, that the sling.properties file is a simple Java Properties file with support for property references. That is, the value of properties may refer other property values by means of the well known ${name} notation. Such property references may even be nested as in

java.packages=${jre-${java.specification.version}}
 
@@ -315,12 +315,7 @@ 15 JCR Repository (Jackrabbit) -commons-collections, commons-io-1.4.jar - - -commons-lang, jackrabbit-api, jackrabbit-jcr-commons, org.apache.sling.commons.mime, org.apache.sling.commons.osgi, org.apache.sling.jcr.api, org.apache.sling.jcr.base, org.apache.sling.jcr.jackrabbit.server, org.apache.sling.jcr.webdav - - +commons-collections, commons-io-1.4.jar, commons-lang, jackrabbit-api, jackrabbit-jcr-commons, org.apache.sling.commons.mime, org.apache.sling.commons.osgi, org.apache.sling.jcr.api, org.apache.sling.jcr.base, org.apache.sling.jcr.jackrabbit.server, org.apache.sling.jcr.webdav 0 @@ -339,7 +334,7 @@

That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 2.4 (or later) compliant servlet container.

- Rev. 1341376 by fmeschbe on Tue, 22 May 2012 09:41:06 +0000 + Rev. 1366516 by fmeschbe on Fri, 27 Jul 2012 19:54:11 +0000
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project