| RCP Application Management [message #38368] |
Tue, 23 March 2004 07:25  |
Eclipse User |
|
|
|
Originally posted by: amottadelli.it.ibm.comnospam
The following article on OSGI
http://www-106.ibm.com/developerworks/wireless/library/wi-os gi/index.html
says:
"The Open Service Gateway initiative (OSGi) framework provides a Java
technology-based lightweight (fully J2ME-compatible) container for
dynamic software components. It handles the interactions between
components and allows developers to remotely manage the entire
application life cycle, including over-the-network deployment and updating."
This sound very interesting.
How can I understand more on RCP application management scenarios and
how it compares/interact with other lightweight distribution
technologies (applets, webstart..... ) ?
Many thanks in advance and best regards,
Alessandro Mottadelli
|
|
|
|
| Re: RCP Application Management [message #38720 is a reply to message #38368] |
Sat, 27 March 2004 01:27  |
| Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
Here is a first shot at an answer. More can probably be said.
Webstart and applets are two technologies providing a way to deliver, in
a pull mode, a piece of code (application) on a client machine. It
simply makes the assumption that java is on the client.
In the case of RCP, the base required is no longer java, but java and at
least osgi and eclipse runtime. Therefore, applets and webstart are not
technology that can be used to get individual plugins inside an RCP base
existing (at least from my knowledge of those techno).
That said, RCP comes with its own mechanism to get plugins down on a
client. This is named "install/update". It works around the notion of
features, a referential model that indicates which plugins must be
installed. Owing to it, a plugin can be dynamically installed as the
application run.
This was for the high level support which forces you to use features and
an update site, however if you don't want to use features there is more.
Since eclipse is based on osgi, you can use APIs such has
bundleContext#install / update / uninstall. This is the lowest level of
control you can get. With these you can write your own install agent.
Actually install/update uses these APIs.
I just covered the case of plugins dynamically installed within the
platform. Of course, since eclipse is a Java app, nothing prevents you
to use Webstart (or applets?) to deliver an RCP based application on a
client machine.
HTH,
PaScaL
Alessandro Mottadelli wrote:
> The following article on OSGI
> http://www-106.ibm.com/developerworks/wireless/library/wi-os gi/index.html
>
> says:
>
> "The Open Service Gateway initiative (OSGi) framework provides a Java
> technology-based lightweight (fully J2ME-compatible) container for
> dynamic software components. It handles the interactions between
> components and allows developers to remotely manage the entire
> application life cycle, including over-the-network deployment and
> updating."
>
> This sound very interesting.
> How can I understand more on RCP application management scenarios and
> how it compares/interact with other lightweight distribution
> technologies (applets, webstart..... ) ?
>
> Many thanks in advance and best regards,
> Alessandro Mottadelli
|
|
|
Powered by
FUDForum. Page generated in 0.02860 seconds
] 
Search
Help
Register
Login
Home
