Re: [ecf-dev] ECF Collab Server as an Equinox runtime instance

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

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 
        http://dev.eclipse.org/viewcvs/index.cgi/equinox-incubator/org.eclipse.core.simpleConfigurator/
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.

Jeff

Ken Gilmer <kgilmer@xxxxxxxxx>
Sent by: ecf-dev-bounces@xxxxxxxxxxx

06/06/2006 04:07 PM

Please respond to
"Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>

To	"Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>
cc
Subject	[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


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev