Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Visual Editor (VE) » Problem with the properties view of VE 1.1.0.1
Problem with the properties view of VE 1.1.0.1 [message #108408] Thu, 29 September 2005 19:15 Go to next message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I just today installed VE 1.1.0.1 and wanted to try it out.
I am able to create a new visual composite class and add SWT widgets to it,
however no properties are shown in the Properties view if I select the
composite or child widget. The Properties seems to be the one used for VE as
there are special submenus like "Show null values" or "Show set values" and
I selected all these options, but nothing is shown.
When I read in the Help, it it written that after selecting the composite in
the design view, I should be able to set properties in the Properties view.
Any ideas?

Thomas

And something else: Can I make the palette permantly visible? Currently it
hidden at the right border of the window and opens as soon as I reach with
the mouse, but disappears again when I have made a selection - quite
nervous. Is there no way to make it stay there like a normal window?

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108428 is a reply to message #108408] Thu, 29 September 2005 19:24 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Is your target JDK at least 1.4.2? For SWT to work correctly in the VE
you need that level of JDK for your project.
--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108441 is a reply to message #108408] Thu, 29 September 2005 20:04 Go to previous messageGo to next message
hanys is currently offline hanysFriend
Messages: 188
Registered: July 2009
Senior Member
Hi,

what regards to hiding of the palette:
Click at the arrow placed at the top of the palete and palette will stay
shown until you next click at this arrow.

Best Regards,
John Caqe

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108453 is a reply to message #108441] Thu, 29 September 2005 20:46 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

You can also use it as a view so that it doesn't take up editor real
estate. Go to Show Views->Other->Basic->Palette. That way you can put
the palette anywhere.

John Cage wrote:
> Hi,
>
> what regards to hiding of the palette:
> Click at the arrow placed at the top of the palete and palette will stay
> shown until you next click at this arrow.
>
> Best Regards,
> John Caqe
>

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108466 is a reply to message #108428] Thu, 29 September 2005 22:36 Go to previous messageGo to next message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I use JDK 1.5.0.

"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhhf13$nq0$1@news.eclipse.org...
> Is your target JDK at least 1.4.2? For SWT to work correctly in the VE you
> need that level of JDK for your project.
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108510 is a reply to message #108466] Fri, 30 September 2005 14:11 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Did you just add SWT.jar to the build path or did you use the New Visual
Class Wizard to create an SWT class? You need to have the SWT Library
added, not the SWT jar.

Are there any errors in the .log file?

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108611 is a reply to message #108510] Sun, 02 October 2005 22:54 Go to previous messageGo to next message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I did use New Visual Class Wizard.

And yes, there seem to be error messages in the .log file:

!ENTRY org.eclipse.ui 4 4 2005-10-03 00:49:50.750
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2005-10-03 00:49:50.765
!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:1424)
at
org.eclipse.ve.internal.java.core.BeanPropertySourceAdapter. getPropertyValue(BeanPropertySourceAdapter.java:94)
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

Thanks,
Thomas


"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhjh1v$cc2$2@news.eclipse.org...
> Did you just add SWT.jar to the build path or did you use the New Visual
> Class Wizard to create an SWT class? You need to have the SWT Library
> added, not the SWT jar.
>
> Are there any errors in the .log file?
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108703 is a reply to message #108611] Mon, 03 October 2005 15:27 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Try changing the target JVM to 1.4.2 (in other words the java that the
project is compiled against). There have been some problems when
targeting 1.5.

Please let me know if that fixes the problem.


--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108797 is a reply to message #108703] Tue, 04 October 2005 12:31 Go to previous messageGo to next message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I'm not quite sure what you mean by "changing the targetJVM to 1.4.2" - is
there a way so change the JVM for just one project?

So what I did was creating a new workspace and importing the existing
project. Then I wanted to set the JRE to 1.4.2, but when I opened the
project, the property view worked fine with the JVM 1.5 - no need to change
the JVM.

Do you have another idea why it works in one workspace and not in another
when both workspaces are using the same JVM?

Thomas


"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhrik9$qet$1@news.eclipse.org...
> Try changing the target JVM to 1.4.2 (in other words the java that the
> project is compiled against). There have been some problems when targeting
> 1.5.
>
> Please let me know if that fixes the problem.
>
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108821 is a reply to message #108797] Tue, 04 October 2005 14:20 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

