| Early bundle start in an RCP application? [message #92622] |
Sun, 22 July 2007 20:03  |
Eclipse User |
|
|
|
Originally posted by: paul.paulgalbraith.net
I have a bundle in my RCP application (spring osgi extender) that I want
to start before the actual application bundle itself. What's the
recommended way to do this? It's a third party bundle, so I don't want
to touch the manifest. Should I manually change the config.ini and set
a lower start level? (Does that make sense, I'm already getting out of
my depth...)
Thanks for any suggestions,
Paul
|
|
|
| Re: Early bundle start in an RCP application? [message #92651 is a reply to message #92622] |
Mon, 23 July 2007 07:41  |
| Eclipse User |
|
|
|
Originally posted by: alex_blewitt.yahoo.com
Three possibilities;
1) Put an entry in the osgi.bundles property that says to start that bundle with a lower start priority than yours. However, note that the update.configurator basically starts everything, so you might want to be lower than that. But if you do, you've got to make sure you start your bundle's dependencies yourself.
2) Change your bundle so that it explicitly depends on that bundle (rather than import-package). This should ensure that your bundle doesn't get started before it (at least, I believe)
3) Set up your bundles to be more dynamic in nature; i.e. handle the bundles starting asynchronously rather than assuming that any bundle will be up at any time.
Alex.
|
|
|
Powered by
FUDForum. Page generated in 0.02650 seconds
] 
Search
Help
Register
Login
Home
