[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Starting equinox framework in program
- From: "林恺" <bmlinkai@xxxxxxxxx>
- Date: Thu, 4 Sep 2008 19:02:21 +0800
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=FN9AZoCdcwat+AL1z2jZsxxvM2Kck8SwcSKejMCnESA0T7Z4JRTdB6tFP5X6HNVPWm h16A1/ydJWsuSDi35hroT6X9zsK8nbY29gdSlX8xnft8SsYb45/HhqzM6yYRR2zTa5Da FzA37VcGzopwIYDwIeuaWr30JUecki+HWIAJE=
Thanks again. The reason why I did not install my plug-in in my application is: my application is not an RCP-based application, most of them might be headless application or web UI application. I developed this plug-in because I was building an IDE to support the development and monitor Equinox-based application, and my monitor plug-in is part of this IDE.
I have thought about using Runtime.exec() to start my another Equinox framework, but how can I get BundleContext using this method?
2008/9/4 Meng Xin Zhu <zhumx@xxxxxxxxxx>
Why not install those plug-ins in your application? Then your plug-in can be in charge of monitoring and manging those plug-ins. The EclipseStarter.startup you called in your plug-in that is the main function of your app. You can easily find that Equinox prevents the framework running again if it's running in the source code of EclipseStarter. If you want to start another Equinox framework, try Runtime.exec.