No clue. The error shown would cause the property sheet to be blank. But
I have no idea how you are getting the bad class. It just shouldn't happen.

Thomas Mauch wrote:
> I'm not quite sure what you mean by "changing the targetJVM to 1.4.2" - is
> there a way so change the JVM for just one project?

Yes there is a way to change for a particular project. You open the
properties on the project and go the java build page, select the Java
Runtime library and select edit. From there you can change the jvm.
>

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108834 is a reply to message #108821] Tue, 04 October 2005 14:34 Go to previous messageGo to next message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
Now it gets even more complicated. After switching back to the original
workspace (where the properties never worked), nothing related to VE seem to
work anymore. My class is no longer shown in the design view (it worked
before the workspace switching) and even the palette remains empty (it
worked before as well).

The following error show up in the log:

!ENTRY org.eclipse.jem.beaninfo 2 0 2005-10-04 16:26:08.333
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:08 CEST 2005 Build job waiting when
trying to start beaninfo registry. Possible race.

!ENTRY org.eclipse.jem.proxy 2 0 2005-10-04 16:26:21.536
!MESSAGE No Server to retrieve a connection.

!ENTRY org.eclipse.jem.beaninfo 2 0 2005-10-04 16:26:21.536
!MESSAGE IWAV0155E Introspection failed on class
"org.eclipse.swt.widgets.Widget." msg="."
!STACK 0
java.lang.IllegalStateException: IWAV0171E Could not create a socket
connection to remote vm.
at
org.eclipse.jem.internal.proxy.remote.REMProxyFactoryRegistr y.createConnection(REMProxyFactoryRegistry.java:440)
at
org.eclipse.jem.internal.proxy.remote.REMProxyFactoryRegistr y.getFreeConnection(REMProxyFactoryRegistry.java:375)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getBeanTypeProxy(REMStandardBeanTypeProxyFactory.j ava:364)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getBeanTypeProxy(REMStandardBeanTypeProxyFactory.j ava:271)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.introspect(BeaninfoClassAdapter.java:769)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.introspectIfNecessary(BeaninfoClassAdapter.java:474)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.introspectIfNecessary(BeaninfoClassAdapter.java:461)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.getEStructuralFeatures(BeaninfoClassAdapter.java:1088)
at
org.eclipse.jem.java.impl.JavaClassImpl.getEStructuralFeatur es(JavaClassImpl.java:394)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:371)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:368)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:368)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu resData(EClassImpl.java:629)
at
org.eclipse.emf.ecore.impl.EClassImpl.getFeatureCount(EClass Impl.java:641)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEStructuralFeature( EClassImpl.java:611)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeatureWitho utMap(XMLHelperImpl.java:817)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:769)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:812)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.getFeature(XMLHand ler.java:2074)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XML Handler.java:1825)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAtt ribs(SAXXMIHandler.java:147)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFa ctory(XMLHandler.java:1378)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTy peName(XMLHandler.java:1304)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHa ndler.java:1241)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1081)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:466)
at
org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMI Handler.java:65)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:449)
at
org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWr apper.java:73)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .startElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanStartElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(U nknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:140)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:169)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:977)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:832)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo ad(ResourceSetImpl.java:249)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.demandLoad(ProjectResourceSetImpl.java:83)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo adHelper(ResourceSetImpl.java:264)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResou rce(ResourceSetImpl.java:349)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.getResource(ProjectResourceSetImpl.java:262)
at
org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtilit y.doLoadFromCache(VEModelCacheUtility.java:103)
at
org.eclipse.ve.internal.java.codegen.core.VEModelInstance.cr eateComposition(VEModelInstance.java:100)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reConnect(JavaSourceTranslator.java:1099)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocument(JavaSourceTranslator.java:877)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(JavaSourceTranslator.java:575)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1881)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:23.130
!MESSAGE Exception thrown.
!STACK 0
java.util.ConcurrentModificationException
at
org.eclipse.emf.common.util.BasicEList$EIterator.checkModCou nt(BasicEList.java:1252)
at
org.eclipse.emf.common.util.BasicEList$EIterator.next(BasicE List.java:1206)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:367)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:368)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu resData(EClassImpl.java:629)
at
org.eclipse.emf.ecore.impl.EClassImpl.getFeatureCount(EClass Impl.java:641)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEStructuralFeature( EClassImpl.java:611)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeatureWitho utMap(XMLHelperImpl.java:817)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:769)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:812)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.getFeature(XMLHand ler.java:2074)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XML Handler.java:1825)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAtt ribs(SAXXMIHandler.java:147)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFa ctory(XMLHandler.java:1378)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTy peName(XMLHandler.java:1304)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHa ndler.java:1241)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1081)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:466)
at
org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMI Handler.java:65)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:449)
at
org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWr apper.java:73)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .startElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanStartElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(U nknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:140)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:169)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:977)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:832)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo ad(ResourceSetImpl.java:249)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.demandLoad(ProjectResourceSetImpl.java:83)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo adHelper(ResourceSetImpl.java:264)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResou rce(ResourceSetImpl.java:349)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.getResource(ProjectResourceSetImpl.java:262)
at
org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtilit y.doLoadFromCache(VEModelCacheUtility.java:103)
at
org.eclipse.ve.internal.java.codegen.core.VEModelInstance.cr eateComposition(VEModelInstance.java:100)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reConnect(JavaSourceTranslator.java:1099)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocument(JavaSourceTranslator.java:877)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(JavaSourceTranslator.java:575)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1881)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:26:24.224
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:24 CEST 2005 Skipping expression:
button1 = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:24.224
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:26:24.349
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:24 CEST 2005 Skipping expression: label
= new Label(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:24.349
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:26:24.396
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:24 CEST 2005 Skipping expression:
button = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:24.396
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:27:20.755
!MESSAGE
+++ Warning +++: Tue Oct 04 16:27:20 CEST 2005 Skipping expression:
button1 = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:27:20.755
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:27:20.771
!MESSAGE
+++ Warning +++: Tue Oct 04 16:27:20 CEST 2005 Skipping expression: label
= new Label(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:27:20.771
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:27:20.771
!MESSAGE
+++ Warning +++: Tue Oct 04 16:27:20 CEST 2005 Skipping expression:
button = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:27:20.771
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:28:04.271
!MESSAGE
+++ Warning +++: Tue Oct 04 16:28:04 CEST 2005 Skipping expression: label
= new Label(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:28:04.271
!MESSAGE Invalid PropertyDecorator

Changing the target JVM as you proposed changes nothing.
What shall I do?
Thomas



"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhu32u$adh$1@news.eclipse.org...
> No clue. The error shown would cause the property sheet to be blank. But I
> have no idea how you are getting the bad class. It just shouldn't happen.
>
> Thomas Mauch wrote:
>> I'm not quite sure what you mean by "changing the targetJVM to 1.4.2" -
>> is there a way so change the JVM for just one project?
>
> Yes there is a way to change for a particular project. You open the
> properties on the project and go the java build page, select the Java
> Runtime library and select edit. From there you can change the jvm.
>>
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108845 is a reply to message #108834] Tue, 04 October 2005 14:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

I don't know. One last thing to try.

1) Open a ve, it will fail but this is ok. Close all VE's that may be open.
2) Go to and select Project->Clean->Clean all projects.
3) Wait for build to complete
4) Try opening a ve again.

