Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "File-based Discovery"

 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
ECF 3.1 makes available a contribution from Siemens, called File-Based Discovery.  File-based discovery allows those using the ECF RFC119 implementation to trigger remote service discovery by publishing remote service interfaces and their associated endpoints in a service description xml file.
+
Starting with ECF 3.5 the old xml-file format for File-based remote services discovery is deprecated in favor of the OSGi 4.2 Remote Services Admin (RSA) specification Endpoint Description Extender Format (edef).  This format is specified by chapter 122.8 of the [http://www.osgi.org/download/r4v42/r4.enterprise.pdf OSGi enterprise specification].
  
The three pieces of information to describe a remote service with the ECF remote services endpoint are
+
See also [[File-based Discovery with the Endpoint Description Extender Format]]
  
# The service interface (i.e. the fully-qualified classname of the service interface class.  Example: '''org.eclipse.ecf.examples.remoteservices.hello.IHello'''
+
[[Category:Draft Documentation]]
# The service publication 'connect id' (aka URI of endpoint).  Example (ECF generic provider):  '''ecftcp://localhost:3282/server'''
+
# The service publication 'connect namespace'.  Example (ECF generic provider): '''org.eclipse.ecf.core.identity.StringID'''
+
 
+
<pre>
+
<?xml version="1.0" encoding="UTF-8"?>
+
  <service-descriptions xmlns="http://www.osgi.org/xmlns/sd/v1.0.0">
+
    <service-description>
+
      <provide
+
interface="org.eclipse.ecf.examples.remoteservices.hello.IHello"/>
+
      <property
+
name="ecf.sp.cid">ecftcp://localhost:3282/server</property>
+
      <property name="ecf.sp.cns">org.eclipse.ecf.core.identity.StringID</property>
+
  </service-description>
+
</service-descriptions>
+
</pre>
+
 
+
Here, for another example, is a service description file that publishes the same service interface '''org.eclipse.ecf.examples.remoteservices.hello.IHello''' with an ECF service publication connect id (ecf.sp.cid) of '''r-osgi://localhost:9278''' and an ECF service publication connect namespace (ecf.sp.cns) of '''ecf.namespace.r_osgi'''.
+
 
+
<pre>
+
<?xml version="1.0" encoding="UTF-8"?>
+
  <service-descriptions xmlns="http://www.osgi.org/xmlns/sd/v1.0.0">
+
    <service-description>
+
      <provide
+
interface="org.eclipse.ecf.examples.remoteservices.hello.IHello"/>
+
      <property
+
name="ecf.sp.cid">r-osgi://localhost:9278</property>
+
      <property name="ecf.sp.cns">ecf.namespace.r_osgi</property>
+
  </service-description>
+
</service-descriptions>
+
</pre>
+

Latest revision as of 15:44, 3 March 2011

Starting with ECF 3.5 the old xml-file format for File-based remote services discovery is deprecated in favor of the OSGi 4.2 Remote Services Admin (RSA) specification Endpoint Description Extender Format (edef). This format is specified by chapter 122.8 of the OSGi enterprise specification.

See also File-based Discovery with the Endpoint Description Extender Format

Back to the top