Bug 127439 - VE/EMF Problem while creating an AWT Dialog.
Summary: VE/EMF Problem while creating an AWT Dialog.
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: VE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: VE Bugzilla inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-13 04:36 EST by Kai Hackemesser CLA
Modified: 2011-06-13 11:36 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Hackemesser CLA 2006-02-13 04:36:33 EST
I was trying to create an AWT Dialog. This doesnt work, I assume this is the problem:

java.lang.NullPointerException
	at org.eclipse.emf.ecore.impl.EStructuralFeatureImpl.getSettingDelegate(EStructuralFeatureImpl.java:790)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSettingDelegate(BasicEObjectImpl.java:822)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicIsSet(BasicEObjectImpl.java:609)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eIsSet(BasicEObjectImpl.java:600)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:951)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XMLSaveImpl.java:2272)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:889)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2001)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1221)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElementID(XMLSaveImpl.java:2272)
	at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:78)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:478)
	at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:206)
	at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:193)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:893)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:813)
	at org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtility.doSaveCache(VEModelCacheUtility.java:158)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.doSave(JavaSourceTranslator.java:1358)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator$2.doRun(JavaSourceTranslator.java:923)
	at org.eclipse.ve.internal.java.codegen.util.ReverseParserJob.run(ReverseParserJob.java:56)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)


eclipse.buildId=M20050929-0840
java.version=1.5.0_06
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
Comment 1 Ed Merks CLA 2006-02-13 07:17:14 EST
I'll transfer this to VE.  I'll need a self contained reproducible test case to address this as an EMF problem.
Comment 2 Richard Kulp CLA 2006-02-13 10:00:18 EST
We've had some cache problems in VE. Please do the following:

Step up to Eclipse 3.2M4, EMF 2.2M4, GEF 3.2M4 and VE 1.2 I20060203. Then do the following to clear the cache.

1) Open a VE but then close it and all other VE's.
2) Do Project->Clean...->Clean All... and wait for the build to complete
3) Open the VE again and see if it now works.

Thanks.
Comment 3 Kai Hackemesser CLA 2006-02-14 01:34:09 EST
I followed your instructions. Finally, when opening the VE for my class nothing appears in the VE Pane, but I got exceptions in the error log:

org.eclipse.emf.common.util.WrappedException: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'size' not found. (file:/D:/eclipse%20workspaces/behr/.metadata/.plugins/org.eclipse.core.resources/.projects/GTA%205.0/org.eclipse.ve.java.core/.cache/emfmodel/eVistaDev/COM/BEHR/GTA/GUI/NewLoginDialog.xmi, 2, 7474)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:268)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:349)
	at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.getResource(ProjectResourceSetImpl.java:262)
	at org.eclipse.ve.internal.java.codegen.util.VEModelCacheUtility.doLoadFromCache(VEModelCacheUtility.java:103)
	at org.eclipse.ve.internal.java.codegen.core.VEModelInstance.createComposition(VEModelInstance.java:100)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.reConnect(JavaSourceTranslator.java:1117)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.decodeDocument(JavaSourceTranslator.java:895)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.loadModel(JavaSourceTranslator.java:590)
	at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEditorPart$Setup.run(JavaVisualEditorPart.java:1971)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'size' not found. (file:/D:/eclipse%20workspaces/behr/.metadata/.plugins/org.eclipse.core.resources/.projects/GTA%205.0/org.eclipse.ve.java.core/.cache/emfmodel/eVistaDev/COM/BEHR/GTA/GUI/NewLoginDialog.xmi, 2, 7474)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeature(XMLHandler.java:1632)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeature(XMLHandler.java:1602)
	at org.eclipse.emf.ecore.xmi.impl.XMIHandler.handleUnknownFeature(XMIHandler.java:102)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2331)
	at org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAttribs(SAXXMIHandler.java:74)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory(XMLHandler.java:1833)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTypeName(XMLHandler.java:1737)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHandler.java:1672)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLHandler.java:1489)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:793)
	at org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMIHandler.java:80)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:771)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:558)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533)
	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:330)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
	at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
	at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:162)
	at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:172)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1015)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:869)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:249)
	at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.demandLoad(ProjectResourceSetImpl.java:83)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:264)
	... 9 more


