I suspect that most of the stuff listed is being dragged in by having included org.eclipse.core.runtime. There I suspect you are doing that because you have an Eclipse application etc.
You are correct. I used the "add required plugins" magic in the equinox runtime profile to determine the dependencies for my bundle.
With a bit of Import-Package work you may well be able to reduce the list quite a bit.
That sounds great. Coming from an embedded perspective, every byte counts!
as a point of interest, why run the server as embedded in tomcat rather than standalone using the Equinox HTTP service (or the Jetty based one that is coming). Bascially you get the same function/setup but eliminate some buck passing and bulk.
What do you mean by bulk? My embedded system does not have a servlet container. I assumed that running equinox plain-jane would be the lightest approach. How is a servlet saving me space?
Thanks for your help!
On Jun 6, 2006, at 8:57 PM, Jeff McAffer wrote:
This is very interesting to me. It would actually be quite interesting to see if you can trim down the list of bundles that are needed. I suspect that most of the stuff listed is being dragged in by having included org.eclipse.core.runtime. There I suspect you are doing that because you have an Eclipse application etc. This is cool and certainly works. Going forward we are trying to continue our refactoring of the runtime so, for example, you wont have to have content types just cause you wanted to have an application. With a bit of Import-Package work you may well be able to reduce the list quite a bit.
In any event, you asked about ways of adding all the bundles in a dir rather than having to list them. The answer is yes. There are two ways you can do this right now.
1) include org.eclipse.update.configurator in your osgi.bundles like pretty much like we do in the normal Eclipse config.ini. "configurators" are responsible for discovering and installing bundles in various ways. the Update configurator does this by looking in the plugins dir etc and then installing everything it finds. you have to have it in the osgi.bundles list and ensure it is started. Again, look at the standard file in the Eclipse SDK drops.
2) we did a "simple configurator" in Equinox at one point. I don't know the complete state of it but take a look at
and see what you think. I think it does (or could easily be modified to do) whole directories. Again, you would have to include the simple configurator on the osgi.bundles list and ensure it is started.
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:
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?
ecf-dev mailing list
ecf-dev mailing list