my servlet comments were wrt Scott's
message about the way they are running the server now. He said they
have Tomcat with the servlet bridge. I always ask people why they
do that. Not that it is wrong but that I like to hear about hte usecases.
Ken Gilmer <kgilmer@xxxxxxxxx> Sent by: ecf-dev-bounces@xxxxxxxxxxx
06/06/2006 11:18 PM
Please respond to
"Eclipse Communication Framework (ECF) developer mailing list."
"Eclipse Communication Framework
(ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>
Re: [ecf-dev] ECF Collab Server as an
Equinox runtime instance
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
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.
[ecf-dev] ECF Collab Server as an Equinox
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:
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