and anothoer:

java.lang.NullPointerException
	at org.eclipse.ve.internal.java.codegen.java.rules.DefaultVisitorFactoryRule.retrieveFromCache(DefaultVisitorFactoryRule.java:83)
	at org.eclipse.ve.internal.java.codegen.java.rules.DefaultVisitorFactoryRule.getTypeVisitor(DefaultVisitorFactoryRule.java:109)
	at org.eclipse.ve.internal.java.codegen.java.JavaBeanModelBuilder.visitType(JavaBeanModelBuilder.java:533)
	at org.eclipse.ve.internal.java.codegen.java.JavaBeanModelBuilder.build(JavaBeanModelBuilder.java:442)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.reverseParse(JavaSourceTranslator.java:850)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.decodeDocument(JavaSourceTranslator.java:932)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.loadModel(JavaSourceTranslator.java:590)
	at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEditorPart$Setup.run(JavaVisualEditorPart.java:1971)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)


eclipse.buildId=I20051215-1506
java.version=1.4.2_06
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
Comment 4 Richard Kulp CLA 2006-02-14 10:13:16 EST
I made a mistake. It should of been VE I20060202. The one I gave you is for working against Eclipse I20060131, not 3.2M4. 

But I don't think that is the problem. This still indicates a cache problem. Clean the cache one more time, please. 

But before you open the VE after cleaning the cache, erase the .log file. That way there won't be any stuff hanging around. This error shows it had written the cache at least once. That should not of occured on the first opening after a cache clear. Are you sure you opened a VE, closed ALL VE's, did a Project->Clean...->Clean ALL projects, waited for build to complete? This must be done in one Eclipse session, you mustn't close Eclipse down in between.
Comment 5 Kai Hackemesser CLA 2006-02-14 14:06:32 EST
I replaced the VE Build as you told. I interpret "open a VE" as "open a java file in VE Editor". I opened a VE, closed all editor panes, made a "clean all projects", opened the java file again in VE editor and got this result:


!ENTRY org.eclipse.ve.java.core 2 0 2006-02-14 20:00:40.362
!MESSAGE Exception thrown.
!STACK 0
java.lang.NullPointerException
	at org.eclipse.ve.internal.java.codegen.util.WorkingCopyProvider.getEditor(WorkingCopyProvider.java:96)
	at org.eclipse.ve.internal.java.codegen.util.WorkingCopyProvider.getDocument(WorkingCopyProvider.java:140)
	at org.eclipse.ve.internal.java.codegen.java.JavaSourceSynchronizer.connect(JavaSourceSynchronizer.java:226)
	at org.eclipse.ve.internal.java.codegen.java.JavaSourceSynchronizer.<init>(JavaSourceSynchronizer.java:99)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.reConnect(JavaSourceTranslator.java:1109)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.decodeDocument(JavaSourceTranslator.java:895)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.loadModel(JavaSourceTranslator.java:590)
	at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEditorPart$Setup.run(JavaVisualEditorPart.java:1971)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

!ENTRY org.eclipse.jdt.core 4 969 2006-02-14 20:00:40.402
!MESSAGE __projectWorkingcopy__ does not exist

Just another point: The default java editor pane looks strange in the 3.2M4 eclipse - I dont have line numbers, error marks, breakpoints in it anymore. 'F3' for Open declaration leads to Info-Message "The resource is not on the build path of a java project" (of course it is, it was all the time)
Comment 6 Richard Kulp CLA 2006-02-14 14:13:20 EST
This means your class is not within the source folder of the java project. Either your project is not a java project or your file is not within a source folder in the project. That would cause the NPE you are getting.
Comment 7 Kai Hackemesser CLA 2006-02-14 14:19:30 EST
The projects I have are all Java projects (I have the small 'J' over their icons, and in the project properties have Java Build path etc.) I have a source folder in it and the packages are listed correctly. So If there is something wrong I can't see it actually. there are no compile errors in the projects (at least not in the compile-ready ones)