If it still fails then I don't know what to do. There is something
messed up in that workspace.

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #108928 is a reply to message #108845] Tue, 04 October 2005 21:31 Go to previous messageGo to next message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
After cleaning up as you suggested at least the design view and palette work
again. The properties view however does not work and the same errors appear
in the log again - even with the target JVM set to 1.4.2. How can a
workspace easily cleaned up or do you have any other suggestion? Should I
file a bug report?

Thomas


"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhu43r$ca8$1@news.eclipse.org...
>I don't know. One last thing to try.
>
> 1) Open a ve, it will fail but this is ok. Close all VE's that may be
> open.
> 2) Go to and select Project->Clean->Clean all projects.
> 3) Wait for build to complete
> 4) Try opening a ve again.
>
> If it still fails then I don't know what to do. There is something messed
> up in that workspace.
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #109049 is a reply to message #108928] Wed, 05 October 2005 19:22 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Can you zip up and send to me your workspace? Would you mind? There is
nothing I can think of that can cause this assuming your Eclipse
configuration is correct.

By the way, exactly what is installed in Eclipse?

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610890 is a reply to message #108408] Thu, 29 September 2005 19:24 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Is your target JDK at least 1.4.2? For SWT to work correctly in the VE
you need that level of JDK for your project.
--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610891 is a reply to message #108408] Thu, 29 September 2005 20:04 Go to previous message
hanys is currently offline hanysFriend
Messages: 188
Registered: July 2009
Senior Member
Hi,

