| VE properties tab is empty [message #96529] |
Thu, 07 July 2005 10:05  |
Eclipse User |
|
|
|
Originally posted by: ath.steinheim.com
When I click on a Shell-Object in the VE-view or the JavaBeans-Tab, the
properties-tab is empty. Instead I get the following errors in the
error-log:
!ENTRY org.eclipse.ui 4 4 2005-07-07 10:45:08.241
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 2005-07-07 10:45:08.241
!MESSAGE Failed to execute runnable (java.lang.ClassCastException:
org.eclipse.emf.ecore.impl.EClassImpl)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.ClassCastException: org.eclipse.emf.ecore.impl.EClassImpl)
at org.eclipse.swt.SWT.error(SWT.java:2942)
at org.eclipse.swt.SWT.error(SWT.java:2865)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:126)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3057)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2716)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.ClassCastException:
org.eclipse.emf.ecore.impl.EClassImpl
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.getBeanPr opertyValue(BeanProxyAdapter.java:1373)
at
org.eclipse.ve.internal.java.core.BeanPropertySourceAdapter. getPropertyValue(BeanPropertySourceAdapter.java:93)
at
org.eclipse.ve.internal.swt.WidgetPropertySourceAdapter.getP ropertyValue(WidgetPropertySourceAdapter.java:365)
at
org.eclipse.ve.internal.propertysheet.command.CommandStackPr opertySheetEntry.primGetValues(CommandStackPropertySheetEntr y.java:173)
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.refreshValues(AbstractPropertySheetEntry.java:892)
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.refreshChildEntries(AbstractPropertySheetEntry.java:823 )
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.setValues(AbstractPropertySheetEntry.java:1028)
at
org.eclipse.ui.views.properties.PropertySheetViewer.setInput (PropertySheetViewer.java:875)
at
org.eclipse.ui.views.properties.PropertySheetPage.selectionC hanged(PropertySheetPage.java:392)
at
org.eclipse.ve.internal.propertysheet.EToolsPropertySheetPag e.superSelectionChanged(EToolsPropertySheetPage.java:250)
at
org.eclipse.ve.internal.propertysheet.EToolsPropertySheetPag e.access$2(EToolsPropertySheetPage.java:243)
at
org.eclipse.ve.internal.propertysheet.EToolsPropertySheetPag e$1.run(EToolsPropertySheetPage.java:236)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
... 18 more
Am I doing something wrong, or is it a problem with VE?
Regards,
Andreas
|
|
|
|
|
|
|
|
|
| Re: Found a fix ... [message #97016 is a reply to message #96705] |
Fri, 08 July 2005 09:47  |
| Eclipse User |
|
|
|
Andreas Thierer wrote:
>
> Sorry, but I have worked on and can't reproduce the error - even with a
> new class. It seems like magic, but I can now switch between JDK 1.4.2
> and 1.5...
>
> Rich Kulp wrote:
>
>> Thanks for the info. We are trying to figure how to at least tolerate
>> 1.5 (i.e. ignore the things we don't understand like generics, enums,
>> and annotations) rather than crashing.
>
>
>> By the way, could you please append the class that was causing the
>> problem? That way we can test it out on our changes for 1.5 to make
>> sure it will work.
>
>
>
Did you file defined 1.5 annotation class? see https://bugs.eclipse.org/bugs/show_bug.cgi?id=76944
|
|
|
| Re: VE properties tab is empty [message #608986 is a reply to message #96529] |
Thu, 07 July 2005 10:09 |
| Eclipse User |
|
|
|
Originally posted by: ath.steinheim.com
Sorry, I forgot to post some further informations:
Eclipse Platform
Version: 3.1.0
Build id: I20050627-1435
Eclipse Graphical Editing Framework
Version: 3.1
Build id: 200506300200
Visual Editor
Version: 1.1.0
Build id: 200506301538
|
|
|
| Re: VE properties tab is empty [message #608987 is a reply to message #96545] |
Thu, 07 July 2005 11:08 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
We've never seen that and it shouldn't occur. What EMF are you using?
Also try
1) Bring up a VE editor
2) Close the editor
3) Do a Projects->Clean...->Clean all projects
4) Reopen the editor
I'm thinking they may be some old stuff laying around.
Andreas Thierer wrote:
> Sorry, I forgot to post some further informations:
>
> Eclipse Platform
> Version: 3.1.0
> Build id: I20050627-1435
>
> Eclipse Graphical Editing Framework
> Version: 3.1
> Build id: 200506300200
>
> Visual Editor
> Version: 1.1.0
> Build id: 200506301538
>
--
Thanks,
Rich Kulp
|
|
|
| Re: VE properties tab is empty [message #608989 is a reply to message #96558] |
Thu, 07 July 2005 12:08 |
| Eclipse User |
|
|
|
Originally posted by: ath.steinheim.com
Thanks for the quick answer. Project cleanup did not help.
BTW it's a new installation. Just Eclipse and VE.
Eclipse Modeling Framework (EMF)
Version: 2.1.0.I200506230200
Build id: 200506300200
When I simply open my project (a simple Shell, currently nothing more), VE
shows up but I get the following message in the error log:
Error 2005-07-07 13:06:05.691 Exception thrown.
java.lang.NullPointerException
at
org.eclipse.emf.ecore.impl.EStructuralFeatureImpl.getSetting Delegate(EStructuralFeatureImpl.java:790)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSettingDelegate (BasicEObjectImpl.java:822)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicIsSet(Ba sicEObjectImpl.java:609)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eIsSet(BasicEObj ectImpl.java:600)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLS aveImpl.java:951)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XML SaveImpl.java:2272)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSa veImpl.java:889)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany (XMLSaveImpl.java:2001)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLS aveImpl.java:1221)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XML SaveImpl.java:2272)
at
org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(X MISaveImpl.java:78)
at
org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveI mpl.java:478)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl. java:206)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLRes ourceImpl.java:193)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(Resour ceImpl.java:893)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(Resour ceImpl.java:813)
at
org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtilit y.doSaveCache(VEModelCacheUtility.java:158)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.doSave(JavaSourceTranslator.java:1349)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or$2.doRun(JavaSourceTranslator.java:917)
at
org.eclipse.ve.internal.java.codegen.util.ReverseParserJob.r un(ReverseParserJob.java:56)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
eclipse.buildId=I20050627-1435
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86
Regards,
Andreas
|
|
|
| Found a fix ... [message #608990 is a reply to message #96585] |
Thu, 07 July 2005 13:36 |
| Eclipse User |
|
|
|
Originally posted by: ath.steinheim.com
I simply changed the JDK compliance to 1.4 and pointed the active JDK to
1.4.2 instead of 1.5.
Greetings,
Andreas
|
|
|
| Re: Found a fix ... [message #608991 is a reply to message #96599] |
Thu, 07 July 2005 13:40 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Thanks for the info. We are trying to figure how to at least tolerate
1.5 (i.e. ignore the things we don't understand like generics, enums,
and annotations) rather than crashing.
By the way, could you please append the class that was causing the
problem? That way we can test it out on our changes for 1.5 to make sure
it will work.
Andreas Thierer wrote:
>
> I simply changed the JDK compliance to 1.4 and pointed the active JDK to
> 1.4.2 instead of 1.5.
>
> Greetings,
> Andreas
>
>
--
Thanks,
Rich Kulp
|
|
|
| Re: Found a fix ... [message #608997 is a reply to message #96614] |
Thu, 07 July 2005 14:48 |
| Eclipse User |
|
|
|
Originally posted by: ath.steinheim.com
Sorry, but I have worked on and can't reproduce the error - even with a
new class. It seems like magic, but I can now switch between JDK 1.4.2 and
1.5...
Rich Kulp wrote:
> Thanks for the info. We are trying to figure how to at least tolerate
> 1.5 (i.e. ignore the things we don't understand like generics, enums,
> and annotations) rather than crashing.
> By the way, could you please append the class that was causing the
> problem? That way we can test it out on our changes for 1.5 to make sure
> it will work.
|
|
|
| Re: Found a fix ... [message #609012 is a reply to message #96705] |
Fri, 08 July 2005 09:47 |
| Eclipse User |
|
|
|
Andreas Thierer wrote:
>
> Sorry, but I have worked on and can't reproduce the error - even with a
> new class. It seems like magic, but I can now switch between JDK 1.4.2
> and 1.5...
>
> Rich Kulp wrote:
>
>> Thanks for the info. We are trying to figure how to at least tolerate
>> 1.5 (i.e. ignore the things we don't understand like generics, enums,
>> and annotations) rather than crashing.
>
>
>> By the way, could you please append the class that was causing the
>> problem? That way we can test it out on our changes for 1.5 to make
>> sure it will work.
>
>
>
Did you file defined 1.5 annotation class? see https://bugs.eclipse.org/bugs/show_bug.cgi?id=76944
|
|
|
Powered by
FUDForum. Page generated in 0.27732 seconds
Home