Home » Eclipse Projects » Equinox » extension (install) location and osgi-bundles
| extension (install) location and osgi-bundles [message #57985] |
Tue, 24 January 2006 15:16  |
Eclipse User |
|
|
|
Originally posted by: chs.tipas.at
the eclipse configuration defines installation extension location.
does equinox know about these locations, and can we install a bundle to a
specific location ??
thanks!
lg, chris
|
|
|
| Re: extension (install) location and osgi-bundles [message #58214 is a reply to message #57985] |
Thu, 26 January 2006 14:06  |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Equinox defines four "locations" , install, configuration, instance and
user. Each Location is registered as a service. See the runtime bundle's
Platform class for examples of how to get/use these services.
However, I'm not sure that this really is your question. What mechanism are
you using to install the bundle? Update manager? other? Or, when you stay
"install a bundle" do you mean call BundleContext.installBundle()?
Jeff
"Chris Schaefer" <chs@tipas.at> wrote in message
news:dr5gce$5l9$1@utils.eclipse.org...
> the eclipse configuration defines installation extension location.
>
> does equinox know about these locations, and can we install a bundle to a
> specific location ??
>
> thanks!
> lg, chris
>
>
|
|
|
| Re: extension (install) location and osgi-bundles [message #58437 is a reply to message #58214] |
Thu, 26 January 2006 16:17 |
| Eclipse User |
|
|
|
Originally posted by: chs.tipas.at
our application will put each form/dialog in its own osgi-bundle, similar to
a web-application and a web-page.
the plugin will be lazy downloaded when the dialog is required.
therefore it will be installed by downloading it from the server and it is
required to be installed as a osgi bundle directly by using
BundleContext.installBundle().
We would separate the base plugins and the dynamic plugins into several
extension/install locations.
the update manager, as far as i know it, does only provide full download and
pre-installation of a complete feature. the feature and extension point
shema is designed to load lazy from file, but not load lazy from server. ?
we do not know and we did not find any documentation about how the update
manager handles multiple install and extension locations.
thanks!
chris
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> schrieb im Newsbeitrag
news:dral0e$k8u$1@utils.eclipse.org...
> Equinox defines four "locations" , install, configuration, instance and
> user. Each Location is registered as a service. See the runtime bundle's
> Platform class for examples of how to get/use these services.
>
> However, I'm not sure that this really is your question. What mechanism
> are
> you using to install the bundle? Update manager? other? Or, when you
> stay
> "install a bundle" do you mean call BundleContext.installBundle()?
>
> Jeff
>
> "Chris Schaefer" <chs@tipas.at> wrote in message
> news:dr5gce$5l9$1@utils.eclipse.org...
>> the eclipse configuration defines installation extension location.
>>
>> does equinox know about these locations, and can we install a bundle to a
>> specific location ??
>>
>> thanks!
>> lg, chris
>>
>>
>
>
|
|
|
| Re: extension (install) location and osgi-bundles [message #58452 is a reply to message #58437] |
Thu, 26 January 2006 20:04 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Thanks for the clarification. You can think of features as just lists of
pluigns to install. If there happens to be only one pluign in the feature,
that is ok too. So you can wrap your individual bundles each in their own
feature and put them on an update site.
Sidenote: you do not have to list all available features in the update site
site.xml file. This file needs only to list the features you want users to
be able to see i the update UI.
Then you write some code that identifies and acquires, on demand, the
features that you want for the various dialogs etc.
As for multiple locations, I'm not sure. When you install a feature I
believe you can say where it should go. Eclipse itself (the runtime)
doesn't care where it goes as long as Update tells it.
Jeff
"Chris Schaefer" <chs@tipas.at> wrote in message
news:drasnf$47e$1@utils.eclipse.org...
>
> our application will put each form/dialog in its own osgi-bundle, similar
to
> a web-application and a web-page.
> the plugin will be lazy downloaded when the dialog is required.
>
> therefore it will be installed by downloading it from the server and it is
> required to be installed as a osgi bundle directly by using
> BundleContext.installBundle().
>
> We would separate the base plugins and the dynamic plugins into several
> extension/install locations.
>
> the update manager, as far as i know it, does only provide full download
and
> pre-installation of a complete feature. the feature and extension point
> shema is designed to load lazy from file, but not load lazy from server. ?
>
> we do not know and we did not find any documentation about how the update
> manager handles multiple install and extension locations.
>
> thanks!
>
> chris
>
>
>
>
> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> schrieb im Newsbeitrag
> news:dral0e$k8u$1@utils.eclipse.org...
> > Equinox defines four "locations" , install, configuration, instance and
> > user. Each Location is registered as a service. See the runtime
bundle's
> > Platform class for examples of how to get/use these services.
> >
> > However, I'm not sure that this really is your question. What mechanism
> > are
> > you using to install the bundle? Update manager? other? Or, when you
> > stay
> > "install a bundle" do you mean call BundleContext.installBundle()?
> >
> > Jeff
> >
> > "Chris Schaefer" <chs@tipas.at> wrote in message
> > news:dr5gce$5l9$1@utils.eclipse.org...
> >> the eclipse configuration defines installation extension location.
> >>
> >> does equinox know about these locations, and can we install a bundle to
a
> >> specific location ??
> >>
> >> thanks!
> >> lg, chris
> >>
> >>
> >
> >
>
>
|
|
|
| Re: extension (install) location and osgi-bundles [message #58663 is a reply to message #58452] |
Fri, 27 January 2006 08:14 |
| Eclipse User |
|
|
|
Originally posted by: chs.tipas.at
thank you for that information so far.
-> Due to the very high number of plugins, we thought of not using the
update manager at all, and install the bundles direclty
questions here are:
a.) how does the update manager tells equinox/osgi where to install the
bundles to in respect to different extension-installation locations ??
b.) who does scan the different install locations for available pluigin and
installs them on startup ?
c.) if we give BundleContext.install a remote url -> is the bundle copied to
the local disk into any install-location (directory) or simply downloaded
and cached in memory ?
more general questions:
..) where can we find more additional documentation (books) about such update
manager and equinox details ?
..) what is the direction of feature and update-manager development. what
kind of additional flexibility in respect to dynamic remote download and
installation will come ?
thanks
chris.
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> schrieb im Newsbeitrag
news:drba0e$re4$1@utils.eclipse.org...
> Thanks for the clarification. You can think of features as just lists of
> pluigns to install. If there happens to be only one pluign in the
> feature,
> that is ok too. So you can wrap your individual bundles each in their own
> feature and put them on an update site.
>
> Sidenote: you do not have to list all available features in the update
> site
> site.xml file. This file needs only to list the features you want users
> to
> be able to see i the update UI.
>
> Then you write some code that identifies and acquires, on demand, the
> features that you want for the various dialogs etc.
>
> As for multiple locations, I'm not sure. When you install a feature I
> believe you can say where it should go. Eclipse itself (the runtime)
> doesn't care where it goes as long as Update tells it.
>
> Jeff
>
> "Chris Schaefer" <chs@tipas.at> wrote in message
> news:drasnf$47e$1@utils.eclipse.org...
>>
>> our application will put each form/dialog in its own osgi-bundle, similar
> to
>> a web-application and a web-page.
>> the plugin will be lazy downloaded when the dialog is required.
>>
>> therefore it will be installed by downloading it from the server and it
>> is
>> required to be installed as a osgi bundle directly by using
>> BundleContext.installBundle().
>>
>> We would separate the base plugins and the dynamic plugins into several
>> extension/install locations.
>>
>> the update manager, as far as i know it, does only provide full download
> and
>> pre-installation of a complete feature. the feature and extension point
>> shema is designed to load lazy from file, but not load lazy from server.
>> ?
>>
>> we do not know and we did not find any documentation about how the update
>> manager handles multiple install and extension locations.
>>
>> thanks!
>>
>> chris
>>
>>
>>
>>
>> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> schrieb im Newsbeitrag
>> news:dral0e$k8u$1@utils.eclipse.org...
>> > Equinox defines four "locations" , install, configuration, instance and
>> > user. Each Location is registered as a service. See the runtime
> bundle's
>> > Platform class for examples of how to get/use these services.
>> >
>> > However, I'm not sure that this really is your question. What
>> > mechanism
>> > are
>> > you using to install the bundle? Update manager? other? Or, when you
>> > stay
>> > "install a bundle" do you mean call BundleContext.installBundle()?
>> >
>> > Jeff
>> >
>> > "Chris Schaefer" <chs@tipas.at> wrote in message
>> > news:dr5gce$5l9$1@utils.eclipse.org...
>> >> the eclipse configuration defines installation extension location.
>> >>
>> >> does equinox know about these locations, and can we install a bundle
>> >> to
> a
>> >> specific location ??
>> >>
>> >> thanks!
>> >> lg, chris
>> >>
>> >>
>> >
>> >
>>
>>
>
>
|
|
|
| Re: extension (install) location and osgi-bundles [message #58782 is a reply to message #58663] |
Sat, 28 January 2006 22:23 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
"Chris Schaefer" <chs@tipas.at> wrote in message
news:drckpf$lgu$1@utils.eclipse.org...
> a.) how does the update manager tells equinox/osgi where to install the
> bundles to in respect to different extension-installation locations ??
the extension locations etc are in fact Update notions. Update tells OSGi
where the bundles are after downloading and storing them where Update thinks
(or is told) they should be. This is the url given to installBundle()
> b.) who does scan the different install locations for available pluigin
and
> installs them on startup ?
It could be anyone (i.e, it is not a special operation). In the typical
case the org.eclipse.update.configurator plugin scans, discovers, and calls
installBundle.
> c.) if we give BundleContext.install a remote url -> is the bundle copied
to
> the local disk into any install-location (directory) or simply downloaded
> and cached in memory ?
Unless you use reference: URLs the framework always copies the bundle
content into a disk cache in the configuration area. If you use a
reference: url (as we always do), the bundles are expected to be in the
filesystem and are left in place. that is, they are just referenced.
> more general questions:
> .) where can we find more additional documentation (books) about such
update
> manager and equinox details ?
There is some information in the RCP book (http://eclipsercp.org). Perhaps
the Java Developers Guide to Eclipse
( http://www.awprofessional.com/bookstore/product.asp?isbn=032 1305027&rl=1)
has some info as well.
> .) what is the direction of feature and update-manager development. what
> kind of additional flexibility in respect to dynamic remote download and
> installation will come ?
Eclipse 3.2 includes some improvements in performance and robustness and a
few new features but it is largely the same design/mechanism as before.
Looking further down the road we are currently thinking about the
requirements. Various people have been enterning bugs and enhancement
requests with usecases, scenarios and proposed behaviour. We'll be looking
at that after 3.2 quiets down.
Jeff
|
|
|
Goto Forum:
Current Time: Sun Dec 22 05:37:41 GMT 2024
Powered by FUDForum. Page generated in 0.03690 seconds |
] 
Search
Help
Register
Login
Home
