Repository: sling-site Updated Branches: refs/heads/master d65a41d55 -> e7c2d03cd
http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/documentation/development/release-management.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md index fdc4a45..d3064ec 100644 --- a/src/main/jbake/content/documentation/development/release-management.md +++ b/src/main/jbake/content/documentation/development/release-management.md @@ -69,6 +69,7 @@ First prepare your POMs for release: ... * If you experience an error during deployment like a HTTP 401 check your settings for the required server entries as outlined in the *Prerequisites* + * Depending on the OS & the gpg version you have, you might hit https://issues.apache.org/jira/browse/MGPG-59, in which case you need, before maven command, to run `gpg --use-agent --armor --detach-sign --output $(mktemp) pom.xml` * Make sure the generated artifacts respect the Apache release [rules](http://www.apache.org/dev/release.html): NOTICE and LICENSE files should be present in the META-INF directory within the jar. For \-sources artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4 * You should verify the deployment under the [snapshot](https://repository.apache.org/content/groups/snapshots/org/apache/sling) repository on Apache @@ -188,6 +189,7 @@ If the vote passes: 1. Push the release to [https://dist.apache.org/repos/dist/release/sling/](https://dist.apache.org/repos/dist/release/sling/). This is only possible for PMC members (for a reasoning look at [http://www.apache.org/dev/release.html#upload-ci](http://www.apache.org/dev/release.html#upload-ci)). If you are not a PMC member, please ask one to do the upload for you. 1. Commit the released artifacts to [https://dist.apache.org/repos/dist/release/sling/](https://dist.apache.org/repos/dist/release/sling/) which is replicated to [http://www.apache.org/dist/sling/](http://www.apache.org/dist/sling/) quickly via svnpubsub. Hint: use svn import to avoid having to checkout the whole folder first. The easiest to do this is to get the released artifact using the check script (check_staged_release.sh) and then simply copy the artifacts from the downloaded folder to your local checkout folder. Make sure to not add the checksum files for the signature file \*.asc.\*). * Make sure to *not* change the end-of-line encoding of the .pom when uploaded via svn import! Eg when a windows style eol encoded file is uploaded with the setting '*.pom = svn:eol-style=native' this would later fail the signature checks! + * Following the SVN commit you will receive an email from the 'Apache Reporter Service'. Follow the link and add the release data, as it used by the PMC chair to prepare board reports. 1. Delete the old release artifacts from that same dist.apache.org svn folder (the dist directory is archived) 1. Push the release to Maven Central 1. Login to [https://repository.apache.org](https://repository.apache.org) with your Apache SVN credentials. Click on *Staging*. Find your closed staging repository and select it by checking the select box. Select the *Releases* repository from the drop-down list and click *Release* from the menu above. @@ -207,6 +209,11 @@ And keep the versions sorted, so when adding a new version moved it down to just Close all issues associated with the released version. +## Update the Sling Launchpad + +If the bundle was already included in the Sling Launchpad or if it a new release that should be included +add it with the release version in the provisioning model under `launchpad/builder/src/main/provisioning`. + ## Create an Announcement http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/documentation/the-sling-engine/architecture.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/documentation/the-sling-engine/architecture.md b/src/main/jbake/content/documentation/the-sling-engine/architecture.md index 71e1255..73a4c19 100644 --- a/src/main/jbake/content/documentation/the-sling-engine/architecture.md +++ b/src/main/jbake/content/documentation/the-sling-engine/architecture.md @@ -16,7 +16,7 @@ The following sections elaborate on each of these highlights. ## OSGi -[OSGi](http://www.osgi.org) is a consortium that has developed a specification to build modular and extensible applications. This offers [various benefits](http://www.osgi.org/About/WhyOSGi). We deal mainly with two parts of the specifications: The Core Specification, which defines the OSGi Framework and Core Services, and the Compendium Services Specification, which defines a host of services that extend the functionality of the OSGi Framework. +[OSGi](http://www.osgi.org) is a consortium that has developed a specification to build modular and extensible applications. This offers [various benefits](https://www.osgi.org/developer/benefits-of-using-osgi/). We deal mainly with two parts of the specifications: The Core Specification, which defines the OSGi Framework and Core Services, and the Compendium Services Specification, which defines a host of services that extend the functionality of the OSGi Framework. ### OSGi Framework http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/documentation/the-sling-engine/service-authentication.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/documentation/the-sling-engine/service-authentication.md b/src/main/jbake/content/documentation/the-sling-engine/service-authentication.md index db89fde..f62de52 100644 --- a/src/main/jbake/content/documentation/the-sling-engine/service-authentication.md +++ b/src/main/jbake/content/documentation/the-sling-engine/service-authentication.md @@ -111,9 +111,11 @@ The `ServiceUserMapper` defines the following API: The implementation uses two fallbacks in case no mapping can be found for the given subServiceName 1. Use user mapping for the serviceName only (not considering subServiceName) -1. Use default user (if one is configured). +1. Use default user (if one is configured in the OSGi configuration for PID ` org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl`). +1. Use default mapping (if it is enabled in the OSGi configuration for PID ` org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl`) which looks up a user with id `serviceuser--<bundleId>[--<subservice-name>]` (since Service User Mapper 1.3.0, [SLING-6227](https://issues.apache.org/jira/browse/SLING-6772)). -In addition a service named `ServiceUserMapped` is registered for each bundle and subservice name for which a service user mapping is configured ([SLING-4312](https://issues.apache.org/jira/browse/SLING-4312)). By explicitly defining a (static) reference towards `ServiceUserMapped` one can defer starting the service until that service user mapping is available. +In addition a service named `ServiceUserMapped` is registered for each bundle and subservice name for which a service user mapping is explicitly configured ([SLING-4312](https://issues.apache.org/jira/browse/SLING-4312)). By explicitly defining a (static) reference towards `ServiceUserMapped` one can defer starting the service until that service user mapping is available. +Please note, that the two last default mappings are not represented as a ServiceUserMapped service and therefore the above mentioned reference does not work. ### `ResourceResolverFactory` @@ -157,11 +159,11 @@ service. The additional Subservice Name may be provided with the ### Service User Mappings For each service/subservice name combination an according mapping needs to be provided. The mapping binds a service name/subservice name to a JCR system user. -This is configured through an OSGi configuration for the factory configuration with PID `org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended` [SLING-3578](https://issues.apache.org/jira/browse/SLING-3578). There you can set one configuration property named `user.mapping` getting a String array as value where each entry must stick to the following format: +This is configured through an OSGi configuration for the factory configuration with PID `org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended` (added in [SLING-3578](https://issues.apache.org/jira/browse/SLING-3578)). There you can set one configuration property named `user.mapping` getting a String array as value where each entry must stick to the following format: - <service-name>[:<subservice-name>]=<authorizable id of a JCR system user>] + <service-name>[:<subservice-name>]=<authorizable id of a JCR system user> -The according user must exist at the point in time where `ResourceResolverFactory.getServiceResourceResolver(...)` or `SlingRepository.loginService(...)` is called. If you rely on one of those methods in your `activate` method of an OSGi component you should make sure that you defer starting your OSGi component until the according service user mapping is in place. For that you can reference the OSGi service `ServiceUserMapped` ([SLING-4312](https://issues.apache.org/jira/browse/SLING-4312)), optionally with a target filter on property `subServiceName` (in case such a subservice name is used). The service `ServiceUserMapped` does not expose any methods but is only a marker interface exclusively used to defer starting of other OSGi components. However this waits only for the mapping configuration to be available, it does not wait for the service user itself to be available. +The according user must exist at the point in time where `ResourceResolverFactory.getServiceResourceResolver(...)` or `SlingRepository.loginService(...)` is called. If you rely on one of those methods in your `activate` method of an OSGi component you should make sure that you defer starting your OSGi component until the according service user mapping is in place. For that you can reference the OSGi service `ServiceUserMapped` (see Section `ServiceUserMapper` above), optionally with a target filter on property `subServiceName` (in case such a subservice name is used). The service `ServiceUserMapped` does not expose any methods but is only a marker interface exclusively used to defer starting of other OSGi components. However this waits only for the mapping configuration to be available, it does not wait for the service user itself to be available. Example OSGi DS Component @@ -177,8 +179,6 @@ Example OSGi DS Component class MyComponent { } -There is a default mapping applied if no OSGi configuration is available for the mapping. The default is: "serviceuser--" + bundleId [ + "--" + subservice-name]. Please note, that these default mappings are not represented as a ServiceUserMapped service and therefore the above mentioned reference does not work. - ## Deprecation of administrative authentication Originally the `ResourceResolverFactory.getAdministrativeResourceResolver` http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md b/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md index cb74a4c..6bc86aa 100644 --- a/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md +++ b/src/main/jbake/content/documentation/tutorials-how-tos/46-line-blog.md @@ -15,11 +15,11 @@ Although this is a simple sample, it requires some custom settings to work. If y ## Step 0: Start, configure and login to Sling -See [Getting and Building Sling](/documentation/development/getting-and-building-sling.html) for how to start Sling. Start it on port 8888 for the below links to work. +See [Getting and Building Sling](/documentation/development/getting-and-building-sling.html) 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 @@ -53,10 +53,10 @@ The easiest way to create content in Sling is to use an HTTP POST request, let's 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. @@ -69,7 +69,7 @@ At this point you're probably looking at an empty form with an URL ending in _fo ## 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: { @@ -94,7 +94,7 @@ And add the `Sling.wizard()` after the form, where we had the _code of step 2 co <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. http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/news.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/news.md b/src/main/jbake/content/news.md index 95b7906..27810fb 100644 --- a/src/main/jbake/content/news.md +++ b/src/main/jbake/content/news.md @@ -3,7 +3,41 @@ type=page status=published ~~~~~~ -* New Releases: [Apache Sling 9](/news/sling-launchpad-9-released.html), Apache Sling Launchpad Testing 9, Apache Sling Launchpad Testing WAR version 9, Apache Sling Launchpad Testing Fragment Bundle 2.0.12, Apache Sling Launchpad Testing Services 2.0.12, Apache Sling Launchpad Test Bundles 0.0.2, Apache Sling Launchpad Testing Services WAR 2.0.12, Apache Sling Integration Tests 1.0.4 ( June 12S , 2017 ) +* New Release: Apache Sling Pipes 1.1.0 (September 24th, 2017) +* New Release: Apache Sling Maven Sling Plugin 2.3.2 (September 23th, 2017) +* New Release: Apache Sling Repoinit JCR version 1.1.6, Apache Sling Repoinit Parser version 1.2.0 (September 22th, 2017) +* New Release: Apache Sling Context-Aware Configuration Impl 1.4.4 (September 22th, 2017) +* New Releases: Apache Sling Scripting HTL Compiler 1.0.14, Apache Sling Scripting HTL Java Compiler 1.0.14, Apache Sling Scripting HTL Engine 1.0.42 (September 20th, 2017) +* New Release: Apache Sling Commons Scheduler 2.7.2 (September 19th, 2017) +* New Release: Apache Sling Commons Compiler 2.3.4 (September 17th, 2017) +* New Release: Apache Sling Commons Compiler 2.3.2 (September 9th, 2017) +* New Release: Apache Sling RRD4J metrics reporter 1.0.0 (September 8th, 2017) +* New Releases: Apache Sling Scripting JavaScript 3.0.2, Apache Sling Scripting HTL JS Use Provider 1.0.24, Apache Sling Scripting HTL Engine 1.0.40, Apache Sling Parent 32, Apache Sling Java Version Maven Plugin 1.0.0 (September 4th, 2017) +* New Releases: Apache Sling Scripting HTL Compiler 1.0.12, Apache Sling Scripting HTL Java Compiler 1.0.12, Apache Sling Scripting HTL Engine 1.0.38 (September 1st, 2017) +* New Release: Apache Sling Launchpad Base 5.6.8-2.6.24 (August 31st, 2017) +* New Release: Apache Sling Provisioning Model 1.8.4, Apache Sling Slingstart Maven Plugin 1.7.8 (August 28th, 2017) +* New Release: Apache Sling Servlets Resolver 2.4.14 (August 28th, 2017) +* New Release: Apache Sling Commons Scheduler 2.7.0 (August 25th, 2017) +* New Release: Apache Sling Scripting JSP 2.3.2 (August 24th, 2017) +* New Releases: Apache Sling Rewriter 1.2.2, Apache Sling Launchpad Base 5.6.6-2.6.22 (August 17th, 2017) +* New Release: Apache Sling Event 4.2.6 (August 16th, 2017) +* New Release: Apache Sling Default POST Servlets 2.3.22 (August 14th, 2017) +* New Release: Apache Sling Parent 31 (August 8th, 2017) +* New Releases: Apache Sling Security 1.1.6, Apache Sling Scripting HTL Engine 1.0.38, Apache Sling Scripting HTL Compiler 1.0.10, Apache Sling HTL Maven Plugin 1.0.8 (August 7th, 2017) +* New Release: Apache Sling Launchpad Base 5.6.6-2.6.20 (August 3rd, 2017) +* New Release: Apache Sling Resource Resolver 1.5.30 (July 27th, 2017) +* New Releases: Apache Sling Service User Mapper 1.3.4, Resource Resolver 1.5.28, JCR Base 3.0.4, and JCR Resource 3.0.4 (July 21th, 2017) +* New Releases: Apache Sling File System Resource Provider 2.1.8, File System Resource Provider 1.4.8 (July 18th, 2017) +* New Releases: Apache Sling Commons Johnzon 1.1.0 (July 17th, 2017) +* New Releases: Apache Sling Discovery Base 2.0.4 and Discovery Oak 1.2.20 (July 10th, 2017) +* New Releases: Apache Sling Resource Resolver 1.5.26 (July 10th, 2017) +* New Releases: Apache Sling Auth Core 1.4.0 (June 29th, 2017) +* New Releases: Apache Sling Event 4.2.4, JCR Content Parser 1.2.4, File System Resource Provider 2.1.6, File System Resource Provider 1.4.6 (June 26th, 2017) +* New Releases: Apache Sling Security 1.1.4 (June 21st, 2017) +* New Releases: Apache Sling Testing Clients 1.1.4, Apache Sling Testing Email 1.0.0, Apache Sling Resource Merger 1.3.4 (June 20th, 2017) +* New Release: Apache Sling Slingstart Archetype (June 15th, 2017) +* New Release: Apache Sling JSPC Maven Plugin 2.1.0 and Apache Sling Slingstart Archetype 1.0.2 (June 15th, 2017) +* New Releases: [Apache Sling 9]({{refs.sling-launchpad-9-released.path}}), Apache Sling Launchpad Testing 9, Apache Sling Launchpad Testing WAR version 9, Apache Sling Launchpad Testing Fragment Bundle 2.0.12, Apache Sling Launchpad Testing Services 2.0.12, Apache Sling Launchpad Test Bundles 0.0.2, Apache Sling Launchpad Testing Services WAR 2.0.12, Apache Sling Integration Tests 1.0.4 (June 12th, 2017) * New Releases: Apache Sling JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, and Tooling Support Source 1.0.4 (June 6th, 2017) * New Releases: Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, and Commons Metrics 1.2.2 (June 6th, 2017) * New Releases: Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0 (June 2nd, 2017) http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/old-stuff/scriptengineintegration/groovy-support.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/old-stuff/scriptengineintegration/groovy-support.md b/src/main/jbake/content/old-stuff/scriptengineintegration/groovy-support.md index 2e6f356..b1c0f8a 100644 --- a/src/main/jbake/content/old-stuff/scriptengineintegration/groovy-support.md +++ b/src/main/jbake/content/old-stuff/scriptengineintegration/groovy-support.md @@ -12,7 +12,7 @@ So, on 11. Dec. 2008 Paul King of the Groovy Team has deployed a [first RC1 Snap 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, for example 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 [email protected] -F../../nt/jcr:primaryType=sling:Folder http:host:8888/apps/nt/folder + $ curl -u admin:admin [email protected] -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) http://git-wip-us.apache.org/repos/asf/sling-site/blob/e7c2d03c/src/main/jbake/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.md b/src/main/jbake/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.md index 3d201e8..54f1cc7 100644 --- a/src/main/jbake/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.md +++ b/src/main/jbake/content/old-stuff/scriptengineintegration/xslt-processing-pipeline.md @@ -19,7 +19,7 @@ The source code is found in the [contrib/scripting/xproc](http://svn.apache.org/ 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: @@ -49,7 +49,7 @@ Let's see some samples in order to understand the processing behaviour. #!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` : @@ -104,7 +104,7 @@ Let's see some samples in order to understand the processing behaviour. 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> @@ -129,7 +129,7 @@ Let's see some samples in order to understand the processing behaviour. 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> @@ -160,7 +160,7 @@ Let's see some samples in order to understand the processing behaviour. 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>
