Author: buildbot
Date: Wed Mar 6 15:28:59 2013
New Revision: 853301
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles.html
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
websites/staging/sling/trunk/content/documentation/development/sling-testing-tools.html
websites/staging/sling/trunk/content/documentation/the-sling-engine/dispatching-requests.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 6 15:28:59 2013
@@ -1 +1 @@
-1453379
+1453385
Modified: websites/staging/sling/trunk/content/documentation/bundles.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/bundles.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles.html Wed Mar 6
15:28:59 2013
@@ -109,7 +109,7 @@
</ul>
<h2 id="misc">Misc</h2>
<ul>
-<li><a href="">Commons Thread Pools</a></li>
+<li><a
href="/documentation/bundles/apache-sling-commons-thread-pool.html">Commons
Thread Pools</a></li>
<li><a href="/documentation/bundles/commons-html-utilities.html">Commons HTML
Utilities</a></li>
<li><a href="/documentation/bundles/mime-type-support-commons-mime.html">MIME
Type Support (commons.mime)</a></li>
<li><a
href="/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.html">Output
Rewriting Pipelines (org.apache.sling.rewriter)</a></li>
@@ -119,7 +119,7 @@
<li><a href="/documentation/bundles/web-console-extensions.html">Web Console
Extensions (org.apache.sling.extensions.webconsolebranding,
org.apache.sling.extensions.webconsolesecurityprovider)</a></li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1352784 by fmeschbe on Fri, 22 Jun 2012 07:10:21 +0000
+ Rev. 1453385 by bdelacretaz on Wed, 6 Mar 2013 15:28:50 +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
Wed Mar 6 15:28:59 2013
@@ -86,7 +86,7 @@
<h1>JCR Installer Provider</h1>
- <p>The JCR installer provider scans the JCR repository for artifacts and
provides them to the <a href="">OSGI installer</a>.</p>
+ <p>The JCR installer provider scans the JCR repository for artifacts and
provides them to the <a href="/documentation/bundles/osgi-installer.html">OSGI
installer</a>.</p>
<h2 id="configuration-and-scanning">Configuration and Scanning</h2>
<p>The JCR installer provider can be configured with weighted paths which are
scanned. By default, the installer scans in <em>/apps</em> and <em>/libs</em>
where artifacts found in <em>/apps</em> get a higher priority. The installer
does a deep scan and uses a regular expression to detect folders containing
artifacts to be installed. By default, artifacts from within a folder named
<em>install</em> are provided to the OSGi installer.</p>
<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>
@@ -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. 1341376 by fmeschbe on Tue, 22 May 2012 09:41:06 +0000
+ Rev. 1453385 by bdelacretaz on Wed, 6 Mar 2013 15:28:50 +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-testing-tools.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/sling-testing-tools.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/sling-testing-tools.html
Wed Mar 6 15:28:59 2013
@@ -95,7 +95,7 @@
<p>This page describes those tools, and points to the bundles that implement
them.</p>
<p>The <a href="">testing/samples/integration-tests</a> module demonstrates
these tools, and is also meant as a sample project to show how to run
integration tests for Sling-based applications.</p>
<p>The main Sling integration tests at <a
href="">launchpad/integration-tests</a> were created before this testing
framework, and do not use it yet (as of March 2011). The new testing tools are
simpler to use, but the "old" tests (all 400 of them as I write this) fulfill
their validation role for testing Sling itself, there's no real need to modify
them to use the new tools.</p>
-<p>See also <a href="">SLINGxSITE:Testing Sling-based applications</a> which
discusses testing in general.</p>
+<p>See also <a
href="/documentation/tutorials-how-tos/testing-sling-based-applications.html">Testing
Sling-based applications</a> which discusses testing in general.</p>
<h1 id="server-side-junit-tests-contributed-by-bundles">Server-side JUnit
tests contributed by bundles</h1>
<p>The services provided by the <a href="">org.apache.sling.junit.core</a>
bundle allow bundles to register JUnit tests, which are executed server-side by
the JUnitServlet registered by default at <code>/system/sling/junit</code>.
This bundle is not dependent on Sling, it should work in other OSGi
environments.</p>
<p>{warning:title=JUnit servlet security}
@@ -162,7 +162,7 @@ For tighter integration with Sling, the
<p>The <a href="">SlingRemoteExecutionRule</a> is a JUnit Rule that allows
tests to be executed remotely in a Sling instance from an IDE, assuming the
test is available on both sides.</p>
<p>The <a href="">ExampleRemoteTest</a> class demonstrates this. To run it
from your IDE, set the <code>sling.remote.test.url</code> in the IDE to the URL
of the JUnitServlet, like http://localhost:8080/system/sling/junit for
example.</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. 1453385 by bdelacretaz on Wed, 6 Mar 2013 15:28:50 +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/dispatching-requests.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/the-sling-engine/dispatching-requests.html
(original)
+++
websites/staging/sling/trunk/content/documentation/the-sling-engine/dispatching-requests.html
Wed Mar 6 15:28:59 2013
@@ -112,7 +112,7 @@ If anonymous is allowed, continue with s
<em> Wraps the <code>HttpServletRequest</code> and the
<code>HttpServletResponse</code> into the <code>SlingHttpServletRequest</code>
and the <code>SlingHttpServletResponse</code>
</em> Checks if Sling is ready for processing the request (checks at the
moment for an existing ResourceResolverFactory service, a ServletResolver
service and a MimeTypeService)
<em> Create the ResourceResolver based on the Session (by default creates a
<code>JcrResourceResolver2</code>)
-</em> Locate the <a href="">Resource</a> on the basis of the request by
calling <code>ResourceResovler.resolve</code> through
<code>RequestData.initResource</code> (see also [URL decomposition])
+</em> Locate the <a
href="/documentation/the-sling-engine/resources.html">Resource</a> on the basis
of the request by calling <code>ResourceResovler.resolve</code> through
<code>RequestData.initResource</code> (see also [URL decomposition])
* Locate the servlet or script (see <a
href="/documentation/the-sling-engine/servlets.html">Servlets</a>) by calling
<code>ServletResolver.resolveServlet</code> through
<code>RequestData.initServlet</code></p>
<h3 id="step-7">Step 7</h3>
<p>After this setup, the request level filters are called (the ones registered
as <code>javax.servlet.Filter</code> with the property
<code>filter.scope=request</code>, see <a
href="/documentation/the-sling-engine/filters.html">Filters</a> for details).
@@ -190,7 +190,7 @@ If any called filter doesn't call <code>
<p>Constants are defined in the
<code>org.apache.sling.api.SlingConstants</code> class for these request
attributes.</p>
<p><em>Note:</em> These request attributes are not set if the servlet or
script is called to handle the request or as a result of
<code>RequestDispatcher.forward</code>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1345726 by fmeschbe on Sun, 3 Jun 2012 17:57:55 +0000
+ Rev. 1453385 by bdelacretaz on Wed, 6 Mar 2013 15:28:50 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
