You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ro...@apache.org on 2017/08/30 11:40:57 UTC
svn commit: r1806688 - in /sling/site/trunk/content: documentation/bundles/
documentation/tutorials-how-tos/ old-stuff/scriptengineintegration/ site/
Author: rombert
Date: Wed Aug 30 11:40:57 2017
New Revision: 1806688
URL: http://svn.apache.org/viewvc?rev=1806688&view=rev
Log:
SLING-7092: Stop using port 8888 as a default for testing
Switch from port 8888 to 8080 in the documentation.
Modified:
sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext
sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext
sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext
sling/site/trunk/content/documentation/tutorials-how-tos/46-line-blog.mdtext
sling/site/trunk/content/old-stuff/scriptengineintegration/groovy-support.mdtext
sling/site/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.mdtext
sling/site/trunk/content/site/groovy-support.html
Modified: sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext Wed Aug 30 11:40:57 2017
@@ -331,8 +331,8 @@ The following properties can be configur
2x the TTL, after which time the message will be ignored.
- [1]: http://localhost:8888/system/console/configMgr/org.apache.sling.discovery.impl.Config
- [2]: http://localhost:8888/system/console/topology
+ [1]: http://localhost:8080/system/console/configMgr/org.apache.sling.discovery.impl.Config
+ [2]: http://localhost:8080/system/console/topology
## discovery.oak: Oak-based, OOTB-implementation
Modified: sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext Wed Aug 30 11:40:57 2017
@@ -50,15 +50,15 @@ We use `curl` to create content, to make
By default, JCRInstall picks up bundles found in folders named *install* under `/libs` and `/apps`, so we start by creating such a folder:
- curl -X MKCOL http://admin:admin@localhost:8888/apps/jcrtest
- curl -X MKCOL http://admin:admin@localhost:8888/apps/jcrtest/install
+ curl -X MKCOL http://admin:admin@localhost:8080/apps/jcrtest
+ curl -X MKCOL http://admin:admin@localhost:8080/apps/jcrtest/install
And we copy the bundle to install in that folder (a backslash in command lines means *continued on next line*):
curl -T desktop_awt_all-2.0.0.jar \
- http://admin:admin@localhost:8888/apps/jcrtest/install/desktop_awt_all-2.0.0.jar
+ http://admin:admin@localhost:8080/apps/jcrtest/install/desktop_awt_all-2.0.0.jar
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 *Knopflerfish Desktop* window on your desktop, and Sling's OSGi console can of course be used to check the details.
@@ -67,7 +67,7 @@ Removing the bundle from the repository
curl -X DELETE \
- http://admin:admin@localhost:8888/apps/jcrtest/install/desktop_awt_all-2.0.0.jar
+ http://admin:admin@localhost:8080/apps/jcrtest/install/desktop_awt_all-2.0.0.jar
Should cause the *Knopflerfish Desktop* window to disappear as the bundle is uninstalled.
@@ -82,13 +82,13 @@ Let's try this feature by creating a con
curl \
-F "jcr:primaryType=sling:OsgiConfig" \
-F foo=bar -F works=yes \
- http://admin:admin@localhost:8888/apps/jcrtest/install/some.config.pid
+ http://admin:admin@localhost:8080/apps/jcrtest/install/some.config.pid
And verify the contents of our config node:
curl \
- http://admin:admin@localhost:8888/apps/jcrtest/install/some.config.pid.json
+ http://admin:admin@localhost:8080/apps/jcrtest/install/some.config.pid.json
Which should display something like
@@ -98,7 +98,7 @@ Which should display something like
"jcr:primaryType":"sling:OsgiConfig","works":"yes"}
-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:
+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:
PID=some.config.pid
@@ -116,7 +116,7 @@ Let's try modifying the configuration pa
curl \
-F works=updated -F even=more \
- http://admin:admin@localhost:8888/apps/jcrtest/install/some.config.pid
+ http://admin:admin@localhost:8080/apps/jcrtest/install/some.config.pid
And check the changes in the console page:
@@ -135,7 +135,7 @@ We can now delete the configuration node
curl -X DELETE \
- http://admin:admin@localhost:8888/apps/jcrtest/install/some.config.pid
+ http://admin:admin@localhost:8080/apps/jcrtest/install/some.config.pid
And verify that the corresponding configuration is gone in the console page (after 1-2 seconds, like for all other JCRInstall operations).
Modified: sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/org-apache-sling-junit-bundles.mdtext Wed Aug 30 11:40:57 2017
@@ -157,7 +157,7 @@ The following customizers are currently
The provisioning of an appropriate instance can be done with the [slingstart-maven-plugin]({{ refs.slingstart.path }}). An example for that is given at [`testing/samples/module-with-it`](https://svn.apache.org/viewvc/sling/trunk/testing/samples/module-with-it). Since `slingstart-maven-plugin` 1.5.0 it is possible to bootstrap a Sling Server from a `model.txt` below `src/test/provisioning` independent of the packaging (see [SLING-6068](https://issues.apache.org/jira/browse/SLING-6068)).
#### LaunchpadCustomizer ####
-The *[`LaunchpadCustomizer.java`](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java)* only verifies that a Sling instance is ready at a given port and configures the `ClientSideTeleporter` to deploy to `http://localhost:8888` with the credentials `admin`:`admin`. `LaunchpadCustomizer` uses the `HttpTestBase` therefore some parameters are customizable through system properties. There is no bootstrapping of an instance done here, so this must be done separately!
+The *[`LaunchpadCustomizer.java`](https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/junit/teleporter/customizers/LaunchpadCustomizer.java)* only verifies that a Sling instance is ready at a given port and configures the `ClientSideTeleporter` to deploy to `http://localhost:8080` with the credentials `admin`:`admin`. `LaunchpadCustomizer` uses the `HttpTestBase` therefore some parameters are customizable through system properties. There is no bootstrapping of an instance done here, so this must be done separately!
#### BWIT_TeleporterCustomizer ####
The *[`BWIT_TeleporterCustomizer.java`](http://svn.apache.org/viewvc/sling/trunk/testing/samples/bundle-with-it/src/test/java/org/apache/sling/junit/teleporter/customizers/BWIT_TeleporterCustomizer.java)* relies on `SlingTestBase` 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 [here](http://labs.6dglobal.com/blog/2013-06-05/creating-integration-tests-apache-sling/) and implicitly done by the customizer itself.
Modified: sling/site/trunk/content/documentation/tutorials-how-tos/46-line-blog.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/tutorials-how-tos/46-line-blog.mdtext?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/tutorials-how-tos/46-line-blog.mdtext (original)
+++ sling/site/trunk/content/documentation/tutorials-how-tos/46-line-blog.mdtext Wed Aug 30 11:40:57 2017
@@ -12,11 +12,11 @@ Although this is a simple sample, it req
## Step 0: Start, configure and login to Sling
-See [Getting and Building Sling]({{ refs.getting-and-building-sling.path }}) for how to start Sling. Start it on port 8888 for the below links to work.
+See [Getting and Building Sling]({{ refs.getting-and-building-sling.path }}) for how to start Sling. Start it on port 8080 for the below links to work.
-For this sample we need the optional *org.apache.sling.samples.path-based.rtp* bundle, if it's not present in the [OSGi console](http://localhost:8888/system/console/bundles), install and start it. That bundle is not released yet so you might need to build it yourself, from its [source](http://svn.apache.org/repos/asf/sling/trunk/samples/path-based-rtp). The bundle must then appear in the [OSGI console's list of bundles](http://localhost:8888/system/console/bundles), with name = *org.apache.sling.samples.path-based.rtp* and status = *Active*.
+For this sample we need the optional *org.apache.sling.samples.path-based.rtp* bundle, if it's not present in the [OSGi console](http://localhost:8080/system/console/bundles), install and start it. That bundle is not released yet so you might need to build it yourself, from its [source](http://svn.apache.org/repos/asf/sling/trunk/samples/path-based-rtp). The bundle must then appear in the [OSGI console's list of bundles](http://localhost:8080/system/console/bundles), with name = *org.apache.sling.samples.path-based.rtp* and status = *Active*.
-Then, login using <http://localhost:8888/?sling:authRequestLogin=1> which should prompt you for a username and password, use *admin* and *admin*. Once that's done, <http://localhost:8888/index.html> should say *You are currently logged in as user *admin* to workspace *default**.
+Then, login using <http://localhost:8080/?sling:authRequestLogin=1> which should prompt you for a username and password, use *admin* and *admin*. Once that's done, <http://localhost:8080/index.html> should say *You are currently logged in as user *admin* to workspace *default**.
## Step 1: Creating content
@@ -50,10 +50,10 @@ The easiest way to create content in Sli
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).
-To test the form, start Sling and save the above script as {{/apps/blog/blog.esp}} [^esp] in the Sling repository - a WebDAV mount is the easiest way to do that. Browsing to <http://localhost:8888/content/blog/*.html> [^port] should display the above form.
+To test the form, start Sling and save the above script as {{/apps/blog/blog.esp}} [^esp] in the Sling repository - a WebDAV mount is the easiest way to do that. Browsing to <http://localhost:8080/content/blog/*.html> [^port] should display the above form.
[^esp]: ESP is Sling's server-side javascript language
-[^port]: This assumes your instance of Sling is running on port 8888. If that's not the case, adjust the example URLs accordingly.
+[^port]: This assumes your instance of Sling is running on port 8080. If that's not the case, adjust the example URLs accordingly.
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.
@@ -66,7 +66,7 @@ At this point you're probably looking at
## Step 2: Where's my content?
-To verify that our content has been created, we can have a look at the JSON data at <http://localhost:8888/content/blog/foo.tidy.json>, which should display our new node's values:
+To verify that our content has been created, we can have a look at the JSON data at <http://localhost:8080/content/blog/foo.tidy.json>, which should display our new node's values:
{
@@ -91,7 +91,7 @@ And add the `Sling.wizard()` after the f
<script>Sling.wizard();</script>
-Reloading the form at `http://localhost:8888/content/blog/*.html` and creating a new post should now redirect to an editable version of the post, with the form fields correctly initialized.
+Reloading the form at `http://localhost:8080/content/blog/*.html` and creating a new post should now redirect to an editable version of the post, with the form fields correctly initialized.
We can now create and edit posts; let's add some navigation, using more of the *sling.js* functionality.
Modified: sling/site/trunk/content/old-stuff/scriptengineintegration/groovy-support.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/old-stuff/scriptengineintegration/groovy-support.mdtext?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/old-stuff/scriptengineintegration/groovy-support.mdtext (original)
+++ sling/site/trunk/content/old-stuff/scriptengineintegration/groovy-support.mdtext Wed Aug 30 11:40:57 2017
@@ -12,7 +12,7 @@ So, on 11. Dec. 2008 Paul King of the Gr
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: `[groovy-all-1.7-beta-1-20081210.120632-2.jar]({{ refs.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.path }})`.
-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 *Start* check box and click *Install or Update* button.
+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 *Start* check box and click *Install or Update* button.
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:
@@ -38,23 +38,23 @@ To test create a simple Groovy script, f
println "You requested the Resource ${resource} (yes, this is a GString)"
-and upload it to the repository as `/apps/nt/folder/GET.groovy` using your favourite WebDAV client or use curl to upload the file (assuming Sling is running on localhost:8888) :
+and upload it to the repository as `/apps/nt/folder/GET.groovy` using your favourite WebDAV client or use curl to upload the file (assuming Sling is running on localhost:8080) :
- $ curl -u admin:admin -FGET.groovy=@GET.groovy -F../../nt/jcr:primaryType=sling:Folder http:host:8888/apps/nt/folder
+ $ curl -u admin:admin -FGET.groovy=@GET.groovy -F../../nt/jcr:primaryType=sling:Folder http:host:8080/apps/nt/folder
To test it create a `/sample` `nt:Folder` node using your favourite WebDAV client or use curl again:
- $ curl -u admin:admin -Fjcr:primaryType=nt:folder http://localhost:8888/
+ $ curl -u admin:admin -Fjcr:primaryType=nt:folder http://localhost:8080/
Finally, request the `/sample` node using your favourite Browser or use curl again:
- $ curl http://localhost:8888/sample
+ $ 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)
Modified: sling/site/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.mdtext?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.mdtext (original)
+++ sling/site/trunk/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.mdtext Wed Aug 30 11:40:57 2017
@@ -17,7 +17,7 @@ The source code is found in the [contrib
Install the `org.apache.sling.scripting.xproc` bundle in order to work with XProc. You can achieve this either building it from `contrib/scripting/xproc` folder in the Sling trunk or by downloading it from the Apache Snapshot repository here: [org.apache.sling.scripting.xproc-2.0.0-incubator-20090403.114403-1.jar](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).
-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.
+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.
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:
@@ -47,7 +47,7 @@ Let's see some samples in order to under
#!bash
$ curl -u admin:admin -F sling:resourceType=xproc -F title="some title" \
- -F text="And some text" http://localhost:8888/foo
+ -F text="And some text" http://localhost:8080/foo
2. Use WebDAV or curl to create a pipeline script at `/apps/xproc/xproc.xpl` :
@@ -102,7 +102,7 @@ Let's see some samples in order to under
4. Request foo.html to execute the pipeline:
#!bash
- $ curl http://admin:admin@localhost:8888/foo.html
+ $ curl http://admin:admin@localhost:8080/foo.html
<?xml version="1.0" encoding="UTF-8"?>
<two>
@@ -127,7 +127,7 @@ Let's see some samples in order to under
6. Again, request foo.html to execute the pipeline:
#!bash
- $ curl http://admin:admin@localhost:8888/foo.html
+ $ curl http://admin:admin@localhost:8080/foo.html
<?xml version="1.0" encoding="UTF-8"?>
<two>
@@ -158,7 +158,7 @@ Let's see some samples in order to under
9. Request foo.html to execute the pipeline:
#!bash
- $ curl http://admin:admin@localhost:8888/foo.html
+ $ curl http://admin:admin@localhost:8080/foo.html
<?xml version="1.0" encoding="UTF-8"?>
<two>
Modified: sling/site/trunk/content/site/groovy-support.html
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/site/groovy-support.html?rev=1806688&r1=1806687&r2=1806688&view=diff
==============================================================================
--- sling/site/trunk/content/site/groovy-support.html (original)
+++ sling/site/trunk/content/site/groovy-support.html Wed Aug 30 11:40:57 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 -FGET.groovy=@GET.groovy -F../../nt/jcr:primaryType=sling:Folder http:host:8888/apps/nt/folder
+<PRE>$ curl -u admin:admin -FGET.groovy=@GET.groovy -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)