[sling-org-apache-sling-serviceusermapper] branch master updated: Correct typo in javadoc

[cz...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

cziegeler pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-serviceusermapper.git


The following commit(s) were added to refs/heads/master by this push:
     new 4799433  Correct typo in javadoc
4799433 is described below

commit 479943377cf5cb7e4a0bdf2da9a75b8ca46f3076
Author: Carsten Ziegeler <cz...@apache.org>
AuthorDate: Thu Nov 8 10:17:58 2018 +0100

    Correct typo in javadoc
---
 .../serviceusermapping/ServiceUserMapped.java      | 23 ++++++++++++++--------
 1 file changed, 15 insertions(+), 8 deletions(-)

diff --git a/src/main/java/org/apache/sling/serviceusermapping/ServiceUserMapped.java b/src/main/java/org/apache/sling/serviceusermapping/ServiceUserMapped.java
index 921dffb..e100661 100644
--- a/src/main/java/org/apache/sling/serviceusermapping/ServiceUserMapped.java
+++ b/src/main/java/org/apache/sling/serviceusermapping/ServiceUserMapped.java
@@ -21,15 +21,22 @@ package org.apache.sling.serviceusermapping;
 import org.osgi.annotation.versioning.ProviderType;
 
 /**
- * The <code>ServiceUserMapped</code> is a marker service that can be used to ensure that there is an already registered mapping for a certain service/subService.
- * A service reference targeting a <code>ServiceUserMapped</code> will be satisfied only if <code>ServiceUserMapper.getServiceUserID</code>
- * will resolve the subService to an userID.
- * For example setting the reference target to "(subServiceName=mySubService)" ensures that your component only starts when the subService is available.
- * The subServiceName will not be set for mappings that do not have one, and those can be referenced with a negating target "(!(subServiceName=*))".
- * Trying to reference a sub service from a bundle for which it was not registered for will not work.
+ * The <code>ServiceUserMapped</code> is a marker service that can be used to
+ * ensure that there is an already registered mapping for a certain
+ * service/subService. A service reference targeting a
+ * <code>ServiceUserMapped</code> will be satisfied only if
+ * <code>ServiceUserMapper.getServiceUserID</code> will resolve the subService
+ * to an userID. For example setting the reference target to
+ * "(subServiceName=mySubService)" ensures that your component only starts when
+ * the subService is available. The subServiceName will not be set for mappings
+ * that do not have one, and those can be referenced with a negating target
+ * "(!(subServiceName=*))". Trying to reference a sub service from a bundle for
+ * which it was not registered for will not work.
  *
- * As the service user mapper implementation is using a fallback, it is usually best to use a reference target that includes both
- * options, the sub service name and the fallback, therefore a target like "(|((subServiceName=mySubService)(!(subServiceName=*))))" should be used.
+ * As the service user mapper implementation is using a fallback, it is usually
+ * best to use a reference target that includes both options, the sub service
+ * name and the fallback, therefore a target like
+ * "(|(subServiceName=mySubService)(!(subServiceName=*)))" should be used.
  */
 @ProviderType
 public interface ServiceUserMapped {