| Rationale for using Equinox [message #83439] |
Sat, 17 February 2007 17:13  |
Eclipse User |
|
|
|
Originally posted by: s0347354.sms.ed.ac.uk
I am writing a report and am trying to get my head around the reasons
for using Equinox's HTTP service (and other bundles) for hosting a web
application whose servlets interact with plugins of the Eclipse platform.
When the HTTP Service (and the underlying web server- Jetty) bundle is
started, does it exist in the same JVM as the Eclipse platform?
Is this the easiest/best (and only way) to interact with Eclipse plugins
from a java based web server, or are there other good options (I think
RPC or Java's RMI could also do the same job no?).
Thanks for any clarification/ pointers!
|
|
|
| Re: Rationale for using Equinox [message #83454 is a reply to message #83439] |
Sun, 18 February 2007 07:00  |
| Eclipse User |
|
|
|
Originally posted by: tonimenzel.gmx.de
Hi!
First quick answer to the first question: "..same VM.." yes
This is because equinox is basically an OSGi framework implementation
which in turn is all about a single VM.
The OSGi Framework describes itself as "the dynamic modul system for
Java" (www.osgi.org)
More detailed, the framework is divided into 4 layers with each of them
giving a certain benefit over traditional java approaches (details at
http://www.osgi.org/osgi_technology/index.asp?section=2)
The most advanced layer used in the eclipse world is probably the
module-layer which all about bundles and its dependencies to eachother.
(in eclipse world bundles are called plugins).
For the question "remoting question": sure, its usually not a bad
solution using remoting to separate layers but it depends on what kind
of functionality/plugins you are going to use from the eclipse platform.
This platform is basically an application-level on top of osgi providing
more coarse grained functionality.
You should know that that OSGi does not describe an application model
because it describes and does things on a very low level with fine
granularity.
At a low level, usually called modules or components, osgi/equinox
provides a proven architecture which rolls into the server-enterprise
class more and more. But those adopters are more things like containers
itself (tomcat,geronimo), application models like spring and of cause
the eclipse platform. You see, those adopters are all platforms itself.
At the end it depends on your specific application (how much are you
thinking of platforms) and on the part you want to use from eclipse
platform.
Googling for equinox and osgi give you lots of material for your report
to think about.. ;-)
kind regards, Toni
EdAcc schrieb:
> I am writing a report and am trying to get my head around the reasons
> for using Equinox's HTTP service (and other bundles) for hosting a web
> application whose servlets interact with plugins of the Eclipse platform.
>
> When the HTTP Service (and the underlying web server- Jetty) bundle is
> started, does it exist in the same JVM as the Eclipse platform?
>
> Is this the easiest/best (and only way) to interact with Eclipse plugins
> from a java based web server, or are there other good options (I think
> RPC or Java's RMI could also do the same job no?).
>
> Thanks for any clarification/ pointers!
|
|
|
| Re: Rationale for using Equinox [message #83467 is a reply to message #83454] |
Sun, 18 February 2007 07:31 |
| Eclipse User |
|
|
|
Originally posted by: s0347354.sms.ed.ac.uk
Thanks very much! That is plenty to get me started... I've googled a
fair bit, and you have clarified my understanding of the OSGi framework.
Thanks again!
Seba
Toni Menzel wrote:
> Hi!
>
> First quick answer to the first question: "..same VM.." yes
>
> This is because equinox is basically an OSGi framework implementation
> which in turn is all about a single VM.
> The OSGi Framework describes itself as "the dynamic modul system for
> Java" (www.osgi.org)
> More detailed, the framework is divided into 4 layers with each of them
> giving a certain benefit over traditional java approaches (details at
> http://www.osgi.org/osgi_technology/index.asp?section=2)
>
> The most advanced layer used in the eclipse world is probably the
> module-layer which all about bundles and its dependencies to eachother.
> (in eclipse world bundles are called plugins).
>
> For the question "remoting question": sure, its usually not a bad
> solution using remoting to separate layers but it depends on what kind
> of functionality/plugins you are going to use from the eclipse platform.
> This platform is basically an application-level on top of osgi providing
> more coarse grained functionality.
>
> You should know that that OSGi does not describe an application model
> because it describes and does things on a very low level with fine
> granularity.
> At a low level, usually called modules or components, osgi/equinox
> provides a proven architecture which rolls into the server-enterprise
> class more and more. But those adopters are more things like containers
> itself (tomcat,geronimo), application models like spring and of cause
> the eclipse platform. You see, those adopters are all platforms itself.
>
> At the end it depends on your specific application (how much are you
> thinking of platforms) and on the part you want to use from eclipse
> platform.
>
> Googling for equinox and osgi give you lots of material for your report
> to think about.. ;-)
>
> kind regards, Toni
>
> EdAcc schrieb:
>> I am writing a report and am trying to get my head around the reasons
>> for using Equinox's HTTP service (and other bundles) for hosting a web
>> application whose servlets interact with plugins of the Eclipse platform.
>>
>> When the HTTP Service (and the underlying web server- Jetty) bundle is
>> started, does it exist in the same JVM as the Eclipse platform?
>>
>> Is this the easiest/best (and only way) to interact with Eclipse
>> plugins from a java based web server, or are there other good options
>> (I think RPC or Java's RMI could also do the same job no?).
>>
>> Thanks for any clarification/ pointers!
|
|
|
Powered by
FUDForum. Page generated in 1.07807 seconds
Home