Community
Participate
Working Groups
Created attachment 3488 [details] Source code as described in the Bug-Description
The attached zip contains the sources for an ActiveX control which can contain SWT widgets. The source could be devided into 4 parts: 1. SWT extension 2. Generic MFC ActiveX control 3. Jace patch 4. JavaCOMReg The SWT extension contains 4 classes which extend Display and Shell that they could be used inside an ActiveX control The generic ActiveX control is a blank container, which passes the windows messages to ActiveXDisplay and ActiveXShell in the correct way. The ActiveX control uses Jace (http://sourceforge.net/projects/jace) to to the JNI stuff. Because of the special requirements (see below) with Java and ActiveX, I did a small patch for Jace 1.1 beta2 (I submitted it some month ago to the Jace project, Toby Reyelts told me he will merge it into the codebase) JavaComReg: Because more than one SWT ActiveX control could be hosted by one process, but only on VM can be in one process, all Java ActiveXen need to share the same VM. Therefore it is necessary that they test if a VM is allready present (done in the Jace patch) and, because the classpath needs to be set when the VM is loaded for the first time (when you look at the SUN classloader code, you see that it needs not, but they sealed this opportunity by making the classloader final and protected), all Java ActiveXen need to register the jars they need, and the classpath needs to be build of this registry entries on the first startup
I will look at this after 2.1.
Are there any plans to implement this feature? This could help to migrate and gain more acceptance in c++/mfc centric organisations, since you could use new swt views in old c++ (or .NET) applications. You can than argue "swt/eclipse is not a one way street", weaken some fears against this new technology! :)
Currently, there is no plan to implement this support by the SWT team. You can create ActiveX controls in C++ using other tools and embed them in SWT using OleControlSite. This would be a good candidate for an external contribution. It is a self contained unit of functionality.
Your bug has been moved to triage, visit http://www.eclipse.org/swt/triage.php for more info.
This is a one-off bulk update. (The last one in the triage migration). Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process: https://wiki.eclipse.org/SWT/Devel/Triage See Bug 518478 for details. Tag for notification/mail filters: @TriageBulkUpdate
