svn commit: r1294062 - /karaf/cellar/trunk/manual/src/main/webapp/user-guide/transport.conf

[jb...@apache.org]

Author: jbonofre
Date: Mon Feb 27 08:36:59 2012
New Revision: 1294062

URL: http://svn.apache.org/viewvc?rev=1294062&view=rev
Log:
Complete the DOSGi section of the manual

Modified:
    karaf/cellar/trunk/manual/src/main/webapp/user-guide/transport.conf

Modified: karaf/cellar/trunk/manual/src/main/webapp/user-guide/transport.conf
URL: http://svn.apache.org/viewvc/karaf/cellar/trunk/manual/src/main/webapp/user-guide/transport.conf?rev=1294062&r1=1294061&r2=1294062&view=diff
==============================================================================
--- karaf/cellar/trunk/manual/src/main/webapp/user-guide/transport.conf (original)
+++ karaf/cellar/trunk/manual/src/main/webapp/user-guide/transport.conf Mon Feb 27 08:36:59 2012
@@ -1 +1,28 @@
 h1. DOSGi and Transport
+
+DOSGi (Distributed OSGi) enables the distribution of OSGi services across the Cellar nodes.
+
+The purpose of the Cellar DOSGi is to leverage the Cellar resources (Hazelcast instances, distributed map, etc), and
+to be very easy to use.
+
+DOSGi is part of the core Cellar feature.
+
+To be available and visible for the others nodes, the OSGi service should only have the service.exported.interfaces
+property:
+
+{code}
+<service ref="MyService" interface="my.interface">
+  <service-properties>
+    <entry key="service.exported.interfaces" value="*"/>
+  </service-properties>
+</service>
+{code}
+
+You can see all OSGi services "flagged" as distributed (available for the nodes) using the cluster:list-service command:
+
+{code}
+karaf@root> cluster:list-service
+{code}
+
+A "client" bundle could use this service. If the service is not available locally, Cellar will "route" the service call
+to the remote remote containing the service.
\ No newline at end of file