Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Launcher for Equinox
David,

Regarding the part that you are using the config.ini, why do you remove that command line option on the subsequent launches? If you keep it there, then it will reuse the cache that it was built the last time under that configuration folder and you should achieve what you want; I am guessing that your config folder is different from "config", underneath where you run your command line, so the next time, after removing that command line option, it looks into the ./config/ directory and doesn't see anything there so it only starts the framework with no additional bundles.

You can also use launchers that are built as part of the equinox [1] if the binary for your hardware is available.

Ali.

[1] http://wiki.eclipse.org/index.php/Equinox_Launcher (I don't know how up-to-date this is but is a good starting point)

On 3/15/2010 11:24 AM, David Conde wrote:

Hi,

 

I am sorry if this is not the right place for this post, but I would appreciate the opinion and answers from people who know more about Equinox and different ways to launch it. What is it the most common way to launch Equinox without using Eclipse?

 

I have the next problem, I would like to have system bundles which are installed from the beggining, one of this bundles has the InstallerBundle role, so it is used in order to install another bundles by programming. Since I would like to achieve a fast deployment I start to use Pax Runner but I had to change this launcher because the persistence did not work fine here. I mean, if I installed a bundle in run time by using Pax Runner context  I have not found way to achieve persistence in the bundles which were installed in run time. The bundles’ states were not kept once I restarted Pax Runner.

 

On the other hand, I have tried by using config.ini file as it is said in [1]. But the problem here is that if I launch the command [2]  to load config.ini from CONFIG_INI_FOLDER the first time Equinox installs and starts the written bundles in config.ini in a right way. But if I want to launch Equinox by keeping the bundles’ state in the second launching by removing –configuration CONFIG_INI_FOLDER I just get the framework Equinox bundle installed instead of the other bundles from config.ini file.

 

 

How can I install a set of bundles automatically and then launch Equinox framework in order to keep the bundles’ states for the next running?

 

 

I would like on the one hand to have a simple and fast way to install and start a set of system bundles without to install one to one each bundle. On the other hand I would like to use this installation context to launch Equinox in normal way, I mean, where I could use the different capabilities that OSGi specification provides, keeping the bundles’s state, keeping as installed bundles those bundles which were installed programmatically, and so on.

How do you achieve this?

 

 

 

[1] http://www.eclipse.org/equinox/documents/quickstart.php

 

[2] java –jar org.eclipse.osgi_3.5.jar –console –configuration CONFIG_INI_FOLDER

 

 

Any idea will appreciated.

 

Thank you in advance

 

David

 


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Back to the top