This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 35886359e Clarify usage of OSGi HTTP Whiteboard with Sling (#108)
35886359e is described below
commit 35886359ecf4f47ec9126a9d8a39d22b05f39e4c
Author: Konrad Windszus <[email protected]>
AuthorDate: Wed Apr 12 09:04:08 2023 +0200
Clarify usage of OSGi HTTP Whiteboard with Sling (#108)
This outlines the limitations discovered in SLING-11677
---
src/main/jbake/content/documentation/the-sling-engine/servlets.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/main/jbake/content/documentation/the-sling-engine/servlets.md
b/src/main/jbake/content/documentation/the-sling-engine/servlets.md
index f25c3484b..661ecfda7 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/servlets.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/servlets.md
@@ -316,3 +316,8 @@ If a resource type has no explicit resource super type, the
resource super type
## Error Handler Servlet(s) or Scripts
Error handling support is described on the
[Errorhandling](/documentation/the-sling-engine/errorhandling.html) page.
+
+## OSGi HTTP Whiteboard Servlets
+
+For certain edge cases even in an OSGi runtime running Sling certain servlets
are still registered leveraging the [OSGi HTTP
Whiteboard](https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.http.whiteboard.html)
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 `/` which will take precedence
by default over all other servlets registered through OSGi Http Whiteboad
leveraging the *default* servlet context
(SLING-11677)[https://issues.apache.org/jira/browse/SLING-11677]. Therefore,
all servlets registered via OSGi HTTP Whiteboard need to be registered with a
custom context having a `service.ranking` higher than the one from [...]
