Author: pderop
Date: Fri Jun 11 06:14:06 2010
New Revision: 953574
URL: http://svn.apache.org/viewvc?rev=953574&view=rev
Log:
fixed javadoc
Modified:
felix/trunk/dependencymanager/annotation/src/main/java/org/apache/felix/dm/annotation/api/Service.java
Modified:
felix/trunk/dependencymanager/annotation/src/main/java/org/apache/felix/dm/annotation/api/Service.java
URL:
http://svn.apache.org/viewvc/felix/trunk/dependencymanager/annotation/src/main/java/org/apache/felix/dm/annotation/api/Service.java?rev=953574&r1=953573&r2=953574&view=diff
==============================================================================
---
felix/trunk/dependencymanager/annotation/src/main/java/org/apache/felix/dm/annotation/api/Service.java
(original)
+++
felix/trunk/dependencymanager/annotation/src/main/java/org/apache/felix/dm/annotation/api/Service.java
Fri Jun 11 06:14:06 2010
@@ -28,7 +28,7 @@ import java.lang.annotation.Target;
* By default, all directly implemented interfaces are registered into the
OSGi registry,
* and the Service is instantiated automatically, when the Service' bundle is
started and
* when the Service dependencies are available. If you need to take control of
when and how
- * much Service instances are getting created, then you can use the
<code>factory</code>
+ * much Service instance must be created, then you can use the
<code>factory</code>
* Service attribute.<p>
* If a <code>factory</code> attribute is set, the Service is not started
automatically
* during bundle startup, and a <code>java.util.Set<Dictionary></code>