Author: fmeschbe
Date: Thu Aug 8 14:13:46 2013
New Revision: 1511794
URL: http://svn.apache.org/r1511794
Log:
For now remove Sling-Service manifest header support (see SLING-2944 for the
reason)
Modified:
sling/site/trunk/content/documentation/the-sling-engine/service-authentication.mdtext
Modified:
sling/site/trunk/content/documentation/the-sling-engine/service-authentication.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/service-authentication.mdtext?rev=1511794&r1=1511793&r2=1511794&view=diff
==============================================================================
---
sling/site/trunk/content/documentation/the-sling-engine/service-authentication.mdtext
(original)
+++
sling/site/trunk/content/documentation/the-sling-engine/service-authentication.mdtext
Thu Aug 8 14:13:46 2013
@@ -55,14 +55,7 @@ Thus the actual service identification (
#!text
service-id = service-name [ ":" subservice-name ] .
-The `service-name` is the value of the `Sling-Service` bundle manifest
-header. This name can be any string valid as a manifest header but must
-not contain a colon `:` which is used to delimit the `service-name` from
-the `service-info` in the `service-id` string.
-
-If the bundle does not have a `Sling-Service` bundle manifest header or
-if the value is the empty string, the bundle's symbolic name is used as
-the `service-name`.
+The `service-name` is the symbolic name of the bundle providing the service.
### Example: Tenant Administration
