[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] How to use Extension bundles in equinox

The spec is pretty clear on terminating the VM in these situations however this can cause problems when embedding Equinox in another process.
I can't really see a way around this for bootclasspath extensions however for framework extensions I think we could just discard the framework class loader and re-start the whole launching process without exiting the VM. This might not be appropriate in all cases as there still would be potential for there to be global state hanging around however I'm a bit curious. Is this worth looking into in?
 
-Simon


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Thomas Watson
Sent: Tuesday, November 28, 2006 10:26 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] How to use Extension bundles in equinox


Yes the framework will relaunch, but you must launch with the eclipse.exe.  If a framework extension is refreshed then the Framework will exit with an exit code indicating to eclipse.exe that the framework should be relaunched in a new VM instance.

Note that updating/uninstalling framework extension bundles do not automatically cause the framework to relaunch.  The framework will only relaunch if PackageAdmin.refreshPackages is called and it causes a framework extension to be refreshed.

Tom




Ikuo Yamasaki <yamasaki.ikuo@xxxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

11/28/2006 07:41 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] How to use Extension bundles in equinox





Thanks for the reply, Tom.

I have a question left.

Will the framework shutdown and relaunch automatically when the
extension bundle is refreshed, updated, uninstalled., and so on as
described in Section 3.15 ?


On Mon, 27 Nov 2006 08:43:42 -0600
Thomas Watson <tjwatson@xxxxxxxxxx> wrote:

Thomas> Equinox currently does not support bootclassath extensions.  Framework
Thomas> extensions work like normal bundle fragments except they attach to the
Thomas> framework implementation (org.eclipse.osgi or system.bundle).
Thomas>
Thomas> Equinox also has additional support when you need a framework extension to
Thomas> provide framework adaptor hooks.  These types of framework extensions need
Thomas> to be loaded at the same time as the framework by startup.jar.  You can
Thomas> find more information about adaptor hooks at
Thomas> http://wiki.eclipse.org/index.php/Adaptor_Hooks
Thomas>
Thomas> Tom
Thomas>
Thomas>
Thomas>
Thomas>
Thomas>
Thomas> Ikuo Yamasaki <yamasaki.ikuo@xxxxxxxxxxxxx>
Thomas> Sent by: equinox-dev-bounces@xxxxxxxxxxx
Thomas> 11/25/2006 09:19 AM
Thomas> Please respond to
Thomas> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Thomas>
Thomas>
Thomas> To
Thomas> equinox-dev@xxxxxxxxxxx
Thomas> cc
Thomas>
Thomas> Subject
Thomas> [equinox-dev] How to use Extension bundles in equinox
Thomas>
Thomas>
Thomas>
Thomas>
Thomas>
Thomas>
Thomas> Hi,
Thomas>
Thomas> Is any document which explains how I can use "Extension Bundles"
Thomas> (framework-extension and bootclasspath-extension) in equinox available.
Thomas> If not, could anyone give information about it ?
Thomas>
Thomas> I know 3.15 Section of OSGi Spec R4 tells how a framework should perform
Thomas> and "How a framework configures itself or the boot class path to append
Thomas> the
Thomas> extension bundle's JAR is implementation specific." as described in
Thomas> 3.15.2.
Thomas>
Thomas> Best regards,
Thomas>
Thomas> =======
Thomas> Ikuo YAMASAKI
Thomas>
Thomas>
Thomas> _______________________________________________
Thomas> equinox-dev mailing list
Thomas> equinox-dev@xxxxxxxxxxx
Thomas> https://dev.eclipse.org/mailman/listinfo/equinox-dev
Thomas>

=======
Ikuo YAMASAKI


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

 
     This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.