| SWT 2.1 Support [message #61990] |
Mon, 27 September 2004 22:18  |
Eclipse User |
|
|
|
Originally posted by: stefan.baramov.trx.com
Does VE 1.0 support SWT 2.1 ?
Because, trying to open the VE with a composite with SWT 2.1 in the
class path failed with NullPointerException.
The stack trace :
Error Sep 27, 2004 18:02:45.65 Exception thrown.
java.lang.NullPointerException
at
org.eclipse.jem.internal.proxy.swt.JavaStandardSWTBeanConsta nts.getDisplayProxy(JavaStandardSWTBeanConstants.java:117)
at
org.eclipse.jem.internal.proxy.swt.JavaStandardSWTBeanConsta nts.invokeSyncExec(JavaStandardSWTBeanConstants.java:135)
at
org.eclipse.ve.internal.swt.WidgetProxyAdapter.invokeSyncExe c(WidgetProxyAdapter.java:65)
at
org.eclipse.ve.internal.swt.ControlProxyAdapter.basicInitial izationStringAllocation(ControlProxyAdapter.java:70)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.primInsta ntiateBeanProxy(BeanProxyAdapter.java:861)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(BeanProxyAdapter.java:755)
at
org.eclipse.ve.internal.swt.FreeFormControlHostAdapter.add(F reeFormControlHostAdapter.java:77)
at
org.eclipse.ve.internal.swt.ControlProxyAdapter.setTarget(Co ntrolProxyAdapter.java:330)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.didAdd(BasicNotifierImpl.java:71)
at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList. java:619)
at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:5 99)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.add(BasicNotifierImpl.java:115)
at
org.eclipse.emf.common.notify.impl.AdapterFactoryImpl.associ ate(AdapterFactoryImpl.java:161)
at
org.eclipse.emf.common.notify.impl.AdapterFactoryImpl.adaptN ew(AdapterFactoryImpl.java:113)
at
org.eclipse.emf.ecore.util.EcoreUtil.getRegisteredAdapter(Ec oreUtil.java:100)
at
org.eclipse.ve.internal.java.core.BeanProxyUtilities.getBean ProxyHost(BeanProxyUtilities.java:353)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itSetting(CompositionProxyAdapter.java:156)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itBeanProxy(CompositionProxyAdapter.java:119)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1488)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Session Data:
eclipse.buildId=I200406251208
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Eclipse 3.0.1
GEF 3.0.1
EMF 2.0.1
VE 1.0.1
The example source code:
package testVe;
import org.eclipse.swt.widgets.Composite;
import org.eclipse.swt.widgets.Button;
import org.eclipse.swt.SWT;
import org.eclipse.swt.layout.GridLayout;
public class TestComposite extends Composite {
private Button button = null;
private Button button1 = null;
public TestComposite(Composite parent, int style) {
super(parent, style);
initialize();
}
private void initialize() {
button = new Button(this, SWT.NONE);
button1 = new Button(this, SWT.NONE);
this.setLayout(new GridLayout());
setSize(new org.eclipse.swt.graphics.Point(300,200));
}
}
This exception might be related to the previous one:
Warning Sep 27, 2004 18:02:44.955
IWAV0073I *** RemoteVM Exception - Trace from Remote VM:
java.lang.UnsatisfiedLinkError: no swt-win32-2135 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1491)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:10 8)
at org.eclipse.swt.internal.win32.OS.<clinit>(OS.java:46)
at org.eclipse.swt.internal.win32.TCHAR.<clinit>(TCHAR.java:30)
at org.eclipse.swt.widgets.Widget.<clinit>(Widget.java:83)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
org.eclipse.jem.internal.proxy.vm.remote.ConnectionHandler.r un(ConnectionHandler.java:143)
at
org.eclipse.jem.internal.proxy.vm.remote.ConnectionThread.ru n(ConnectionThread.java:47)
IWAV0074I *** Local StackTrace:
org.eclipse.jem.internal.proxy.remote.REMThrowableBeanProxyP roxy:
java.lang.UnsatisfiedLinkError: no swt-win32-2135 in java.library.path
at
org.eclipse.jem.internal.proxy.remote.REMThrowableBeanTypePr oxy.createThrowableBeanProxy(REMThrowableBeanTypeProxy.java: 34)
at
org.eclipse.jem.internal.proxy.remote.REMThrowableBeanTypePr oxy.newBeanProxy(REMThrowableBeanTypeProxy.java:65)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanProxyFa ctory.getBeanProxy(REMStandardBeanProxyFactory.java:454)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanProxyFa ctory.processErrorReturn(REMStandardBeanProxyFactory.java:50 5)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getClassReturn(REMStandardBeanTypeProxyFactory.jav a:313)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.createBeanTypeProxy(REMStandardBeanTypeProxyFactor y.java:173)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getBeanTypeProxy(REMStandardBeanTypeProxyFactory.j ava:290)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getBeanTypeProxy(REMStandardBeanTypeProxyFactory.j ava:237)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.primInsta ntiateBeanProxy(BeanProxyAdapter.java:857)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(BeanProxyAdapter.java:755)
at
org.eclipse.ve.internal.swt.FreeFormControlHostAdapter.add(F reeFormControlHostAdapter.java:77)
at
org.eclipse.ve.internal.swt.ControlProxyAdapter.setTarget(Co ntrolProxyAdapter.java:330)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.didAdd(BasicNotifierImpl.java:71)
at org.eclipse.emf.common.util.BasicEList.addUnique(BasicEList. java:619)
at org.eclipse.emf.common.util.BasicEList.add(BasicEList.java:5 99)
at
org.eclipse.emf.common.notify.impl.BasicNotifierImpl$EAdapte rList.add(BasicNotifierImpl.java:115)
at
org.eclipse.emf.common.notify.impl.AdapterFactoryImpl.associ ate(AdapterFactoryImpl.java:161)
at
org.eclipse.emf.common.notify.impl.AdapterFactoryImpl.adaptN ew(AdapterFactoryImpl.java:113)
at
org.eclipse.emf.ecore.util.EcoreUtil.getRegisteredAdapter(Ec oreUtil.java:100)
at
org.eclipse.ve.internal.java.core.BeanProxyUtilities.getBean ProxyHost(BeanProxyUtilities.java:353)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itSetting(CompositionProxyAdapter.java:156)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itBeanProxy(CompositionProxyAdapter.java:119)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1488)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
So, from what I see, the VE creates a new JVM isntance to render the
GUI. If this is the case then it probably will be convenient to define
or customize the type of runtime library. Or provide support for
different SWT versions.
This could become a problem if I am using VE 1.0.1 (bundled with SWT
3.0.1) but working with project that have SWT 3.1 or 2.1.
I am sorry to say this, but having dependancy of SWT 3.0, renders the VE
useless for me because I develop and deploy on Eclipse 2.1. The project
will migrate to 3.0 eventually but this will not happen before the end
of the year.
Thanks,
Stefan
|
|
|
| Re: SWT 2.1 Support [message #62297 is a reply to message #61990] |
Tue, 28 September 2004 13:59  |
| Eclipse User |
|
|
|
Originally posted by: myersj.nospam.gmail.com
Hi Stefan,
We have planned for the ability to target versions of SWT other than
that used in the workbench, but that feature didn't make it into 1.0.
Hopefully it'll be addressed in the near future.
In the mean time, what are you planning on using in SWT 2.1 that's API
has significantly changed in 3.0? I would suggest developing using the
3.0 version of SWT, then checking the resulting code when running on 2.1.
Good Luck,
- Jeff
Stefan Baramov wrote:
> Does VE 1.0 support SWT 2.1 ?
>
> Because, trying to open the VE with a composite with SWT 2.1 in the
> class path failed with NullPointerException.
> So, from what I see, the VE creates a new JVM isntance to render the
> GUI. If this is the case then it probably will be convenient to define
> or customize the type of runtime library. Or provide support for
> different SWT versions.
>
> This could become a problem if I am using VE 1.0.1 (bundled with SWT
> 3.0.1) but working with project that have SWT 3.1 or 2.1.
>
> I am sorry to say this, but having dependancy of SWT 3.0, renders the VE
> useless for me because I develop and deploy on Eclipse 2.1. The project
> will migrate to 3.0 eventually but this will not happen before the end
> of the year.
>
> Thanks,
> Stefan
|
|
|
| Re: SWT 2.1 Support [message #63049 is a reply to message #62297] |
Wed, 29 September 2004 15:02 |
| Eclipse User |
|
|
|
Originally posted by: stefan.baramov.trx.com
Jeff:
I am targeting Eclipse Platform 2.1. I have very limited resources and
cannot spend time migrating to 3.0 right now. My goal is to release a
functional product. The Eclipse Platform 3.0 does not really offers any
significant advantages as long as my product is concerned. I will
probably migrate to 3.0 by the end of the year.
- Stefan
Jeff Myers wrote:
>
> In the mean time, what are you planning on using in SWT 2.1 that's API
> has significantly changed in 3.0? I would suggest developing using the
> 3.0 version of SWT, then checking the resulting code when running on 2.1.
>
> Good Luck,
> - Jeff
>
|
|
|
| Re: SWT 2.1 Support [message #63148 is a reply to message #63049] |
Wed, 29 September 2004 16:20 |
| Eclipse User |
|
|
|
Originally posted by: myersj.nospam.gmail.com
Stefan,
I didn't mean to suggest that you migrate your product to Eclipse 3.0
now, rather that that SWT API changes between 3.0 and 2.1 for the most
part aren't very significant. So you can develop SWT with VE targeting
SWT 3.0, and most likely it'll work fine if you bring the code back to
use it in SWT 2.1.
- Jeff
Stefan Baramov wrote:
> Jeff:
>
> I am targeting Eclipse Platform 2.1. I have very limited resources and
> cannot spend time migrating to 3.0 right now. My goal is to release a
> functional product. The Eclipse Platform 3.0 does not really offers any
> significant advantages as long as my product is concerned. I will
> probably migrate to 3.0 by the end of the year.
>
> - Stefan
>
>
> Jeff Myers wrote:
>
>>
>> In the mean time, what are you planning on using in SWT 2.1 that's API
>> has significantly changed in 3.0? I would suggest developing using
>> the 3.0 version of SWT, then checking the resulting code when running
>> on 2.1.
>>
>> Good Luck,
>> - Jeff
>>
|
|
|
| Re: SWT 2.1 Support [message #599885 is a reply to message #61990] |
Tue, 28 September 2004 13:59 |
 Jeff Myers
Messages: 396
Registered: July 2009 |
Senior Member |
|
|
Hi Stefan,
We have planned for the ability to target versions of SWT other than
that used in the workbench, but that feature didn't make it into 1.0.
Hopefully it'll be addressed in the near future.
In the mean time, what are you planning on using in SWT 2.1 that's API
has significantly changed in 3.0? I would suggest developing using the
3.0 version of SWT, then checking the resulting code when running on 2.1.
Good Luck,
- Jeff
Stefan Baramov wrote:
> Does VE 1.0 support SWT 2.1 ?
>
> Because, trying to open the VE with a composite with SWT 2.1 in the
> class path failed with NullPointerException.
> So, from what I see, the VE creates a new JVM isntance to render the
> GUI. If this is the case then it probably will be convenient to define
> or customize the type of runtime library. Or provide support for
> different SWT versions.
>
> This could become a problem if I am using VE 1.0.1 (bundled with SWT
> 3.0.1) but working with project that have SWT 3.1 or 2.1.
>
> I am sorry to say this, but having dependancy of SWT 3.0, renders the VE
> useless for me because I develop and deploy on Eclipse 2.1. The project
> will migrate to 3.0 eventually but this will not happen before the end
> of the year.
>
> Thanks,
> Stefan
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04708 seconds
] 
Search
Help
Register
Login
Home
