This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e916a5b6c Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/655/
e916a5b6c is described below
commit e916a5b6cc31a6116388deda198bdad338f2aedd
Author: jenkins <[email protected]>
AuthorDate: Wed Apr 12 07:14:48 2023 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/655/
---
documentation/the-sling-engine/servlets.html | 2 +-
sitemap.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/documentation/the-sling-engine/servlets.html
b/documentation/the-sling-engine/servlets.html
index cf6ad4861..7ae820aa1 100644
--- a/documentation/the-sling-engine/servlets.html
+++ b/documentation/the-sling-engine/servlets.html
@@ -373,7 +373,7 @@ sling.servlet.extensions = [ "html",
"txt", "json"
<h2><a href="#error-handler-servlets-or-scripts"
id="error-handler-servlets-or-scripts">Error Handler Servlet(s) or
Scripts</a></h2>
<p>Error handling support is described on the <a
href="/documentation/the-sling-engine/errorhandling.html">Errorhandling</a>
page.</p>
<h2><a href="#osgi-http-whiteboard-servlets"
id="osgi-http-whiteboard-servlets">OSGi HTTP Whiteboard Servlets</a></h2>
-<p>For certain edge cases even in an OSGi runtime running Sling certain
servlets are still registered leveraging the <a
href="https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.http.whiteboard.html">OSGi
HTTP Whiteboard</a> instead of leveraging the Sling servlet registration
outlined above. Note though, that whenever the Sling engine bundle is deployed
it registers a Servlet with the OSGi HTTP Whiteboard for path <code>/</code>
which will take precedence by default over all oth [...]
+<p>For certain edge cases even in an OSGi runtime running Sling certain
servlets are still registered leveraging the <a
href="https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.http.whiteboard.html">OSGi
HTTP Whiteboard</a> instead of leveraging the Sling servlet registration
outlined above. Note though, that whenever the Sling engine bundle is deployed
it registers a Servlet with the OSGi HTTP Whiteboard for path <code>/</code>
which will take precedence by default over all oth [...]
</section></div></div>
</div>
</div>
diff --git a/sitemap.xml b/sitemap.xml
index 179ebf479..f81c4c747 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,9 +1,9 @@
<?xml version="1.0"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9
http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
<url>
-
<loc>https://sling.apache.org/releases.html</loc><lastmod>2023-04-09</lastmod>
- </url><url>
<loc>https://sling.apache.org/documentation/the-sling-engine/servlets.html</loc><lastmod>2023-04-12</lastmod>
+ </url><url>
+
<loc>https://sling.apache.org/releases.html</loc><lastmod>2023-04-09</lastmod>
</url><url>
<loc>https://sling.apache.org/project-information/project-team.html</loc><lastmod>2022-10-31</lastmod>
</url><url>