Bug 162669 - Visual classes are not displayed anymore
Summary: Visual classes are not displayed anymore
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-10-28 09:50 EDT by Harel Ben Attia CLA
Modified: 2011-06-13 11:37 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 Harel Ben Attia CLA 2006-10-28 09:50:00 EDT
No visual window is shown (for any of the visual classes). The only things that appear in the visual part are icons of "this" and "sShell" (without "X"s on them), and not error is shown in the status bar.

Looking at the log file, there a lot of exceptions, but they don't re-occur. They are just written the first time after an eclipse restart, but not afterwards.

The problem started happening after an eclipse crash. Cleaning the cache did not work. The problem remains.


!ENTRY org.eclipse.ve.java.core 4 0 2006-10-29 02:30:02.062
!MESSAGE Exception thrown.
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: -1
	at org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:514)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObjectForURIFragmentRootSegment(ResourceImpl.java:642)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObject(ResourceImpl.java:692)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObject(ResourceImpl.java:671)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.setValueFromId(XMLHandler.java:2511)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2439)
	at org.eclipse.emf.ecore.xmi.impl.SAXXMIHandler.handleObjectAttribs(SAXXMIHandler.java:74)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory(XMLHandler.java:1929)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromTypeName(XMLHandler.java:1833)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject(XMLHandler.java:1768)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLHandler.java:1576)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:876)
	at org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMIHandler.java:82)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:854)
	at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:626)
	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:179)
	at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:179)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1089)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:895)
	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)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:390)
	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:1134)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.decodeDocument(JavaSourceTranslator.java:910)
	at org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslator.loadModel(JavaSourceTranslator.java:597)
	at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEditorPart$Setup.run(JavaVisualEditorPart.java:1978)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)


!ENTRY org.eclipse.ve.java.core 2 0 2006-10-28 04:26:22.140
!MESSAGE Exception thrown.
!STACK 0
org.eclipse.ve.internal.java.core.IAllocationProcesser$AllocationException: java.lang.IllegalArgumentException: IWAV0177E Expression "ti" is too complicated. - ((LoadManagerNodeInfo)(ti.getData())).isClientSimulatorOpen()
	at org.eclipse.ve.internal.java.core.BasicAllocationProcesser.allocate(BasicAllocationProcesser.java:164)
	at org.eclipse.ve.internal.java.core.BasicAllocationProcesser.allocate(BasicAllocationProcesser.java:362)
	at org.eclipse.ve.internal.java.core.PrimitiveProxyAdapter.instantiateBeanProxy(PrimitiveProxyAdapter.java:287)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantiateSettingBean(BeanProxyAdapter.java:1011)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantiateSettingBean(BeanProxyAdapter.java:973)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.applySetting(BeanProxyAdapter.java:771)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.applied(BeanProxyAdapter.java:700)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter$5.isSet(BeanProxyAdapter.java:495)
	at org.eclipse.jem.internal.instantiation.base.JavaInstance.visitSetFeatures(JavaInstance.java:70)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.applyAllSettings(BeanProxyAdapter.java:485)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantiateAndInitialize(BeanProxyAdapter.java:463)
	at org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantiateBeanProxy(BeanProxyAdapter.java:328)
	at org.eclipse.ve.internal.java.core.MemberContainerProxyAdapter.initSetting(MemberContainerProxyAdapter.java:546)
	at org.eclipse.ve.internal.java.core.MemberContainerProxyAdapter.memberInitBeanProxy(MemberContainerProxyAdapter.java:621)
	at org.eclipse.ve.internal.java.core.MemberContainerProxyAdapter.memberInitBeanProxy(MemberContainerProxyAdapter.java:642)
	at org.eclipse.ve.internal.java.core.MemberContainerProxyAdapter.initBeanProxy(MemberContainerProxyAdapter.java:570)
	at org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEditorPart$Setup.run(JavaVisualEditorPart.java:2089)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: java.lang.IllegalArgumentException: IWAV0177E Expression "ti" is too complicated. - ((LoadManagerNodeInfo)(ti.getData())).isClientSimulatorOpen()
	at org.eclipse.jem.internal.instantiation.base.ParseTreeAllocationInstantiationVisitor.visit(ParseTreeAllocationInstantiationVisitor.java:398)
	at org.eclipse.jem.internal.instantiation.impl.PTInvalidExpressionImpl.accept0(PTInvalidExpressionImpl.java:162)
	at org.eclipse.jem.internal.instantiation.impl.PTExpressionImpl.childAccept0(PTExpressionImpl.java:126)
	at org.eclipse.jem.internal.instantiation.impl.PTExpressionImpl.accept(PTExpressionImpl.java:60)
	at org.eclipse.jem.internal.instantiation.base.ParseTreeAllocationInstantiationVisitor.getProxy(ParseTreeAllocationInstantiationVisitor.java:208)
	at org.eclipse.ve.internal.java.core.BasicAllocationProcesser.allocate(BasicAllocationProcesser.java:160)
	... 17 more
Comment 1 David Williams CLA 2007-09-19 15:12:23 EDT
As part of some general bugzilla cleanup, I am marking all old JEM bugs as "won't fix" simply because JEM is in maintenance mode, and there are no plans to fix these old bugs. 

If I have mistaken marked something that is still a current problem in the latests releases from WTP, please re-open. 

Comment 2 Philippe Ombredanne CLA 2007-09-19 19:33:51 EDT
Moving that bug to VE.