Author: buildbot
Date: Wed Aug 30 11:41:25 2017
New Revision: 1017475
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
websites/staging/sling/trunk/content/documentation/tutorials-how-tos/46-line-blog.html
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/groovy-support.html
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.html
websites/staging/sling/trunk/content/site/groovy-support.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Aug 30 11:41:25 2017
@@ -1 +1 @@
-1806469
+1806688
Modified:
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/discovery-api-and-impl.html
Wed Aug 30 11:41:25 2017
@@ -391,12 +391,12 @@ A topology connector is by definition al
can be structured in an arbitrary way (chain, star, tree, etc) with the only
important point to note here that
since changes in the topology propagate through these topology connectors they
have a certain delay (namely
the configured heartbeatInterval per hop).</p>
-<p>Topology connectors are configured at <a
href="http://localhost:8888/system/console/configMgr/org.apache.sling.discovery.impl.Config";>/system/console/configMgr/org.apache.sling.discovery.impl.Config</a>.
+<p>Topology connectors are configured at <a
href="http://localhost:8080/system/console/configMgr/org.apache.sling.discovery.impl.Config";>/system/console/configMgr/org.apache.sling.discovery.impl.Config</a>.
They use the same interval and timeout as the repository heartbeats
(heartbeatInterval and heartbeatTimeout).</p>
<h3 id="webconsole">WebConsole<a class="headerlink" href="#webconsole"
title="Permanent link">¶</a></h3>
-<p>A Felix WebConsole plugin at <a
href="http://localhost:8888/system/console/topology";>/system/console/topology</a>
provides a (read-only) overview of the topology.</p>
+<p>A Felix WebConsole plugin at <a
href="http://localhost:8080/system/console/topology";>/system/console/topology</a>
provides a (read-only) overview of the topology.</p>
<h3 id="configuration">Configuration<a class="headerlink"
href="#configuration" title="Permanent link">¶</a></h3>
-<p>The following properties can be configured (at <a
href="http://localhost:8888/system/console/configMgr/org.apache.sling.discovery.impl.Config";>/system/console/configMgr/org.apache.sling.discovery.impl.Config</a>):</p>
+<p>The following properties can be configured (at <a
href="http://localhost:8080/system/console/configMgr/org.apache.sling.discovery.impl.Config";>/system/console/configMgr/org.apache.sling.discovery.impl.Config</a>):</p>
<ul>
<li>
<p>heartbeatInterval: the time in seconds between two heartbeats (both
cluster-internal and for HTTP-connectors). Default
@@ -505,7 +505,7 @@ cross-cluster topology announcements (vi
<p>This is the base bundle solely used by discovery.impl and discovery.oak and
contains exactly the mentioned
properties and announcement handling.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1784944 by stefanegli on Wed, 1 Mar 2017 14:01:53 +0000
+ Rev. 1806688 by rombert on Wed, 30 Aug 2017 11:40:57 +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 Aug 30 11:41:25 2017
@@ -143,21 +143,21 @@ As JCR properties do not support all Jav
<p>We'll use the <a
href="http://www.knopflerfish.org/releases/2.0.5/jars/desktop_awt/desktop_awt_all-2.0.0.jar";>Knopflerfish
Desktop</a> bundle for this example, it is convenient as it displays a
graphical user interface when started.</p>
<p>We use <code>curl</code> to create content, to make it easy to reproduce
the example by copying and pasting the <code>curl</code> commands. Any other
way to create content in the repository will work, of course.</p>
<p>By default, JCRInstall picks up bundles found in folders named
<em>install</em> under <code>/libs</code> and <code>/apps</code>, so we start
by creating such a folder:</p>
-<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">X</span> <span class="n">MKCOL</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">admin</span><span class="p">:</span><span class="n">admin</span><span
class="p">@</span><span class="n">localhost</span><span
class="p">:</span>8888<span class="o">/</span><span class="n">apps</span><span
class="o">/</span><span class="n">jcrtest</span>
-<span class="n">curl</span> <span class="o">-</span><span class="n">X</span>
<span class="n">MKCOL</span> <span class="n">http</span><span
class="p">:</span><span class="o">//</span><span class="n">admin</span><span
class="p">:</span><span class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span class="n">install</span>
+<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">X</span> <span class="n">MKCOL</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">admin</span><span class="p">:</span><span class="n">admin</span><span
class="p">@</span><span class="n">localhost</span><span
class="p">:</span>8080<span class="o">/</span><span class="n">apps</span><span
class="o">/</span><span class="n">jcrtest</span>
+<span class="n">curl</span> <span class="o">-</span><span class="n">X</span>
<span class="n">MKCOL</span> <span class="n">http</span><span
class="p">:</span><span class="o">//</span><span class="n">admin</span><span
class="p">:</span><span class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span class="n">install</span>
</pre></div>
<p>And we copy the bundle to install in that folder (a backslash in command
lines means <em>continued on next line</em>):</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">T</span> <span
class="n">desktop_awt_all</span><span class="o">-</span>2<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span> <span class="o">\</span>
- <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">desktop_awt_all</span><span class="o">-</span>2<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span>
+ <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">desktop_awt_all</span><span class="o">-</span>2<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span>
</pre></div>
<p>That's it. After 2-3 seconds, the bundle should be picked up by JCRInstall,
installed and started. If this works you'll see a small <em>Knopflerfish
Desktop</em> window on your desktop, and Sling's OSGi console can of course be
used to check the details.</p>
<p>Removing the bundle from the repository will cause it to be uninstalled,
so:</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">X</span> <span class="n">DELETE</span> <span
class="o">\</span>
- <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">desktop_awt_all</span><span class="o">-</span>2<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span>
+ <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">desktop_awt_all</span><span class="o">-</span>2<span
class="p">.</span>0<span class="p">.</span>0<span class="p">.</span><span
class="n">jar</span>
</pre></div>
@@ -168,13 +168,13 @@ As JCR properties do not support all Jav
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">\</span>
<span class="o">-</span><span class="n">F</span> "<span
class="n">jcr</span><span class="p">:</span><span
class="n">primaryType</span><span class="p">=</span><span
class="n">sling</span><span class="p">:</span><span
class="n">OsgiConfig</span>" <span class="o">\</span>
<span class="o">-</span><span class="n">F</span> <span
class="n">foo</span><span class="p">=</span><span class="n">bar</span> <span
class="o">-</span><span class="n">F</span> <span class="n">works</span><span
class="p">=</span><span class="n">yes</span> <span class="o">\</span>
- <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
+ <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
</pre></div>
<p>And verify the contents of our config node:</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">\</span>
- <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span><span class="p">.</span><span
class="n">json</span>
+ <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span><span class="p">.</span><span
class="n">json</span>
</pre></div>
@@ -185,7 +185,7 @@ As JCR properties do not support all Jav
</pre></div>
-<p>At this point, JCRInstall should have picked up our new config and
installed it. The logs would confirm that, but we can also use the OSGi
console's config status page (http://localhost:8888/system/console/config) to
check it. That page should now contain:</p>
+<p>At this point, JCRInstall should have picked up our new config and
installed it. The logs would confirm that, but we can also use the OSGi
console's config status page (http://localhost:8080/system/console/config) to
check it. That page should now contain:</p>
<div class="codehilite"><pre><span class="n">PID</span><span
class="p">=</span><span class="n">some</span><span class="p">.</span><span
class="n">config</span><span class="p">.</span><span class="n">pid</span>
<span class="n">BundleLocation</span><span class="p">=</span><span
class="n">Unbound</span>
<span class="n">_jcr_config_path</span><span class="p">=</span><span
class="n">jcrinstall</span><span class="p">:</span><span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
@@ -199,7 +199,7 @@ As JCR properties do not support all Jav
<p>Let's try modifying the configuration parameters:</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">\</span>
<span class="o">-</span><span class="n">F</span> <span
class="n">works</span><span class="p">=</span><span class="n">updated</span>
<span class="o">-</span><span class="n">F</span> <span
class="n">even</span><span class="p">=</span><span class="n">more</span> <span
class="o">\</span>
- <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
+ <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
</pre></div>
@@ -216,7 +216,7 @@ As JCR properties do not support all Jav
<p>We can now delete the configuration node:</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">X</span> <span class="n">DELETE</span> <span
class="o">\</span>
- <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
+ <span class="n">http</span><span class="p">:</span><span
class="o">//</span><span class="n">admin</span><span class="p">:</span><span
class="n">admin</span><span class="p">@</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">apps</span><span class="o">/</span><span
class="n">jcrtest</span><span class="o">/</span><span
class="n">install</span><span class="o">/</span><span
class="n">some</span><span class="p">.</span><span class="n">config</span><span
class="p">.</span><span class="n">pid</span>
</pre></div>
@@ -234,7 +234,7 @@ As JCR properties do not support all Jav
<li>JCR installer provider (<a
href="http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr";>org.apache.sling.installer.provider.jcr</a>)</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1763693 by kwin on Fri, 7 Oct 2016 08:04:16 +0000
+ Rev. 1806688 by rombert on Wed, 30 Aug 2017 11:40:57 +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/org-apache-sling-junit-bundles.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
(original)
+++
websites/staging/sling/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.html
Wed Aug 30 11:41:25 2017
@@ -345,7 +345,7 @@ classes which are used only on the clien
</table>
<p>The provisioning of an appropriate instance can be done with the <a
href="/documentation/development/slingstart.html">slingstart-maven-plugin</a>.
An example for that is given at <a
href="https://svn.apache.org/viewvc/sling/trunk/testing/samples/module-with-it";><code>testing/samples/module-with-it</code></a>.
Since <code>slingstart-maven-plugin</code> 1.5.0 it is possible to bootstrap a
Sling Server from a <code>model.txt</code> below
<code>src/test/provisioning</code> independent of the packaging (see <a
href="https://issues.apache.org/jira/browse/SLING-6068";>SLING-6068</a>).</p>
<h4 id="launchpadcustomizer">LaunchpadCustomizer<a class="headerlink"
href="#launchpadcustomizer" title="Permanent link">¶</a></h4>
-<p>The <em><a
href="https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java";><code>LaunchpadCustomizer.java</code></a></em>
only verifies that a Sling instance is ready at a given port and configures
the <code>ClientSideTeleporter</code> to deploy to
<code>http://localhost:8888</code> with the credentials
<code>admin</code>:<code>admin</code>. <code>LaunchpadCustomizer</code> uses
the <code>HttpTestBase</code> therefore some parameters are customizable
through system properties. There is no bootstrapping of an instance done here,
so this must be done separately!</p>
+<p>The <em><a
href="https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java";><code>LaunchpadCustomizer.java</code></a></em>
only verifies that a Sling instance is ready at a given port and configures
the <code>ClientSideTeleporter</code> to deploy to
<code>http://localhost:8080</code> with the credentials
<code>admin</code>:<code>admin</code>. <code>LaunchpadCustomizer</code> uses
the <code>HttpTestBase</code> therefore some parameters are customizable
through system properties. There is no bootstrapping of an instance done here,
so this must be done separately!</p>
<h4 id="bwit_teleportercustomizer">BWIT_TeleporterCustomizer<a
class="headerlink" href="#bwit_teleportercustomizer" title="Permanent
link">¶</a></h4>
<p>The <em><a
href="http://svn.apache.org/viewvc/sling/trunk/testing/samples/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java";><code>BWIT_TeleporterCustomizer.java</code></a></em>
relies on <code>SlingTestBase</code> to set the server's base url and
credentials. Additionally the test bundle is adjusted so that the API is not
included in it (but rather referenced from another bundle). The bootstrapping
of the Sling instance is tweaked through system properties which are desribed
<a
href="http://labs.6dglobal.com/blog/2013-06-05/creating-integration-tests-apache-sling/";>here</a>
and implicitly done by the customizer itself.</p>
<p>Those should give you an overview on what can be done with a customizer and
decide whether you need to write your own one or using the default customizer
is just enough.</p>
@@ -393,7 +393,7 @@ same request again. </p>
but using the newer <code>TeleporterRule</code> described above is much
simpler. As a result, this bundle
should only be needed for existing tests that were written using its
mechanisms. </p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1784175 by kwin on Thu, 23 Feb 2017 16:50:05 +0000
+ Rev. 1806688 by rombert on Wed, 30 Aug 2017 11:40:57 +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/tutorials-how-tos/46-line-blog.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/tutorials-how-tos/46-line-blog.html
(original)
+++
websites/staging/sling/trunk/content/documentation/tutorials-how-tos/46-line-blog.html
Wed Aug 30 11:41:25 2017
@@ -121,9 +121,9 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="audience">Audience<a class="headerlink" href="#audience"
title="Permanent link">¶</a></h2>
<p>Although this is a simple sample, it requires some custom settings to work.
If you're just starting with Sling, <a
href="/documentation/getting-started/discover-sling-in-15-minutes.html">Discover
Sling in 15 minutes</a> might be a better choice.</p>
<h2 id="step-0-start-configure-and-login-to-sling">Step 0: Start, configure
and login to Sling<a class="headerlink"
href="#step-0-start-configure-and-login-to-sling" title="Permanent
link">¶</a></h2>
-<p>See <a
href="/documentation/development/getting-and-building-sling.html">Getting and
Building Sling</a> for how to start Sling. Start it on port 8888 for the below
links to work.</p>
-<p>For this sample we need the optional
<em>org.apache.sling.samples.path-based.rtp</em> bundle, if it's not present in
the <a href="http://localhost:8888/system/console/bundles";>OSGi console</a>,
install and start it. That bundle is not released yet so you might need to
build it yourself, from its <a
href="http://svn.apache.org/repos/asf/sling/trunk/samples/path-based-rtp";>source</a>.
The bundle must then appear in the <a
href="http://localhost:8888/system/console/bundles";>OSGI console's list of
bundles</a>, with name = <em>org.apache.sling.samples.path-based.rtp</em> and
status = <em>Active</em>.</p>
-<p>Then, login using <a
href="http://localhost:8888/?sling:authRequestLogin=1";>http://localhost:8888/?sling:authRequestLogin=1</a>
which should prompt you for a username and password, use <em>admin</em> and
<em>admin</em>. Once that's done, <a
href="http://localhost:8888/index.html";>http://localhost:8888/index.html</a>
should say <em>You are currently logged in as user </em>admin<em> to workspace
</em>default**.</p>
+<p>See <a
href="/documentation/development/getting-and-building-sling.html">Getting and
Building Sling</a> for how to start Sling. Start it on port 8080 for the below
links to work.</p>
+<p>For this sample we need the optional
<em>org.apache.sling.samples.path-based.rtp</em> bundle, if it's not present in
the <a href="http://localhost:8080/system/console/bundles";>OSGi console</a>,
install and start it. That bundle is not released yet so you might need to
build it yourself, from its <a
href="http://svn.apache.org/repos/asf/sling/trunk/samples/path-based-rtp";>source</a>.
The bundle must then appear in the <a
href="http://localhost:8080/system/console/bundles";>OSGI console's list of
bundles</a>, with name = <em>org.apache.sling.samples.path-based.rtp</em> and
status = <em>Active</em>.</p>
+<p>Then, login using <a
href="http://localhost:8080/?sling:authRequestLogin=1";>http://localhost:8080/?sling:authRequestLogin=1</a>
which should prompt you for a username and password, use <em>admin</em> and
<em>admin</em>. Once that's done, <a
href="http://localhost:8080/index.html";>http://localhost:8080/index.html</a>
should say <em>You are currently logged in as user </em>admin<em> to workspace
</em>default**.</p>
<h2 id="step-1-creating-content">Step 1: Creating content<a class="headerlink"
href="#step-1-creating-content" title="Permanent link">¶</a></h2>
<p>The easiest way to create content in Sling is to use an HTTP POST request,
let's use a simple HTML form:</p>
<div class="codehilite"><pre><span class="nt"><html></span>
@@ -154,7 +154,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>That's two input fields, a submit button and a hidden field that tells
Sling what to do after the POST (in this case: redirect to the html view of the
node that was just created).</p>
-<p>To test the form, start Sling and save the above script as <sup
id="fnref:esp"><a class="footnote-ref" href="#fn:esp"
rel="footnote">1</a></sup> in the Sling repository - a WebDAV mount is the
easiest way to do that. Browsing to <a
href="http://localhost:8888/content/blog/*.html";>http://localhost:8888/content/blog/*.html</a>
<sup id="fnref:port"><a class="footnote-ref" href="#fn:port"
rel="footnote">2</a></sup> should display the above form.</p>
+<p>To test the form, start Sling and save the above script as <sup
id="fnref:esp"><a class="footnote-ref" href="#fn:esp"
rel="footnote">1</a></sup> in the Sling repository - a WebDAV mount is the
easiest way to do that. Browsing to <a
href="http://localhost:8080/content/blog/*.html";>http://localhost:8080/content/blog/*.html</a>
<sup id="fnref:port"><a class="footnote-ref" href="#fn:port"
rel="footnote">2</a></sup> should display the above form.</p>
<p>Input some data (using "foo" for the title, for the sake of our examples
below), save the form, and Sling should display the form again, using the URL
of the node that was just created.</p>
<div class="note">
If you get an error saying _javax.jcr.AccessDeniedException: ...not allowed to
add or modify item_ it means that you are not logged in as user _admin_. See
instructions above for logging in.
@@ -162,7 +162,7 @@ If you get an error saying _javax.jcr.Ac
<p>At this point you're probably looking at an empty form with an URL ending
in <em>foo</em>, if you used that for the title. Or <em>foo_0</em> or
<em>foo_1</em> if other _foo_s already existed. Don't worry about not seeing
your content, we'll fix that right away.</p>
<h2 id="step-2-wheres-my-content">Step 2: Where's my content?<a
class="headerlink" href="#step-2-wheres-my-content" title="Permanent
link">¶</a></h2>
-<p>To verify that our content has been created, we can have a look at the JSON
data at <a
href="http://localhost:8888/content/blog/foo.tidy.json";>http://localhost:8888/content/blog/foo.tidy.json</a>,
which should display our new node's values:</p>
+<p>To verify that our content has been created, we can have a look at the JSON
data at <a
href="http://localhost:8080/content/blog/foo.tidy.json";>http://localhost:8080/content/blog/foo.tidy.json</a>,
which should display our new node's values:</p>
<div class="codehilite"><pre><span class="p">{</span>
"<span class="n">jcr</span><span class="p">:</span><span
class="n">primaryType</span>"<span class="p">:</span> "<span
class="n">nt</span><span class="p">:</span><span
class="n">unstructured</span>"<span class="p">,</span>
"<span class="n">text</span>"<span class="p">:</span> "<span
class="n">This</span> <span class="n">is</span> <span class="n">the</span>
<span class="n">foo</span> <span class="n">text</span>"<span
class="p">,</span>
@@ -185,7 +185,7 @@ If you get an error saying _javax.jcr.Ac
</pre></div>
-<p>Reloading the form at
<code>http://localhost:8888/content/blog/*.html</code> and creating a new post
should now redirect to an editable version of the post, with the form fields
correctly initialized.</p>
+<p>Reloading the form at
<code>http://localhost:8080/content/blog/*.html</code> and creating a new post
should now redirect to an editable version of the post, with the form fields
correctly initialized.</p>
<p>We can now create and edit posts; let's add some navigation, using more of
the <em>sling.js</em> functionality. </p>
<h2 id="step-3-navigation">Step 3: Navigation<a class="headerlink"
href="#step-3-navigation" title="Permanent link">¶</a></h2>
<p>The <em>sling.js</em> library provides utilities to access and manipulate
content. For our blog, we'll use the <code>getContent(path)</code> method to
list the siblings of the current node.</p>
@@ -233,12 +233,12 @@ If you get an error saying _javax.jcr.Ac
<p>ESP is Sling's server-side javascript language <a
class="footnote-backref" href="#fnref:esp" rev="footnote" title="Jump back to
footnote 1 in the text">↩</a></p>
</li>
<li id="fn:port">
-<p>This assumes your instance of Sling is running on port 8888. If that's not
the case, adjust the example URLs accordingly. <a class="footnote-backref"
href="#fnref:port" rev="footnote" title="Jump back to footnote 2 in the
text">↩</a></p>
+<p>This assumes your instance of Sling is running on port 8080. If that's not
the case, adjust the example URLs accordingly. <a class="footnote-backref"
href="#fnref:port" rev="footnote" title="Jump back to footnote 2 in the
text">↩</a></p>
</li>
</ol>
</div>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1464512 by bdelacretaz on Thu, 4 Apr 2013 13:03:31 +0000
+ Rev. 1806688 by rombert on Wed, 30 Aug 2017 11:40:57 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/groovy-support.html
==============================================================================
---
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/groovy-support.html
(original)
+++
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/groovy-support.html
Wed Aug 30 11:41:25 2017
@@ -124,7 +124,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>Currently the Groovy team is working hard towards the 1.6 release and many
things are in flux, which is really great.</p>
<p>So, on 11. Dec. 2008 Paul King of the Groovy Team has deployed a <a
href="">first RC1 Snapshot of Groovy 1.6</a> which contains all the required
OSGi bundle manifest headers as well das the JSR-233 <code>ScriptEngine</code>
to use the <code>groovy-all.jar</code> unmodified with Sling. So just go ahead,
grab the Groovy-All 1.6 RC 1 SNAPSHOT deploy it into your Sling instance and
enjoy the fun of Groovy.</p>
<p>If you want to be on verge of development, you might want to go for Groovy
1.7: The second SNAPSHOT of beta-1 also contains the required headers and
classes and may as well be used unmodified in Sling. You may download it here:
<code>[groovy-all-1.7-beta-1-20081210.120632-2.jar]()</code>.</p>
-<p>To deploy the bundle go to the Bundles page, for example at
http://localhost:8888/system/console/bundles of the Apache Felix Web Console
select the bundle file to upload, check the <em>Start</em> check box and click
<em>Install or Update</em> button.</p>
+<p>To deploy the bundle go to the Bundles page, for example at
http://localhost:8080/system/console/bundles of the Apache Felix Web Console
select the bundle file to upload, check the <em>Start</em> check box and click
<em>Install or Update</em> button.</p>
<p>You may check, whether the Groovy ScriptEngine has been "accepted" by
Sling, by going to the Script Engines page of the Apache Felix Web Console. You
should see the entry for Groovy there, somthing like this:</p>
<div class="codehilite"><pre><span class="n">Groovy</span> <span
class="n">Scripting</span> <span class="n">Engine</span><span
class="p">,</span> 2<span class="p">.</span>0
<span class="n">Language</span> <span class="n">Groovy</span><span
class="p">,</span>
@@ -145,18 +145,18 @@ println "You requested the Resource
</pre></div>
-<p>and upload it to the repository as <code>/apps/nt/folder/GET.groovy</code>
using your favourite WebDAV client or use curl to upload the file (assuming
Sling is running on localhost:8888) :</p>
-<div class="codehilite"><pre>$ <span class="n">curl</span> <span
class="o">-</span><span class="n">u</span> <span class="n">admin</span><span
class="p">:</span><span class="n">admin</span> <span class="o">-</span><span
class="n">FGET</span><span class="p">.</span><span class="n">groovy</span><span
class="p">=@</span><span class="n">GET</span><span class="p">.</span><span
class="n">groovy</span> <span class="o">-</span><span class="n">F</span><span
class="p">.</span><span class="o">./</span><span class="p">.</span><span
class="o">./</span><span class="n">nt</span><span class="o">/</span><span
class="n">jcr</span><span class="p">:</span><span
class="n">primaryType</span><span class="p">=</span><span
class="n">sling</span><span class="p">:</span><span class="n">Folder</span>
<span class="n">http</span><span class="p">:</span><span
class="n">host</span><span class="p">:</span>8888<span class="o">/</span><span
class="n">apps</span><span class="o">/</span><span class="n">nt</span><span cl
ass="o">/</span><span class="n">folder</span>
+<p>and upload it to the repository as <code>/apps/nt/folder/GET.groovy</code>
using your favourite WebDAV client or use curl to upload the file (assuming
Sling is running on localhost:8080) :</p>
+<div class="codehilite"><pre>$ <span class="n">curl</span> <span
class="o">-</span><span class="n">u</span> <span class="n">admin</span><span
class="p">:</span><span class="n">admin</span> <span class="o">-</span><span
class="n">FGET</span><span class="p">.</span><span class="n">groovy</span><span
class="p">=@</span><span class="n">GET</span><span class="p">.</span><span
class="n">groovy</span> <span class="o">-</span><span class="n">F</span><span
class="p">.</span><span class="o">./</span><span class="p">.</span><span
class="o">./</span><span class="n">nt</span><span class="o">/</span><span
class="n">jcr</span><span class="p">:</span><span
class="n">primaryType</span><span class="p">=</span><span
class="n">sling</span><span class="p">:</span><span class="n">Folder</span>
<span class="n">http</span><span class="p">:</span><span
class="n">host</span><span class="p">:</span>8080<span class="o">/</span><span
class="n">apps</span><span class="o">/</span><span class="n">nt</span><span cl
ass="o">/</span><span class="n">folder</span>
</pre></div>
<p>To test it create a <code>/sample</code> <code>nt:Folder</code> node using
your favourite WebDAV client or use curl again:</p>
-<div class="codehilite"><pre>$ <span class="n">curl</span> <span
class="o">-</span><span class="n">u</span> <span class="n">admin</span><span
class="p">:</span><span class="n">admin</span> <span class="o">-</span><span
class="n">Fjcr</span><span class="p">:</span><span
class="n">primaryType</span><span class="p">=</span><span
class="n">nt</span><span class="p">:</span><span class="n">folder</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">localhost</span><span class="p">:</span>8888<span class="o">/</span>
+<div class="codehilite"><pre>$ <span class="n">curl</span> <span
class="o">-</span><span class="n">u</span> <span class="n">admin</span><span
class="p">:</span><span class="n">admin</span> <span class="o">-</span><span
class="n">Fjcr</span><span class="p">:</span><span
class="n">primaryType</span><span class="p">=</span><span
class="n">nt</span><span class="p">:</span><span class="n">folder</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">localhost</span><span class="p">:</span>8080<span class="o">/</span>
</pre></div>
<p>Finally, request the <code>/sample</code> node using your favourite Browser
or use curl again:</p>
-<div class="codehilite"><pre>$ <span class="n">curl</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">localhost</span><span class="p">:</span>8888<span
class="o">/</span><span class="n">sample</span>
+<div class="codehilite"><pre>$ <span class="n">curl</span> <span
class="n">http</span><span class="p">:</span><span class="o">//</span><span
class="n">localhost</span><span class="p">:</span>8080<span
class="o">/</span><span class="n">sample</span>
<span class="n">Hello</span> <span class="n">World</span> !
<span class="n">This</span> <span class="n">is</span> <span
class="n">Groovy</span> <span class="n">Speaking</span>
<span class="n">You</span> <span class="n">requested</span> <span
class="n">Resource</span> <span class="n">JcrNodeResource</span><span
class="p">,</span> <span class="n">type</span><span class="p">=</span><span
class="n">nt</span><span class="p">:</span><span class="n">folder</span><span
class="p">,</span> <span class="n">path</span><span class="p">=</span><span
class="o">/</span><span class="n">sample</span> <span class="p">(</span><span
class="n">yes</span><span class="p">,</span> <span class="n">this</span> <span
class="n">is</span> <span class="n">a</span> <span
class="n">GString</span><span class="p">)</span>
@@ -170,7 +170,7 @@ println "You requested the Resource
<li><a href="">Groovy in Apache Sling</a> -- Thread on adding the
<code>DynamicImport-Package</code> header to the Groovy bundle manifest.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1499238 by fmeschbe on Wed, 3 Jul 2013 07:39:54 +0000
+ Rev. 1806688 by rombert on Wed, 30 Aug 2017 11:40:57 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified:
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.html
==============================================================================
---
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.html
(original)
+++
websites/staging/sling/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.html
Wed Aug 30 11:41:25 2017
@@ -123,7 +123,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>The source code is found in the <a
href="http://svn.apache.org/repos/asf/incubator/sling/trunk/contrib/scripting/xproc";>contrib/scripting/xproc</a>
module.</p>
<h2 id="how-to-install">How to Install<a class="headerlink"
href="#how-to-install" title="Permanent link">¶</a></h2>
<p>Install the <code>org.apache.sling.scripting.xproc</code> bundle in order
to work with XProc. You can achieve this either building it from
<code>contrib/scripting/xproc</code> folder in the Sling trunk or by
downloading it from the Apache Snapshot repository here: <a
href="http://people.apache.org/repo/m2-snapshot-repository/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-incubator-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-incubator-20090403.114403-1.jar";>org.apache.sling.scripting.xproc-2.0.0-incubator-20090403.114403-1.jar</a>.</p>
-<p>To deploy the bundle go to the bundles page of Apache Felix Web Console
(http://localhost:8888/system/console/bundles), select the bundle file to
upload, check the Start check box and click Install or Update button.</p>
+<p>To deploy the bundle go to the bundles page of Apache Felix Web Console
(http://localhost:8080/system/console/bundles), select the bundle file to
upload, check the Start check box and click Install or Update button.</p>
<p>In order to check whether XProc scripting engine has been installed, go to
the Script Engines page of the Apache Felix Web Console and see the entry for
XProc there:</p>
<div class="codehilite"><pre><span class="n">Apache</span> <span
class="n">Sling</span> <span class="n">Scripting</span> <span
class="n">W3C</span> <span class="n">XML</span> <span
class="n">Processing</span> <span class="n">Support</span><span
class="p">,</span> 2<span class="p">.</span>0<span class="p">.</span>0<span
class="o">-</span><span class="n">incubator</span><span class="o">-</span><span
class="n">SNAPSHOT</span>
<span class="n">Language</span> <span class="n">XMLProc</span><span
class="p">,</span> 1<span class="p">.</span>0
@@ -148,7 +148,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>Create some content</p>
<table class="codehilitetable"><tr><td class="linenos"><div
class="linenodiv"><pre>1
2</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl -u admin:admin -F sling:resourceType<span
class="o">=</span>xproc -F <span class="nv">title</span><span
class="o">=</span><span class="s2">"some title"</span> <span
class="se">\</span>
--F <span class="nv">text</span><span class="o">=</span><span
class="s2">"And some text"</span> http://localhost:8888/foo
+-F <span class="nv">text</span><span class="o">=</span><span
class="s2">"And some text"</span> http://localhost:8080/foo
</pre></div>
</td></tr></table>
@@ -248,7 +248,7 @@ h2:hover > .headerlink, h3:hover > .head
5
6
7
-8</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl http://admin:admin@localhost:8888/foo.html
+8</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl http://admin:admin@localhost:8080/foo.html
<?xml <span class="nv">version</span><span class="o">=</span><span
class="s2">"1.0"</span> <span class="nv">encoding</span><span
class="o">=</span><span class="s2">"UTF-8"</span>?>
<two>
@@ -291,7 +291,7 @@ h2:hover > .headerlink, h3:hover > .head
9
10
11
-12</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl http://admin:admin@localhost:8888/foo.html
+12</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl http://admin:admin@localhost:8080/foo.html
<?xml <span class="nv">version</span><span class="o">=</span><span
class="s2">"1.0"</span> <span class="nv">encoding</span><span
class="o">=</span><span class="s2">"UTF-8"</span>?>
<two>
@@ -341,7 +341,7 @@ h2:hover > .headerlink, h3:hover > .head
9
10
11
-12</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl http://admin:admin@localhost:8888/foo.html
+12</pre></div></td><td class="code"><div class="codehilite"><pre><span
class="nv">$ </span>curl http://admin:admin@localhost:8080/foo.html
<?xml <span class="nv">version</span><span class="o">=</span><span
class="s2">"1.0"</span> <span class="nv">encoding</span><span
class="o">=</span><span class="s2">"UTF-8"</span>?>
<two>
@@ -367,7 +367,7 @@ h2:hover > .headerlink, h3:hover > .head
<li><a href="http://markmail.org/thread/33h5nhk5e3mswrue";>Mail list
discussion</a></li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1500501 by fmeschbe on Sun, 7 Jul 2013 18:49:51 +0000
+ Rev. 1806688 by rombert on Wed, 30 Aug 2017 11:40:57 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
Modified: websites/staging/sling/trunk/content/site/groovy-support.html
==============================================================================
--- websites/staging/sling/trunk/content/site/groovy-support.html (original)
+++ websites/staging/sling/trunk/content/site/groovy-support.html Wed Aug 30
11:41:25 2017
@@ -67,7 +67,7 @@
<P>If you want to be on verge of development, you might want to go for Groovy
1.7: The second SNAPSHOT of beta-1 also contains the required headers and
classes and may as well be used unmodified in Sling. You may download it here:
<TT><A
href="http://snapshots.repository.codehaus.org/org/codehaus/groovy/groovy-all/1.7-beta-1-SNAPSHOT/groovy-all-1.7-beta-1-20081210.120632-2.jar";
class="external-link"
rel="nofollow">groovy-all-1.7-beta-1-20081210.120632-2.jar</A></TT>.</P>
-<P>To deploy the bundle go to the Bundles page, for example at <A
href="http://localhost:8888/system/console/bundles"; class="external-link"
rel="nofollow">http://localhost:8888/system/console/bundles</A> of the Apache
Felix Web Console select the bundle file to upload, check the <EM>Start</EM>
check box and click <EM>Install or Update</EM> button.</P>
+<P>To deploy the bundle go to the Bundles page, for example at <A
href="http://localhost:8080/system/console/bundles"; class="external-link"
rel="nofollow">http://localhost:8888/system/console/bundles</A> of the Apache
Felix Web Console select the bundle file to upload, check the <EM>Start</EM>
check box and click <EM>Install or Update</EM> button.</P>
<P>You may check, whether the Groovy ScriptEngine has been
"accepted" by Sling, by going to the Script Engines page of the
Apache Felix Web Console. You should see the entry for Groovy there, somthing
like this:</P>
@@ -96,17 +96,17 @@ println <SPAN class="code-quote">"Y
</PRE>
</DIV></DIV>
-<P>and upload it to the repository as <TT>/apps/nt/folder/GET.groovy</TT>
using your favourite WebDAV client or use curl to upload the file (assuming
Sling is running on localhost:8888) :</P>
+<P>and upload it to the repository as <TT>/apps/nt/folder/GET.groovy</TT>
using your favourite WebDAV client or use curl to upload the file (assuming
Sling is running on localhost:8080) :</P>
<DIV class="preformatted panel" style="border-width: 1px;"><DIV
class="preformattedContent panelContent">
-<PRE>$ curl -u admin:admin [email protected]
-F../../nt/jcr:primaryType=sling:Folder http:host:8888/apps/nt/folder
+<PRE>$ curl -u admin:admin [email protected]
-F../../nt/jcr:primaryType=sling:Folder http:host:8080/apps/nt/folder
</PRE>
</DIV></DIV>
<P>To test it create a <TT>/sample</TT> <TT>nt:Folder</TT> node using your
favourite WebDAV client or use curl again:</P>
<DIV class="preformatted panel" style="border-width: 1px;"><DIV
class="preformattedContent panelContent">
-<PRE>$ curl -u admin:admin -Fjcr:primaryType=nt:folder http://localhost:8888/
+<PRE>$ curl -u admin:admin -Fjcr:primaryType=nt:folder http://localhost:8080/
</PRE>
</DIV></DIV>
@@ -114,7 +114,7 @@ println <SPAN class="code-quote">"Y
<P>Finally, request the <TT>/sample</TT> node using your favourite Browser or
use curl again:</P>
<DIV class="preformatted panel" style="border-width: 1px;"><DIV
class="preformattedContent panelContent">
-<PRE>$ curl http://localhost:8888/sample
+<PRE>$ curl http://localhost:8080/sample
Hello World !
This is Groovy Speaking
You requested Resource JcrNodeResource, type=nt:folder, path=/sample (yes,
this is a GString)