what regards to hiding of the palette:
Click at the arrow placed at the top of the palete and palette will stay
shown until you next click at this arrow.

Best Regards,
John Caqe

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610892 is a reply to message #108441] Thu, 29 September 2005 20:46 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

You can also use it as a view so that it doesn't take up editor real
estate. Go to Show Views->Other->Basic->Palette. That way you can put
the palette anywhere.

John Cage wrote:
> Hi,
>
> what regards to hiding of the palette:
> Click at the arrow placed at the top of the palete and palette will stay
> shown until you next click at this arrow.
>
> Best Regards,
> John Caqe
>

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610893 is a reply to message #108428] Thu, 29 September 2005 22:36 Go to previous message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I use JDK 1.5.0.

"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhhf13$nq0$1@news.eclipse.org...
> Is your target JDK at least 1.4.2? For SWT to work correctly in the VE you
> need that level of JDK for your project.
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610896 is a reply to message #108466] Fri, 30 September 2005 14:11 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Did you just add SWT.jar to the build path or did you use the New Visual
Class Wizard to create an SWT class? You need to have the SWT Library
added, not the SWT jar.

Are there any errors in the .log file?

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610903 is a reply to message #108510] Sun, 02 October 2005 22:54 Go to previous message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I did use New Visual Class Wizard.

And yes, there seem to be error messages in the .log file:

!ENTRY org.eclipse.ui 4 4 2005-10-03 00:49:50.750
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2005-10-03 00:49:50.765
!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:1424)
at
org.eclipse.ve.internal.java.core.BeanPropertySourceAdapter. getPropertyValue(BeanPropertySourceAdapter.java:94)
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

Thanks,
Thomas


"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhjh1v$cc2$2@news.eclipse.org...
> Did you just add SWT.jar to the build path or did you use the New Visual
> Class Wizard to create an SWT class? You need to have the SWT Library
> added, not the SWT jar.
>
> Are there any errors in the .log file?
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610910 is a reply to message #108611] Mon, 03 October 2005 15:27 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Try changing the target JVM to 1.4.2 (in other words the java that the
project is compiled against). There have been some problems when
targeting 1.5.

Please let me know if that fixes the problem.


--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610917 is a reply to message #108703] Tue, 04 October 2005 12:31 Go to previous message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
I'm not quite sure what you mean by "changing the targetJVM to 1.4.2" - is
there a way so change the JVM for just one project?

So what I did was creating a new workspace and importing the existing
project. Then I wanted to set the JRE to 1.4.2, but when I opened the
project, the property view worked fine with the JVM 1.5 - no need to change
the JVM.

Do you have another idea why it works in one workspace and not in another
when both workspaces are using the same JVM?

Thomas


"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhrik9$qet$1@news.eclipse.org...
> Try changing the target JVM to 1.4.2 (in other words the java that the
> project is compiled against). There have been some problems when targeting
> 1.5.
>
> Please let me know if that fixes the problem.
>
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610919 is a reply to message #108797] Tue, 04 October 2005 14:20 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

No clue. The error shown would cause the property sheet to be blank. But
I have no idea how you are getting the bad class. It just shouldn't happen.

Thomas Mauch wrote:
> I'm not quite sure what you mean by "changing the targetJVM to 1.4.2" - is
> there a way so change the JVM for just one project?

Yes there is a way to change for a particular project. You open the
properties on the project and go the java build page, select the Java
Runtime library and select edit. From there you can change the jvm.
>

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610920 is a reply to message #108821] Tue, 04 October 2005 14:34 Go to previous message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
Now it gets even more complicated. After switching back to the original
workspace (where the properties never worked), nothing related to VE seem to
work anymore. My class is no longer shown in the design view (it worked
before the workspace switching) and even the palette remains empty (it
worked before as well).

The following error show up in the log:

!ENTRY org.eclipse.jem.beaninfo 2 0 2005-10-04 16:26:08.333
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:08 CEST 2005 Build job waiting when
trying to start beaninfo registry. Possible race.

!ENTRY org.eclipse.jem.proxy 2 0 2005-10-04 16:26:21.536
!MESSAGE No Server to retrieve a connection.

