Author: buildbot
Date: Thu Apr 25 17:28:49 2013
New Revision: 859891
Log:
Staging update by buildbot for sling
Added:
websites/staging/sling/trunk/content/res/docs/
websites/staging/sling/trunk/content/res/docs/ApacheConEU08_FFT_Sling.pdf
(with props)
websites/staging/sling/trunk/content/res/docs/ApacheConEU08_JCR_Meetup_Sling_Architecture.pdf
(with props)
websites/staging/sling/trunk/content/res/docs/ApacheConUS07_FFT_Sling.pdf
(with props)
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
websites/staging/sling/trunk/content/documentation/development/client-request-logging.html
websites/staging/sling/trunk/content/documentation/development/getting-and-building-sling.html
websites/staging/sling/trunk/content/documentation/development/issue-tracker.html
websites/staging/sling/trunk/content/documentation/development/logging.html
websites/staging/sling/trunk/content/documentation/development/release-management.html
websites/staging/sling/trunk/content/documentation/development/repository-based-development.html
websites/staging/sling/trunk/content/documentation/development/sling.html
websites/staging/sling/trunk/content/documentation/getting-started/discover-sling-in-15-minutes.html
websites/staging/sling/trunk/content/documentation/the-sling-engine/architecture.html
websites/staging/sling/trunk/content/documentation/the-sling-engine/resources.html
websites/staging/sling/trunk/content/links.html
websites/staging/sling/trunk/content/project-information/project-team.html
websites/staging/sling/trunk/content/project-information/security.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 25 17:28:49 2013
@@ -1 +1 @@
-1475804
+1475862
Modified:
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/apache-sling-eventing-and-job-handling.html
Thu Apr 25 17:28:49 2013
@@ -93,10 +93,9 @@
<em> <a
href="/documentation/tutorials-how-tos/how-to-manage-events-in-sling.html">How
to Manage Events in Sling</a>
</em> <a
href="/documentation/bundles/scheduler-service-commons-scheduler.html">Scheduler
Service (commons scheduler)</a></p>
<p>The Sling Event Supports adds the following services:
-<em> <a href="">Jobs</a>
-</em> <a href="">Distributed Events</a>
-* <a href="">Scheduled Events</a></p>
-<p>{anchor:jobs}</p>
+<em> <a href="#jobs-guarantee-of-processing">Jobs</a>
+</em> <a href="#distributed-events">Distributed Events</a>
+* <a href="#sending-scheduled-events">Scheduled Events</a></p>
<h2 id="jobs-guarantee-of-processing">Jobs (Guarantee of Processing)</h2>
<p>In general, the eventing mechanism (OSGi EventAdmin) has no knowledge about
the contents of an event. Therefore, it can't decide if an event is important
and should be processed by someone. As the event mechanism is a "fire event and
forget about it" algorithm, there is no way for an event admin to tell if
someone has really processed the event. Processing of an event could fail, the
server or bundle could be stopped etc.</p>
<p>On the other hand, there are use cases where the guarantee of processing a
job is a must and usually this comes with the requirement of processing this
job exactly once. Typical examples are sending notification emails (or sms) or
post processing of content (like thumbnail generation of images or
documents).</p>
@@ -187,7 +186,6 @@
<p>As we follow the principle of distributing each event to every registered
handler, the handler has to decide if it will process the event. In order to
avoid multiple processing of this event in a clustered environment, the event
handler should check the <em>event.application</em> property. If it is not set,
it's a local event and the handler should process the event. If the
<em>event.application</em> is set, it's a remote event and the handler should
not process the event. This is a general rule of thumb - however, it's up to
the handler to make its decision either on <em>event.application</em> or any
other information.</p>
<p>It is advisable to perform the local event check even in a non clustered
environment as it makes the migration to a cluster later on much easier and
there is nearly no performance overhead caused by the check.</p>
<p>The ~EventUtil class provides an utility method
<em>isLocalEvent(Event)</em> which checks the existance of the
<em>event.application</em> property and returns <em>true</em> if it is
absend.</p>
-<p>{anchor:distributed}</p>
<h2 id="distributed-events">Distributed Events</h2>
<p>In addition to the job handling, the Sling Event support adds handling for
distributed events. A distributed event is an OSGi event which is sent across
JVM boundaries to a different VM. A potential use case is to broadcast
information in a clustered environment.</p>
<h3 id="sources-of-events">Sources of Events</h3>
@@ -196,7 +194,7 @@
</em> Application generated events
<em> Events from messaging systems (~JMS)
</em> "External events"</p>
-<p>The events can eiter be generated inside a current user context, e.g. when
the user performs an action through the UI, or they can be out of a user
context, e.g. for schedulded events. This leads to different weights of
events.</p>
+<p>The events can either be generated inside a current user context, e.g. when
the user performs an action through the UI, or they can be out of a user
context, e.g. for schedulded events. This leads to different weights of
events.</p>
<h3 id="weights-of-events">Weights of Events</h3>
<p>We can distinguish two different weights of events, depending how they are
distributed in a clustered environment:</p>
<ul>
@@ -227,7 +225,6 @@
| <em>event:created</em> | The date and time when the event has been
created (stored in the repository)
| <em>event:properties</em> | Serialized properties (except the
<em>event.distribute</em>, but including the <em>event.application</em>) |</p>
<p>Each application is periodically removing old events from the repository
(using the scheduler).</p>
-<p>{anchor:timed}</p>
<h3 id="sending-scheduled-events_1">Sending Scheduled Events</h3>
<p>Scheduled events are OSGi events that have been created by the environemnt.
They are generated on each application node of the cluster through an own
scheduler instance. Sending these events works the same as sending events based
on JCR events (see above).</p>
<p>In most use cases a scheduler will send job events to ensure that exactly
one application node is processing the event.</p>
@@ -246,7 +243,7 @@
<h2 id="scheduling">Scheduling</h2>
<p>The scheduler is a service which uses the open source Quartz library. The
scheduler has methods to start jobs periodically or with a cron definition. In
addition, a service either implementing <em>java.lang.Runnable</em> or
<em>org.quartz.job</em> is started through the whiteboard pattern <em>if</em>
it either contains a configuration property <em>scheduler.expression</em> or
<em>scheduler.period</em>. The job is started with the ~PID of the service - if
the service has no PID, the configuration property <em>scheduler.name</em> must
be set.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1341376 by fmeschbe on Tue, 22 May 2012 09:41:06 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
Thu Apr 25 17:28:49 2013
@@ -92,7 +92,7 @@
<p>If such an install folder contains a binary artifact (e.g. a bundle) this
is provided to the OSGi installer. In addition a node of type
<em>sling:OsgiConfig</em> is provided as a configuration to the installer.</p>
<p>The jcr installer provider does not check or scan the artifacts itself, the
detection and installation is deferred to the OSGi installer.</p>
<h3 id="runmode-support">Runmode Support</h3>
-<p>The JCR installer supports run modes for installing artifacts. By default
folders named <em>install</em> are checked for artifacts. If Apache Sling is
started with one (or more run modes), all folders named <em>install.<a
href="">RUNMODE</a></em> are scanned as well. To be precise, the folder name
can be followed by any number of run modes separated by comma. For example, if
started with run modes <em>dev</em>, <em>a1</em>, and <em>public</em>, folders
like <em>install.dev</em>, <em>install.a1</em>, <em>install.public</em> are
searched as well as <em>install.dev.a1</em>, or <em>install.a1.dev</em>.</p>
+<p>The JCR installer supports run modes for installing artifacts. By default
folders named <em>install</em> are checked for artifacts. If Apache Sling is
started with one (or more run modes), all folders named
<em>install.[RUNMODE]</em> are scanned as well. To be precise, the folder name
can be followed by any number of run modes separated by comma. For example, if
started with run modes <em>dev</em>, <em>a1</em>, and <em>public</em>, folders
like <em>install.dev</em>, <em>install.a1</em>, <em>install.public</em> are
searched as well as <em>install.dev.a1</em>, or <em>install.a1.dev</em>.</p>
<p>Artifacts from folders with a run mode get a higher priority. For example
by default, an <em>install</em> folder underneath <em>/libs</em> gets the
priority <em>50</em>. For each run mode in the folder name, this priority is
increased by <em>1</em>, so <em>install.dev</em> has <em>51</em> and
<em>install.a1.dev</em> is <em>52</em>.</p>
<h1 id="example">Example</h1>
<p>Here's a quick walkthrough of the JCR installer functionality.</p>
@@ -193,7 +193,7 @@
</ul>
<p>Many of these tests are fairly readable, and can be used to find out in
more detail how these modules work.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/client-request-logging.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/client-request-logging.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/client-request-logging.html
Thu Apr 25 17:28:49 2013
@@ -103,13 +103,13 @@
<tr>
<td>Request Log Name</td>
<td><code>request.log.output</code></td>
-<td>Name of the destination for the request log. The request log logs the
entry and exit of each request into and out of the system together with the
entry time, exit time, time to process the request, a request counter as well
as the final status code and response content type. In terms of Request Logger
Service formats, request entry is logged with the format <code>%t \[%R]()
\-> %m %U%q %H</code> and request exit is logged with the format
<code>%\{end}t \[%R] <\- %s %\{Content-Type}o %Dms</code> (See [#Log Format
Specification] below for the specification of the format).</td>
+<td>Name of the destination for the request log. The request log logs the
entry and exit of each request into and out of the system together with the
entry time, exit time, time to process the request, a request counter as well
as the final status code and response content type. In terms of Request Logger
Service formats, request entry is logged with the format <code>%t \[%R\] \->
%m %U%q %H</code> and request exit is logged with the format <code>%\{end}t
\[%R] <\- %s %\{Content-Type}o %Dms</code> (See [#Log Format Specification]
below for the specification of the format).</td>
<td></td>
</tr>
<tr>
<td>Request Log Type</td>
<td><code>request.log.outputtype</code></td>
-<td>Type of Logger named with the Logger Name parameter. See <a href="">#Log
Output</a> below</td>
+<td>Type of Logger named with the Logger Name parameter. See <a href="#Log
Output">Log Output</a> below</td>
<td></td>
</tr>
<tr>
@@ -121,13 +121,13 @@
<tr>
<td>Access Log Name</td>
<td><code>access.log.output</code></td>
-<td>Name of the destination for the access log. The access log writes an entry
for each request as the request terminates using the NCSA extended/combined log
format. In terms of Request Logger Service formats the access log is written
with the format <code>%h %l %u %t "%r" %>s %b "%\{Referer}i"
"%\{User-Agent}i"</code> (See <a href="">#Log Format Specification</a> below
for the specification of the format).</td>
+<td>Name of the destination for the access log. The access log writes an entry
for each request as the request terminates using the NCSA extended/combined log
format. In terms of Request Logger Service formats the access log is written
with the format <code>%h %l %u %t "%r" %>s %b "%\{Referer}i"
"%\{User-Agent}i"</code> (See <a href="#log-format-specification">Log Format
Specification</a> below for the specification of the format).</td>
<td></td>
</tr>
<tr>
<td>Access Log Type</td>
<td><code>access.log.outputtype</code></td>
-<td>Type of Logger named with the Logger Name parameter. See <a href="">#Log
Output</a> below</td>
+<td>Type of Logger named with the Logger Name parameter. See <a
href="#log-output">Log Output</a> below</td>
<td></td>
</tr>
<tr>
@@ -166,7 +166,7 @@
</tr>
</tbody>
</table>
-<p><em>Note:</em> If logging to a file, this file is not rotated and/or
limited by size. To get log file rotation use the <em>Logger Name</em> logging
type. See <a href="">#Rotating Logger Files</a> below for information on how
logging information can be written to rotated and/or size limited files.</p>
+<p><em>Note:</em> If logging to a file, this file is not rotated and/or
limited by size. To get log file rotation use the <em>Logger Name</em> logging
type. See <a href="#rotating-logger-files">#Rotating Logger Files</a> below for
information on how logging information can be written to rotated and/or size
limited files.</p>
<h3 id="additional-per-request-loggers">Additional per-request Loggers</h3>
<p>In the Web Console create <em>Apache Sling Customizable Request Data
Logger</em> (Factory
PID=<code>org.apache.sling.engine.impl.log.RequestLoggerService</code>)
configuration.</p>
<p>In the Sling Web Console locate the Configuration page
(<code>/system/console/configMgr</code>) and click on the <code>+</code> (plus)
symbol on the <em>Apache Sling Customizable Request Data Logger</em> line. This
opens a dialog to enter the configuration whose properties can be configured as
follows:</p>
@@ -183,20 +183,20 @@
<tr>
<td>Log Format</td>
<td><code>request.log.service.format</code></td>
-<td>Specify a <a href="">#Log Format Specification</a> as described below</td>
+<td>Specify a <a href="#log-format-specification">#Log Format
Specification</a> as described below</td>
<td></td>
</tr>
<tr>
<td>Logger Type</td>
<td><code>request.log.service.outputtype</code></td>
<td>Logger Name/<code>0</code></td>
-<td>Type of Logger named with the Logger Name parameter. See <a href="">#Log
Output</a> above</td>
+<td>Type of Logger named with the Logger Name parameter. See <a
href="#log-output">#Log Output</a> above</td>
</tr>
<tr>
<td>Logger Name</td>
<td><code>request.log.service.output</code></td>
<td><code>request.log</code></td>
-<td>Name of the Logger to be used. See <a href="">#Log Output</a> above</td>
+<td>Name of the Logger to be used. See <a href="#log-output">#Log Output</a>
above</td>
</tr>
<tr>
<td>Request Entry</td>
@@ -377,7 +377,7 @@
<li>Optionally, you may create an <em>Apache Sling Logging Writer
Configuration</em> for the log file defined in the previous step to better
control rotation setup. See <a href="">Log Writer Configuration</a> for full
details.</li>
</ol>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/getting-and-building-sling.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/getting-and-building-sling.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/getting-and-building-sling.html
Thu Apr 25 17:28:49 2013
@@ -92,7 +92,7 @@
<li>from the command line (using SVN and the Maven command line tool)</li>
<li>or using Eclipse</li>
</ul>
-<p>Note that you don't <em>have</em> to build Sling yourself, if you don't
need the bleeding-edge stuff you can get prebuilt binaries from the <a
href="">Downloads</a> page.</p>
+<p>Note that you don't <em>have</em> to build Sling yourself, if you don't
need the bleeding-edge stuff you can get prebuilt binaries from the <a
href="/downloads.cgi">Downloads</a> page.</p>
<p>A full build of Sling takes 5-10 minutes on a recent computer once your
local Maven repository is up to date. The first build may take much longer than
that if you start with an empty local Maven repository, as Maven will then
download its plugins and all the required dependencies.</p>
<h2 id="prerequisites">Prerequisites</h2>
<p>Before you begin, you need to have the following tools installed on your
system:</p>
@@ -275,7 +275,7 @@ For more information on this see the <a
</ul>
<p>If adding dependencies to the poms, run mvn eclipse:eclipse again and
refresh the project in Eclipse. Debugging works as described above.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/issue-tracker.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/issue-tracker.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/issue-tracker.html
Thu Apr 25 17:28:49 2013
@@ -101,7 +101,7 @@
<tbody>
<tr>
<td><em>Bug</em></td>
-<td>Bug reports are used for cases where Sling fails not function as it should
(as defined by some documentation). If you are not certain whether the issue
you've found is actually a bug, please ask the <a href="">Sling mailing
lists</a> first for help.</td>
+<td>Bug reports are used for cases where Sling fails not function as it should
(as defined by some documentation). If you are not certain whether the issue
you've found is actually a bug, please ask the <a
href="/project-information.html#mailing-lists">Sling mailing lists</a> first
for help.</td>
</tr>
<tr>
<td><em>New Feature</em></td>
@@ -208,7 +208,7 @@
<h2 id="patches">Patches</h2>
<p>When reporting a bug, requesting a feature or propose an improvement, it is
a good thing to attach a patch to the issue. This may speed up issue processing
and helps you being recognized as a good community member leading to closer
involvement with Sling.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/logging.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/logging.html
(original)
+++ websites/staging/sling/trunk/content/documentation/development/logging.html
Thu Apr 25 17:28:49 2013
@@ -90,13 +90,13 @@
<p>Logging in Sling is supported by the
<code>org.apache.sling.commons.log</code> bundle, which is one of the first
bundles installed and started by the Sling Launcher. The
<code>org.apache.sling.commons.log</code> bundle has the following tasks:</p>
<ul>
<li>Implements the OSGi Log Service Specification and registers the
<code>LogService</code> and <code>LogReader</code> services</li>
-<li>Exports three commonly used logging APIs:
- <strong> <a href="">Simple Logging Facade for Java (SLF4J)</a>
- <br />
-</strong> <a href="http://jakarta.apache.org/commons/logging";>Apache Commons
Logging</a>
- <strong> <a href="http://logging.apache.org/log4j/index.html";>log4j</a>
- <br />
-</strong> <a
href="http://download.oracle.com/javase/6/docs/api/java/util/logging/package-summary.html";>java.util.logging</a>
(as of r1169918)</li>
+<li>Exports three commonly used logging APIs:<ul>
+<li><a href="http://www.slf4j,org";>Simple Logging Facade for Java
(SLF4J)</a></li>
+<li><a href="http://jakarta.apache.org/commons/logging";>Apache Commons
Logging</a></li>
+<li><a href="http://logging.apache.org/log4j/index.html";>log4j</a></li>
+<li><a
href="http://download.oracle.com/javase/6/docs/api/java/util/logging/package-summary.html";>java.util.logging</a>
(as of r1169918)</li>
+</ul>
+</li>
<li>Configures logging through our own implementation of the SLF4J backend
API</li>
</ul>
<h2 id="initial-configuration">Initial Configuration</h2>
@@ -159,25 +159,25 @@
<tbody>
<tr>
<td><code>org.apache.sling.commons.log.level</code></td>
-<td>String</td>
+<td><code>String</code></td>
<td><code>INFO</code></td>
<td>Sets the logging level of the loggers. This may be any of the defined
logging levels <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>,
<code>ERROR</code> and <code>FATAL</code>.</td>
</tr>
<tr>
<td><code>org.apache.sling.commons.log.file</code></td>
-<td>String</td>
+<td><code>String</code></td>
<td>undefined</td>
<td>Sets the log file to which log messages are written. If this property is
empty or missing, log messages are written to <code>System.out</code>. This
property should refer to the file name of a configured Log Writer (see below).
If no Log Writer is configured with the same file name an implicit Log Writer
configuration with default configuration is created.</td>
</tr>
<tr>
<td><code>org.apache.sling.commons.log.pattern</code></td>
-<td>String</td>
+<td><code>String</code></td>
<td>{0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}]() {3} {5}</td>
<td>The <code>java.util.MessageFormat</code> pattern to use for formatting log
messages with the root logger. This is a <code>java.util.MessageFormat</code>
pattern supporting up to six arguments: {0} The timestamp of type
<code>java.util.Date</code>, {1} the log marker, {2} the name of the current
thread, {3} the name of the logger, {4} the debug level and {5} the actual
debug message. If the log call includes a Throwable, the stacktrace is just
appended to the message regardless of the pattern.</td>
</tr>
<tr>
<td><code>org.apache.sling.commons.log.names</code></td>
-<td>String<a href=""></a></td>
+<td><code>String\[\]</code></td>
<td>--</td>
<td>A list of logger names to which this configuration applies.</td>
</tr>
@@ -268,7 +268,7 @@
<p>Log file rotation by size is specified by setting the
<code>org.apache.sling.commons.log.file.size</code> property to a plain number
or a number plus a size multiplier. The size multiplier may be any of
<code>K</code>, <code>KB</code>, <code>M</code>, <code>MB</code>,
<code>G</code>, or <code>GB</code> where the case is ignored and the meaning is
probably obvious.</p>
<p>When using Size Rotation, the
<code>org.apache.sling.commons.log.file.number</code> defines the number of old
log file generations to keep. For example to keep 5 old log files indexed by 0
through 4, set the <code>org.apache.sling.commons.log.file.number</code> to
<code>5</code> (which happens to be the default).</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/release-management.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/release-management.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/release-management.html
Thu Apr 25 17:28:49 2013
@@ -289,7 +289,7 @@ $ mvn release:prepare</p>
<li>Once the release is promoted click on <em>Repositories</em>, select the
<em>Releases</em> repository and validate that your artifacts are all
there.</li>
<li>If you're releasing bundles, you should also add them to the Sling Release
OBR (see <em>Appendix C</em>).</li>
<li>Update the news section on the website at <a
href="/news.html">news</a>.</li>
-<li>Update the download page on the website at <a href="">downloads</a> to
point to the new release.</li>
+<li>Update the download page on the website at <a
href="/downloads.cgi">downloads</a> to point to the new release.</li>
</ol>
<p>For the last two tasks, it's better to give the mirrors some time to
distribute the uploaded artifacts (one day should be fine). This ensures that
once the website (news and download page) is updated, people can actually
download the artifacts.</p>
<h2 id="update-jira">Update JIRA</h2>
@@ -426,7 +426,7 @@ $ rm the<em>module-version.jar the</em>m
<div class="codehilite"><pre><span class="n">After</span> <span
class="n">updating</span> <span class="n">the</span> <span
class="n">site</span> <span class="n">source</span> <span class="n">it</span>
<span class="n">will</span> <span class="n">generally</span> <span
class="n">take</span> <span class="n">an</span> <span class="n">hour</span>
<span class="ow">or</span> <span class="n">two</span> <span
class="k">until</span> <span class="n">the</span> <span
class="n">changes</span> <span class="n">are</span> <span
class="n">visible</span> <span class="n">on</span> <span class="n">the</span>
<span class="n">web</span><span class="o">.</span>
</pre></div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/repository-based-development.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/repository-based-development.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/repository-based-development.html
Thu Apr 25 17:28:49 2013
@@ -141,13 +141,13 @@ slingroot/prefix/workspace/item
<td>The name of the HTTP Basic Authentication Realm presented to the client to
ask for authentication credentials to access the repository.</td>
</tr>
<tr>
-<td>Non Collection Node Typee</td>
-<td><a href=""> <code>nt:file</code>, <code>nt:resource</code> </a></td>
+<td>Non Collection Node Types</td>
+<td><code>nt:file</code>, <code>nt:resource</code></td>
<td>The JCR Node Types considered being non-collection resouces by WebDAV. Any
node replying <code>true</code> to <code>Node.isNodeType()</code> for one of
the listed types is considered a non-collection resource. Otherwise the
respective node is considered a colleciton resource.</td>
</tr>
<tr>
<td>Filter Prefixes</td>
-<td><a href=""> <code>jcr</code>, <code>rep</code> </a></td>
+<td><code>jcr</code>, <code>rep</code></td>
<td>A list of namespace prefixes indicating JCR items filtered from being
reported as collection members or properties. The default list includes jcr and
rep (Jackrabbit internal namespace prefix) items. Do not modify this setting
unless you know exactly what you are doing.</td>
</tr>
<tr>
@@ -190,7 +190,7 @@ slingroot/prefix/workspace/item
<h2 id="eclipse-plugin-for-jcr">Eclipse plugin for JCR</h2>
<p>TBD</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/development/sling.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/sling.html
(original)
+++ websites/staging/sling/trunk/content/documentation/development/sling.html
Thu Apr 25 17:28:49 2013
@@ -87,9 +87,28 @@
<h1>Maven Sling Plugin</h1>
<p>The Maven Sling Plugin provides a number of goals which may be of
help while developping bundles for Sling. To run the plugin you need at least
Maven 2.x and JDK 1.5 or higher. Maven Sling Plugin provides the following
goals:</p>
-<p>| <a href="">sling:deploy</a> | Deploy a OSGi-bundle into a running Sling
instance. |
-| <a href="">sling:deploy-file</a> | Deploy a OSGi-bundle into a running Sling
instance without requiring a project descriptor file. |</p>
-<p>| <a href="">sling:install-file</a> | Install a OSGi-bundle into a running
Sling instance without requiring a project descriptor file. |</p>
+<table>
+<thead>
+<tr>
+<th>Name</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><a href="#the-deploy-goal">sling:deploy</a></td>
+<td>Deploy a OSGi-bundle into a running Sling instance.</td>
+</tr>
+<tr>
+<td><a href="#the-deploy-file-goal">sling:deploy-file</a></td>
+<td>Deploy a OSGi-bundle into a running Sling instance without requiring a
project descriptor file.</td>
+</tr>
+<tr>
+<td><a href="#the-install-file-goal">sling:install-file</a></td>
+<td>Install a OSGi-bundle into a running Sling instance without requiring a
project descriptor file.</td>
+</tr>
+</tbody>
+</table>
<h2 id="usage">Usage</h2>
<p>You should specify the version in your project's plugin configuration:</p>
<div class="codehilite"><pre><span class="nt"><project></span>
@@ -122,7 +141,6 @@
<p>For more information, see <a
href="http://maven.apache.org/guides/mini/guide-configuring-plugins.html";>"Guide
to Configuring Plug-ins"</a></p>
-<p>{anchor:deploy}</p>
<h2 id="the-deploy-goal">The <code>deploy</code> goal</h2>
<p>The <code>deploy</code> goal uploads a bundle to a Sling OSGi Bundle
Repository server implemented by the <em>sling-obr</em> bundle, which may be
located on a remote system. The plugin places an HTTP <code>POST</code> request
to the server sending the bundle file. </p>
<h3 id="use">Use</h3>
@@ -162,8 +180,7 @@
| <code>skip</code> | <code>false</code> | <code>sling.deploy.skip</code> |
Whether to skip this step even though it has been configured in the project to
be executed. The main use of this setting is preventing deployment of the
bundle to a Sling OSGi Bundle Repository server if it is known that there is
none or if such an upload is not required. |
| <code>buildDirectory</code> | <code>$\{project.build.directory</code>} | - |
The path of the file to be installed |
| <code>jarName</code> | <code>$\{project.build.finalName}.jar</code> | - |
The name of the file to be installed |
-| <code>obr</code> | - | <code>obr</code> | The URL of the running Sling
instance to which the bundle is installed. Note that this parameter is required
and has no defualt value. It must always be specified in the configuration
section or on the command line. |
-{anchor:deploy-file}</p>
+| <code>obr</code> | - | <code>obr</code> | The URL of the running Sling
instance to which the bundle is installed. Note that this parameter is required
and has no defualt value. It must always be specified in the configuration
section or on the command line. |</p>
<h2 id="the-deploy-file-goal">The <code>deploy-file</code> goal</h2>
<p>The <code>deploy-file</code> goal is equivalent to the <code>deploy</code>
goal except, that the <code>deploy-file</code> does not require a project
descriptor file while the <code>deploy</code> goal does. In other words the
<code>deploy-file</code> goal may used to upload any bundle file available to a
Sling OBR server instance.</p>
<h3 id="use_1">Use</h3>
@@ -184,7 +201,6 @@ Example: To deploy the bundle file <code
</pre></div>
-<p>{anchor:install}</p>
<h2 id="the-install-goal">The <code>install</code> goal</h2>
<p>The <code>install</code> goal uploads a bundle to a running sling instance,
which may be located on a remote system. The plugin places an HTTP
<code>POST</code> request to the sling instance sending the bundle file
together with flags indicating whether to start the bundle and what start level
to assign the bundle. It's also possible to HTTP <code>PUT</code> instead of
<code>POST</code> for WebDAV.</p>
<h3 id="use_2">Use</h3>
@@ -242,7 +258,7 @@ Example: To deploy the bundle file <code
<p>Specifying the bundle file to upload with the <code>sling.file</code>
property is required.</p>
<h3 id="configuration_3">Configuration</h3>
<p>The <code>install-file</code> supports the same configuration parameters as
the <code>install</code> goal with the exception of the <code>skip</code>
parameter which makes no sense. In addition, all parameters must be specified
on the command line by setting system properties. The
<code>bundleFileName</code> parameter specified as the <code>sling.file</code>
system property is required by the <code>install-file</code> goal.</p>
-<p>For a description of the parameters see the configuration section of the <a
href=""><code>install</code> goal</a> above.</p>
+<p>For a description of the parameters see the configuration section of the <a
href="#the-install-goal"><code>install</code> goal</a> above.</p>
<p>Example: To upload the bundle file <code>someBundle.jar</code> you might
use the goal as follows:</p>
<div class="codehilite"><pre><span class="nv">$</span> <span
class="nv">mvn</span> <span class="n">org</span><span class="o">.</span><span
class="n">apache</span><span class="o">.</span><span
class="n">sling:maven</span><span class="o">-</span><span
class="n">sling</span><span class="o">-</span><span
class="n">plugin:install</span><span class="o">-</span><span
class="n">file</span> <span class="o">-</span><span
class="n">Dsling</span><span class="o">.</span><span class="n">file</span><span
class="o">=</span><span class="n">someBundle</span><span
class="o">.</span><span class="n">jar</span>
</pre></div>
@@ -330,7 +346,7 @@ Example: To deploy the bundle file <code
| <code>skip</code> | <code>false</code> | <code>sling.validation.skip</code>
| Whether to skip the validation |
| <code>skipJson</code> | <code>false</code> |
<code>sling.validation.skipJson</code> | Whether to skip the JSON validation.
At the time, there's no difference between <code>skip</code> and
<code>skipJson</code> because only JSON files will be validated by now. |</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/getting-started/discover-sling-in-15-minutes.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/getting-started/discover-sling-in-15-minutes.html
(original)
+++
websites/staging/sling/trunk/content/documentation/getting-started/discover-sling-in-15-minutes.html
Thu Apr 25 17:28:49 2013
@@ -110,7 +110,7 @@
<p>Once you grok the basic examples of this page, we recommend studying the
<em>slingbucks</em> and <em>espblog</em> samples. Both have README files with
more info.</p>
<h2 id="prerequisites">Prerequisites</h2>
-<p>We'll start with the self-runnable jar from the Sling distribution, you
only need a Java 5 JDK. Download the latest release from the Sling <a
href="">Downloads</a> page or by clicking this link: <a
href="http://www.apache.org/dyn/closer.cgi/sling/org.apache.sling.launchpad-6-standalone.jar";>org.apache.sling.launchpad-6-standalone.jar</a>.
Alternatively you can deploy the <a
href="http://www.apache.org/dyn/closer.cgi/sling/org.apache.sling.launchpad-6.war";>Sling
Web application</a> into any decent Servlet Container such as Jetty or Tomcat
or you can <a
href="/documentation/development/getting-and-building-sling.html">build the
current source yourself</a>.</p>
+<p>We'll start with the self-runnable jar from the Sling distribution, you
only need a Java 5 JDK. Download the latest release from the Sling <a
href="/downloads.cgi">Downloads</a> page or by clicking this link: <a
href="http://www.apache.org/dyn/closer.cgi/sling/org.apache.sling.launchpad-6-standalone.jar";>org.apache.sling.launchpad-6-standalone.jar</a>.
Alternatively you can deploy the <a
href="http://www.apache.org/dyn/closer.cgi/sling/org.apache.sling.launchpad-6.war";>Sling
Web application</a> into any decent Servlet Container such as Jetty or Tomcat
or you can <a
href="/documentation/development/getting-and-building-sling.html">build the
current source yourself</a>.</p>
<p>To show the simplicity of the REST-style approach taken by Sling the
examples below will be using <a href="http://curl.haxx.se/";>cURL</a>. Any HTTP
client would do, but cURL is the easiest to document in a reproducible way.</p>
<p>A WebDAV client makes editing server-side scripts much more convenient, but
to make our examples easy to reproduce, we're using cURL below to create and
update files in the JCR repository, via the Sling WebDAV server.</p>
<h2 id="start-the-launchpad">Start the Launchpad</h2>
@@ -254,7 +254,7 @@ well as above in the <em>see also</em> s
<p>The <a
href="http://localhost:8080/content/mynode.html";>http://localhost:8080/content/mynode.html</a>,
once refreshed, now shows the blue headline and logo, and this layout also
applies to any node created with <em>sling:resourceType=foo/bar</em>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1452739 by bdelacretaz on Tue, 5 Mar 2013 11:10:43 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/the-sling-engine/architecture.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/the-sling-engine/architecture.html
(original)
+++
websites/staging/sling/trunk/content/documentation/the-sling-engine/architecture.html
Thu Apr 25 17:28:49 2013
@@ -88,12 +88,12 @@
<h1>Architecture</h1>
<p>The following is a short list of high-lights of Sling:</p>
<ul>
-<li><em><a href="">OSGi</a></em> --- The Sling application is built as a
series of OSGi bundles and makes heavy use of a number of OSGi core and
compendium services.</li>
-<li><em><a href="">Sling API</a></em> --- To implement content based Web
applications with Sling, an API has been defined, this extends the Servlet API
and provides more functionality to work on the content.</li>
-<li><em><a href="">Request Processing</a></em> --- Sling takes a unique
approach to handling requests in that a request URL is first resolved to a
resource, then based on the resource (and only the resource) it selects the
actual servlet or script to handle the request.</li>
-<li><em><a href="">Resources</a></em> --- The central mantra of Sling is the
<em>Resource</em>, which represents the resource addressed by any request URL.
It is the resource that is first resolved when handling a request. Based on the
resource, a first servlet or script is then accessed to actually handle the
request.</li>
-<li><em><a href="">Servlets and Scripts</a></em> --- Servlets and Scripts are
handled uniformly in that they are represented as resources themselves and are
accessible by a resource path.</li>
-<li><em><a href="">Launchpad</a></em> --- 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.</li>
+<li><em><a href="#osgi">OSGi</a></em> --- The Sling application is built as a
series of OSGi bundles and makes heavy use of a number of OSGi core and
compendium services.</li>
+<li><em><a href="#sling-api">Sling API</a></em> --- To implement content based
Web applications with Sling, an API has been defined, this extends the Servlet
API and provides more functionality to work on the content.</li>
+<li><em><a href="#request-processing">Request Processing</a></em> --- Sling
takes a unique approach to handling requests in that a request URL is first
resolved to a resource, then based on the resource (and only the resource) it
selects the actual servlet or script to handle the request.</li>
+<li><em><a href="#resources">Resources</a></em> --- The central mantra of
Sling is the <em>Resource</em>, which represents the resource addressed by any
request URL. It is the resource that is first resolved when handling a request.
Based on the resource, a first servlet or script is then accessed to actually
handle the request.</li>
+<li><em><a href="#servlets-and-scripts">Servlets and Scripts</a></em> ---
Servlets and Scripts are handled uniformly in that they are represented as
resources themselves and are accessible by a resource path.</li>
+<li><em><a href="#launchpad">Launchpad</a></em> --- 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.</li>
</ul>
<p>The following sections elaborate on each of these highlights.</p>
<h2 id="osgi">OSGi</h2>
@@ -141,7 +141,7 @@
<p>Optionally, PAX Web's implementation of HttpService can be used when Sling
is launched as a standalone Java Application. See the <a
href="/documentation/development/maven-launchpad-plugin.html">Maven Launchpad
Plugin</a> page for information on how to do this.</p>
<p>See <a href="/documentation/the-sling-engine/the-sling-launchpad.html">The
Sling Launchpad</a> for more information.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1436426 by ieb on Mon, 21 Jan 2013 15:41:20 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/documentation/the-sling-engine/resources.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/the-sling-engine/resources.html
(original)
+++
websites/staging/sling/trunk/content/documentation/the-sling-engine/resources.html
Thu Apr 25 17:28:49 2013
@@ -112,7 +112,7 @@
<em> Absolute Path Mapping Resource Resolution: The
<code>resolve(HttpServletRequest, String)</code> and
<code>resolve(String)</code> methods are called to apply some implementation
specific path matching algorithm to find a Resource. These methods are mainly
used to map external paths - such as path components of request URLs - to
Resources. To support creating external paths usable in an URL a third method
<code>map(String)</code> is defined, which allows for round-tripping.
</em> Absolute or Relative Path Resolution (including search path): The
<code>getResource(String path)</code> and <code>getResource(Resource base,
String path)</code> methods may be used to access a resource with an absolute
path directly. If it can't be found the path is assumed to be relative and the
search path retrieved from <code>getSearchPath()</code> is used to retrieve the
resource. This mechanism is similar to resolving a programm with the
<code>PATH</code> environment variable in your favourite operating system.
<em> Resource Enumeration: To enumerate resources and thus iterate the
resource tree, the <code>listChildren(Resource)</code> method may be used. This
method returns an <code>Iterator<Resource></code> listing all resources
whose path prefix is the path of the given Resource. This method will of course
also cross boundaries of registered <code>ResourceProvider</code> instances to
enable iterating the complete resource tree.
-</em> Resource Querying: Querying resources is currently only supported for
JCR Resources through the <code>findResources(String query, String
language)</code> and <code>queryResources(String query, String language)</code>
methods. For more information see the section on <a
href="">Querying*Resources</a> below.</p>
+</em> Resource Querying: Querying resources is currently only supported for
JCR Resources through the <code>findResources(String query, String
language)</code> and <code>queryResources(String query, String language)</code>
methods. For more information see the section on <a
href="#querying-resources">Querying Resources</a> below.</p>
<h3 id="absolute-path-mapping">Absolute Path Mapping</h3>
<p>As has been said, the absolute path mapping methods
<code>resolve(HttpServletRequest, String)</code> and
<code>resolve(String)</code> apply some implementation specific path matching
algorithm to find a Resource. The difference between the two methods is that
the former may take more properties of the <code>HttpServletRequest</code> into
account when resolving the Resoure, while the latter just has an absolute path
to work on.</p>
<p>The general algorithm of the two methods is as follows:
@@ -160,7 +160,7 @@
<h2 id="wrapdecorate-resources">Wrap/Decorate Resources</h2>
<p>The Sling API provides an easy way to wrap or decorate a resource before
returning. Details see <a
href="/documentation/the-sling-engine/wrap-or-decorate-resources.html">Wrap or
Decorate Resources</a>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1453378 by bdelacretaz on Wed, 6 Mar 2013 15:19:40 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified: websites/staging/sling/trunk/content/links.html
==============================================================================
--- websites/staging/sling/trunk/content/links.html (original)
+++ websites/staging/sling/trunk/content/links.html Thu Apr 25 17:28:49 2013
@@ -110,17 +110,19 @@
<ul>
<li><a href="http://www.slideshare.net/tag/sling";>Presentations tagged with
"sling" at slideshare</a> </li>
</ul>
-<p>The following screencasts demonstrate Day Software's CRX quickstart
product, powered by Sling:
- * <a
href="http://dev.day.com/microsling/content/blogs/main/firststeps1.html";>First
Steps with CRX Quickstart</a>
- * <a
href="http://dev.day.com/microsling/content/blogs/main/firststeps2.html";>TheServerSide.com
in 15 minutes</a></p>
+<p>The following screencasts demonstrate Day Software's CRX quickstart
product, powered by Sling:</p>
+<ul>
+<li><a
href="http://dev.day.com/microsling/content/blogs/main/firststeps1.html";>First
Steps with CRX Quickstart</a></li>
+<li><a
href="http://dev.day.com/microsling/content/blogs/main/firststeps2.html";>TheServerSide.com
in 15 minutes</a></li>
+</ul>
<h2 id="from-apachecon-eu-08">From ApacheCon EU 08</h2>
<ul>
-<li><a href="">ApacheCon EU 08 Fast Feather Track Presentation on
Sling</a></li>
-<li><a href="">JCR Meetup Presentation on Sling Architecture</a></li>
+<li><a href="/res/docs/ApacheConEU08_FFT_Sling.pdf">ApacheCon EU 08 Fast
Feather Track Presentation on Sling</a></li>
+<li><a href="/res/docs/ApacheConEU08_JCR_Meetup_Sling_Architecture.pdf">JCR
Meetup Presentation on Sling Architecture</a></li>
</ul>
<h2 id="from-apachecon-us-07">From ApacheCon US 07</h2>
<ul>
-<li><a href="">ApacheCon US 07 Fast Feather Track Presentation on
Sling</a></li>
+<li><a href="/res/docs/ApacheConUS07_FFT_Sling.pdf">ApacheCon US 07 Fast
Feather Track Presentation on Sling</a></li>
<li><a href="http://feathercast.org/?p=59";>Feathercast On Day 4 with an
interview on Sling with Felix</a></li>
</ul>
<h2 id="technology-used-by-sling">Technology used by Sling</h2>
@@ -131,7 +133,7 @@
<li><a href="http://www.osgi.org";>The OSGi Alliance</a> - The OSGi Alliance is
the specification body defining the OSGi Core and Compendium Services. These
specifications are at the center of making Sling possible.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/project-information/project-team.html
==============================================================================
--- websites/staging/sling/trunk/content/project-information/project-team.html
(original)
+++ websites/staging/sling/trunk/content/project-information/project-team.html
Thu Apr 25 17:28:49 2013
@@ -153,9 +153,9 @@
<tr>
<td>dklco</td>
<td>Dan Klco</td>
-<td></td>
+<td>Six Dimensions</td>
<td>Java Developer</td>
-<td></td>
+<td>-5</td>
</tr>
<tr>
<td>fmeschbe (*)</td>
@@ -284,7 +284,7 @@
<h2 id="contributors">Contributors</h2>
<p>There are no contributors listed for this project.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified: websites/staging/sling/trunk/content/project-information/security.html
==============================================================================
--- websites/staging/sling/trunk/content/project-information/security.html
(original)
+++ websites/staging/sling/trunk/content/project-information/security.html Thu
Apr 25 17:28:49 2013
@@ -99,13 +99,13 @@
<li>availability of patches and/or new releases</li>
</ul>
<p>should be addressed to our public users mailing list. Please see the <a
href="/project-information.html">Project Information</a> page for details of
how to subscribe.</p>
-<p>The private security mailing address is: <a
href="">mailto:[email protected]</a>.</p>
+<p>The private security mailing address is: security(at)sling.apache.org.</p>
<p>Note that all networked servers are subject to denial of service attacks,
and we cannot promise magic workarounds to generic problems (such as a client
streaming lots of data to your server, or re-requesting the same URL
repeatedly). In general our philosophy is to avoid any attacks which can cause
the server to consume resources in a non-linear relationship to the size of
inputs.</p>
<p>For more information on handling security issues at the Apache Software
Foundation please refer to the <a href="http://www.apache.org/security/";>ASF
Security Team</a> page.</p>
<h1 id="errors-and-omissions">Errors and omissions</h1>
-<p>Please report any errors or omissions to <a
href="">mailto:[email protected]</a>.</p>
+<p>Please report any errors or omissions to security(at)sling.apache.org.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1475804 by dklco on Thu, 25 Apr 2013 14:45:50 +0000
+ Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Added: websites/staging/sling/trunk/content/res/docs/ApacheConEU08_FFT_Sling.pdf
==============================================================================
Binary file - no diff available.
Propchange:
websites/staging/sling/trunk/content/res/docs/ApacheConEU08_FFT_Sling.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added:
websites/staging/sling/trunk/content/res/docs/ApacheConEU08_JCR_Meetup_Sling_Architecture.pdf
==============================================================================
Binary file - no diff available.
Propchange:
websites/staging/sling/trunk/content/res/docs/ApacheConEU08_JCR_Meetup_Sling_Architecture.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added: websites/staging/sling/trunk/content/res/docs/ApacheConUS07_FFT_Sling.pdf
==============================================================================
Binary file - no diff available.
Propchange:
websites/staging/sling/trunk/content/res/docs/ApacheConUS07_FFT_Sling.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
