[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.equinox] Re: Alternative runtimes (Re: Work items posted) 
ted stockwell wrote:

As a reality check, here is how I see Equinox developing and the difference
between OSGi and Equinox.  To deploy a Servlet in OSGi a bundle would lookup
the HttpService interface and then call specific methods to deploy a
Servlet.  In Equinox I think the procedure would be to use the extension
point registry to lookup a specific extension point and then create a new
extension of that extension point.  The extension point concept adds a level
of power to the whole framework.  Consider this scenario for example:  I
create a plugin that exports an extension point for registering web
services.  Later I can add another plugin that creates RMI facades to any
registered web services.  This can be done in Equinox in a way that is
decoupled from the web services plugin.  The RMI plugin will listen to
registrations against the web services extension point.  In OSGi I would
have to add the capability to listen for registrations to each service that
I intended, in advance, to be extendable in this way.

The Http Service was one of the first services we developed and has therefore a model where it keeps a private registry of Servlets and static resources. However, since then most of our services are developed with the "white board approach" where the client is registered instead of the server (i.e. if we had to design the Http Service we would register an object modeling the servlet, not the web server). This allows different applications to pick up the same objects for different purposes. I think this matches your desired model exactly :-)

Kind regards,

	Peter Kriens



I am more interested in how to eventually use dynamic plugins to implement a
secure, updateable, extendable, and interoperable web service framework than
I am in the specifics of dynamic plugins themselves.   Implementing such a
web service framework for publishing web services, and client-side plugins
for consuming web services, is my goal for my JLense project.  This is where
my interests and the Equinox project overlap.  Besides, architecting dynamic
plugins will be the truly hard part of Equinox so I'm more than happy to
leave that to the real experts!


ted stockwell
jlense.sf.net