!ENTRY org.eclipse.jem.beaninfo 2 0 2005-10-04 16:26:21.536
!MESSAGE IWAV0155E Introspection failed on class
"org.eclipse.swt.widgets.Widget." msg="."
!STACK 0
java.lang.IllegalStateException: IWAV0171E Could not create a socket
connection to remote vm.
at
org.eclipse.jem.internal.proxy.remote.REMProxyFactoryRegistr y.createConnection(REMProxyFactoryRegistry.java:440)
at
org.eclipse.jem.internal.proxy.remote.REMProxyFactoryRegistr y.getFreeConnection(REMProxyFactoryRegistry.java:375)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getBeanTypeProxy(REMStandardBeanTypeProxyFactory.j ava:364)
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanTypePro xyFactory.getBeanTypeProxy(REMStandardBeanTypeProxyFactory.j ava:271)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.introspect(BeaninfoClassAdapter.java:769)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.introspectIfNecessary(BeaninfoClassAdapter.java:474)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.introspectIfNecessary(BeaninfoClassAdapter.java:461)
at
org.eclipse.jem.internal.beaninfo.adapters.BeaninfoClassAdap ter.getEStructuralFeatures(BeaninfoClassAdapter.java:1088)
at
org.eclipse.jem.java.impl.JavaClassImpl.getEStructuralFeatur es(JavaClassImpl.java:394)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:371)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:368)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:368)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu resData(EClassImpl.java:629)
at
org.eclipse.emf.ecore.impl.EClassImpl.getFeatureCount(EClass Impl.java:641)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEStructuralFeature( EClassImpl.java:611)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeatureWitho utMap(XMLHelperImpl.java:817)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:769)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:812)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.getFeature(XMLHand ler.java:2074)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XML Handler.java:1825)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAtt ribs(SAXXMIHandler.java:147)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFa ctory(XMLHandler.java:1378)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTy peName(XMLHandler.java:1304)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHa ndler.java:1241)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1081)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:466)
at
org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMI Handler.java:65)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:449)
at
org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWr apper.java:73)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .startElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanStartElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(U nknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:140)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:169)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:977)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:832)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo ad(ResourceSetImpl.java:249)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.demandLoad(ProjectResourceSetImpl.java:83)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo adHelper(ResourceSetImpl.java:264)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResou rce(ResourceSetImpl.java:349)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.getResource(ProjectResourceSetImpl.java:262)
at
org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtilit y.doLoadFromCache(VEModelCacheUtility.java:103)
at
org.eclipse.ve.internal.java.codegen.core.VEModelInstance.cr eateComposition(VEModelInstance.java:100)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reConnect(JavaSourceTranslator.java:1099)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocument(JavaSourceTranslator.java:877)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(JavaSourceTranslator.java:575)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1881)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:23.130
!MESSAGE Exception thrown.
!STACK 0
java.util.ConcurrentModificationException
at
org.eclipse.emf.common.util.BasicEList$EIterator.checkModCou nt(BasicEList.java:1252)
at
org.eclipse.emf.common.util.BasicEList$EIterator.next(BasicE List.java:1206)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:367)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu res(EClassImpl.java:368)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEAllStructuralFeatu resData(EClassImpl.java:629)
at
org.eclipse.emf.ecore.impl.EClassImpl.getFeatureCount(EClass Impl.java:641)
at
org.eclipse.emf.ecore.impl.EClassImpl.getEStructuralFeature( EClassImpl.java:611)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeatureWitho utMap(XMLHelperImpl.java:817)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:769)
at
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getFeature(XMLH elperImpl.java:812)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.getFeature(XMLHand ler.java:2074)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XML Handler.java:1825)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAtt ribs(SAXXMIHandler.java:147)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFa ctory(XMLHandler.java:1378)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTy peName(XMLHandler.java:1304)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHa ndler.java:1241)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLH andler.java:1081)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XML Handler.java:466)
at
org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMI Handler.java:65)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHa ndler.java:449)
at
org.eclipse.emf.ecore.xmi.impl.SAXWrapper.startElement(SAXWr apper.java:73)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .startElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanStartElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentS cannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuratio n.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(U nknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser .parse(Unknown
Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl. java:140)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLRes ourceImpl.java:169)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:977)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(Resour ceImpl.java:832)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo ad(ResourceSetImpl.java:249)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.demandLoad(ProjectResourceSetImpl.java:83)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLo adHelper(ResourceSetImpl.java:264)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResou rce(ResourceSetImpl.java:349)
at
org.eclipse.jem.internal.util.emf.workbench.ProjectResourceS etImpl.getResource(ProjectResourceSetImpl.java:262)
at
org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtilit y.doLoadFromCache(VEModelCacheUtility.java:103)
at
org.eclipse.ve.internal.java.codegen.core.VEModelInstance.cr eateComposition(VEModelInstance.java:100)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.reConnect(JavaSourceTranslator.java:1099)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocument(JavaSourceTranslator.java:877)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(JavaSourceTranslator.java:575)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1881)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:26:24.224
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:24 CEST 2005 Skipping expression:
button1 = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:24.224
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:26:24.349
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:24 CEST 2005 Skipping expression: label
= new Label(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:24.349
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:26:24.396
!MESSAGE
+++ Warning +++: Tue Oct 04 16:26:24 CEST 2005 Skipping expression:
button = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:26:24.396
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:27:20.755
!MESSAGE
+++ Warning +++: Tue Oct 04 16:27:20 CEST 2005 Skipping expression:
button1 = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:27:20.755
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:27:20.771
!MESSAGE
+++ Warning +++: Tue Oct 04 16:27:20 CEST 2005 Skipping expression: label
= new Label(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:27:20.771
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:27:20.771
!MESSAGE
+++ Warning +++: Tue Oct 04 16:27:20 CEST 2005 Skipping expression:
button = new Button(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:27:20.771
!MESSAGE Invalid PropertyDecorator

!ENTRY org.eclipse.ve.java.core 2 0 2005-10-04 16:28:04.271
!MESSAGE
+++ Warning +++: Tue Oct 04 16:28:04 CEST 2005 Skipping expression: label
= new Label(this, SWT.NONE)

!ENTRY org.eclipse.ve.java.core 4 0 2005-10-04 16:28:04.271
!MESSAGE Invalid PropertyDecorator

Changing the target JVM as you proposed changes nothing.
What shall I do?
Thomas



"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhu32u$adh$1@news.eclipse.org...
> No clue. The error shown would cause the property sheet to be blank. But I
> have no idea how you are getting the bad class. It just shouldn't happen.
>
> Thomas Mauch wrote:
>> I'm not quite sure what you mean by "changing the targetJVM to 1.4.2" -
>> is there a way so change the JVM for just one project?
>
> Yes there is a way to change for a particular project. You open the
> properties on the project and go the java build page, select the Java
> Runtime library and select edit. From there you can change the jvm.
>>
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610921 is a reply to message #108834] Tue, 04 October 2005 14:37 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

I don't know. One last thing to try.

1) Open a ve, it will fail but this is ok. Close all VE's that may be open.
2) Go to and select Project->Clean->Clean all projects.
3) Wait for build to complete
4) Try opening a ve again.

