Author: sseifert
Date: Mon Sep 19 14:53:37 2016
New Revision: 1761464

URL: http://svn.apache.org/viewvc?rev=1761464&view=rev
Log:
switch to simplified API for config properties

Modified:
    sling/site/trunk/content/documentation/development/osgi-mock.mdtext

Modified: sling/site/trunk/content/documentation/development/osgi-mock.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/osgi-mock.mdtext?rev=1761464&r1=1761463&r2=1761464&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/osgi-mock.mdtext 
(original)
+++ sling/site/trunk/content/documentation/development/osgi-mock.mdtext Mon Sep 
19 14:53:37 2016
@@ -60,9 +60,9 @@ Example:
       @Test
       public void testSomething() {
 
-        // register and activate service
+        // register and activate service with configuration
         MyService service1 = context.registerInjectActivateService(new 
MyService(),
-            ImmutableMap.<String, Object>of("prop1", "value1"));
+            "prop1", "value1");
 
         // get service instance
         OtherService service2 = context.getService(OtherService.class);
@@ -94,9 +94,9 @@ Example:
     // get bundle context
     BundleContext bundleContext = MockOsgi.newBundleContext();
 
-    // get component context
+    // get component context with configuration
     BundleContext bundleContext = MockOsgi.newComponentContext(properties,
-        ImmutableMap.<String, Object>of("prop1", "value1"));
+        "prop1", "value1");
 
 It is possible to simulate registering of OSGi services (backed by a simple 
hash map internally):
 


Reply via email to