| [ecf-dev] ECF Collab Server as an Equinox runtime instance |
Hello ECFers, I'm doing some investigation into ECF as messaging infrastructure for portable devices. Using the equinox tooling available in 3.2, and by taking the code straight from ServerApp.java (in org.eclipse.ecf.provider) I was able create an equinox runtime that boots up an ECF collab server. These are my bundles: com.buglabs.bugnet.bug_1.0.0.jar configuration org.eclipse.core.contenttype_3.2.0.v20060511.jar org.eclipse.core.jobs_3.2.0.v20060511.jar org.eclipse.core.runtime.compatibility.auth_3.2.0.v20060511.jar org.eclipse.core.runtime.compatibility.registry_3.2.0.v20060426 org.eclipse.core.runtime_3.2.0.v20060511.jar org.eclipse.ecf.datashare_0.8.4 org.eclipse.ecf.provider.datashare_0.8.4 org.eclipse.ecf.provider_0.8.4 org.eclipse.ecf_0.8.4 org.eclipse.equinox.common_3.2.0.v20060512.jar org.eclipse.equinox.preferences_3.2.0.v20060511.jar org.eclipse.equinox.registry_3.2.0.v20060511.jar org.eclipse.osgi_3.2.0.v20060510.jar The top bundle is where I put the code from ServerApp.java. Here is my config.ini: osgi.bundles=org.eclipse.equinox.common@start,org.eclipse.core.runtime@start, org.eclipse.core.contenttype@start, org.eclipse.core.jobs@start, org.eclipse.core.runtime.compatibility.auth@start, org.eclipse.core.runtime.compatibility.registry, org.eclipse.equinox.preferences@start, org.eclipse.equinox.registry@start, org.eclipse.ecf@start, org.eclipse.ecf.datashare@start, org.eclipse.ecf.provider@start, org.eclipse.ecf.provider.datashare@start, com.buglabs.bugnet.bug@start And, as you can see here, when I start up Equinox, I get the good old ECF server message: lurcher vbug # java -jar org.eclipse.osgi_3.2.0.v20060510.jar -console osgi> Hello World!! Creating ECF server container...success! Waiting for JOIN requests at 'ecftcp://localhost:3282/server'... <ctrl>-c to stop server Worked exactly as expected. Is there any interest in creating equinox/osgi-specific releases of ECF? Also, does anyone know if it's possible to specify a "plugins" directory in the config.ini that the osgi runtime will look in for bundle dependencies, rather than having to explicitly define them? cheers ken |