If it still fails then I don't know what to do. There is something
messed up in that workspace.

--
Thanks,
Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610928 is a reply to message #108845] Tue, 04 October 2005 21:31 Go to previous message
Thomas Mauch is currently offline Thomas MauchFriend
Messages: 30
Registered: July 2009
Member
After cleaning up as you suggested at least the design view and palette work
again. The properties view however does not work and the same errors appear
in the log again - even with the target JVM set to 1.4.2. How can a
workspace easily cleaned up or do you have any other suggestion? Should I
file a bug report?

Thomas


"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> schrieb im Newsbeitrag
news:dhu43r$ca8$1@news.eclipse.org...
>I don't know. One last thing to try.
>
> 1) Open a ve, it will fail but this is ok. Close all VE's that may be
> open.
> 2) Go to and select Project->Clean->Clean all projects.
> 3) Wait for build to complete
> 4) Try opening a ve again.
>
> If it still fails then I don't know what to do. There is something messed
> up in that workspace.
>
> --
> Thanks,
> Rich Kulp

Report message to a moderator

Re: Problem with the properties view of VE 1.1.0.1 [message #610938 is a reply to message #108928] Wed, 05 October 2005 19:22 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Can you zip up and send to me your workspace? Would you mind? There is
nothing I can think of that can cause this assuming your Eclipse
configuration is correct.

By the way, exactly what is installed in Eclipse?

--
Thanks,
Rich Kulp

Report message to a moderator

Previous Topic:Cannot use "New Visual Class" wizard
Next Topic:VE on MacOSX
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Apr 26 12:52:27 GMT 2024

Powered by FUDForum. Page generated in 0.07888 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly