Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » services vs. extension points, IAdaptable and rcp on the server side
services vs. extension points, IAdaptable and rcp on the server side [message #54166] Fri, 02 December 2005 16:34 Go to next message
Martin Schikowski is currently offline Martin SchikowskiFriend
Messages: 19
Registered: July 2009
Junior Member
Hello togehter,

for my thesis I have been working on for 2 month now, I have been dealing with the
problem of integrating equinox within a single
Tomcat-Webapplication to split
the whole webapplication in components and take advantage of the eclipse-runtime
functionalities (update, extensions...).

Now I have serveral questions I would ask you:
(1) What are the main differences between osgi-services, extension points and the IAdaptable-Pattern? For this a slide is available
which shows the service- and extension-point-approach. This slide derives from the presentation
of Jeff McAffer and Wayne Beaton with the topic "Building Rich Client Applications with
the Eclipse Rich Client Platform (RCP)", 2005-12-01. After registration you can get it here http://bzmedia.com/webseminar/seminar2215.htm.
The slide I refer to is slide no. 14 with the title "Plug-in Interactions. On this slide these two approches are separated by a red dashed line.
It seems on the slide that they have nothing in common. But as I have already programmed some testing apps
around equinox I know there is something they must have in common in my opinion:

For my understanding an extension point is similar to a service. A Plugin can register to
an extension point and contribute its functionality to it, it provides some add-on and symbolizes an extension.
"A guy wants functionality from me!" (after registration)

In contrast an osgi-service goes the contrary way: I request some functionality,
wich I can use and work with it further on. "I want functionality from another guy!"

The IAdaptable-Pattern seems to be a technical concept to realize the extension-point approach.

Could these statements be right?

My last question: Is it reasonable to integrate the eclipse-runtime the way I plan to do in my thesis? Might it be more effective/reasonable to
build up a totally new webapplication server fully based on equinox (eclipse-runtime + osgi) like maybe
tango (http://servicetango.sourceforge.net)? It might be more powerful.

-martin
Re: services vs. extension points, IAdaptable and rcp on the server side [message #54194 is a reply to message #54166] Sat, 03 December 2005 05:15 Go to previous message
Eclipse UserFriend
Originally posted by: skaegi.sympatico.ca

Hi Martin,

I'll leave discussion of services vs. extension points to someone else but I
can talk a bit about server side work.

There's been a fair bit of activity in the 3.2 stream to ensure that
use-cases like the one you describe are possible.
If you're interested and don't mind spelunking your way through a bunch of
code you should definitely take a look at:
1) org.eclipse.equinox.servlet.bridge
2) org.eclipse.equinox.servlet.http
3) org.eclipse.equinox.servlet.ext

These are projects in the equinox-incubator CVS that should let you embed
eclipse in a web application just like you describe.
Documentation is woefully inadequate right now but I'll put what I have up
on the server-side incubator site when I get a moment.
I'm working towards having a full set of instructions up in time for 3.2M4
as that will be the first supported stable build with the required changes
built in.
For now I'm working directly off of HEAD so if you're determined enough you
can set yourself up too.
(a recent 3.2 stream integration build should work too)

I would be incredibly appreciative to you (or anyone other brave souls)
willing to lend a hand and try out this stuff.
I'll keep a close watch and try and give help where needed.

As to your last question is this a reasonable approach... I definitely think
so. The other approach you describe (embedding an httpservice) also makes
sense and to date has been where the majority of effort has gone.

I use both, and do development embedding an httpservice in the Eclipse IDE
but for production run embedded in a J2EE Application Server.
In the end it really depends on your context and environmental requirements.

-Simon
--


"Martin Schikowski" <schikowski@gmx.de> wrote in message
news:18273153.1133541310024.JavaMail.root@cp1.javalobby.org...
> Hello togehter,
>
> for my thesis I have been working on for 2 month now, I have been dealing
with the
> problem of integrating equinox within a single
> Tomcat-Webapplication to split
> the whole webapplication in components and take advantage of the
eclipse-runtime
> functionalities (update, extensions...).
>
> Now I have serveral questions I would ask you:
> (1) What are the main differences between osgi-services, extension points
and the IAdaptable-Pattern? For this a slide is available
> which shows the service- and extension-point-approach. This slide derives
from the presentation
> of Jeff McAffer and Wayne Beaton with the topic "Building Rich Client
Applications with
> the Eclipse Rich Client Platform (RCP)", 2005-12-01. After registration
you can get it here http://bzmedia.com/webseminar/seminar2215.htm.
> The slide I refer to is slide no. 14 with the title "Plug-in Interactions.
On this slide these two approches are separated by a red dashed line.
> It seems on the slide that they have nothing in common. But as I have
already programmed some testing apps
> around equinox I know there is something they must have in common in my
opinion:
>
> For my understanding an extension point is similar to a service. A Plugin
can register to
> an extension point and contribute its functionality to it, it provides
some add-on and symbolizes an extension.
> "A guy wants functionality from me!" (after registration)
>
> In contrast an osgi-service goes the contrary way: I request some
functionality,
> wich I can use and work with it further on. "I want functionality from
another guy!"
>
> The IAdaptable-Pattern seems to be a technical concept to realize the
extension-point approach.
>
> Could these statements be right?
>
> My last question: Is it reasonable to integrate the eclipse-runtime the
way I plan to do in my thesis? Might it be more effective/reasonable to
> build up a totally new webapplication server fully based on equinox
(eclipse-runtime + osgi) like maybe
> tango (http://servicetango.sourceforge.net)? It might be more powerful.
>
> -martin
Previous Topic:relative library paths to jars outside of plugins
Next Topic:test
Goto Forum:
  


Current Time: Sat Jul 27 12:24:34 GMT 2024

Powered by FUDForum. Page generated in 0.02847 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top