Bugzilla – Full Text Bug Listing
| Summary: | The RUIHandler and RUIWidget system parts are not up to date | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Joseph Vincens <jvincens> |
| Component: | EDT | Assignee: | Paul Harmon <pharmon> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Joseph Vincens
As near as I can tell, these parts are up to date. EDT uses a new definition for these stereoTypes named defaultSuperType. The defaultSuperType for RUIHandler is View and the defaultSuperType for RuiWidget is Widget. The source for both of these external types is defined in egl.ui.rui.ExternalTypes. If you find a specific field/function that needs to be added, please reopen this defect I get a stack trace in the error log during the compile because there is no initialUI field. Here is the missing field in RUIWidget org.eclipse.edt.compiler.internal.core.builder.BuildException: java.lang.IllegalArgumentException: No such field named: targetWidget in EClass egl.ui.rui.RUIWidget at org.eclipse.edt.compiler.internal.core.builder.AbstractProcessingQueue.process(AbstractProcessingQueue.java:187) at org.eclipse.edt.compiler.internal.core.builder.AbstractProcessingQueue.requestCompilationFor(AbstractProcessingQueue.java:248) at org.eclipse.edt.ide.core.internal.lookup.ProjectBuildPathEntry.getPartBinding(ProjectBuildPathEntry.java:149) at org.eclipse.edt.ide.core.internal.lookup.ProjectBuildPathEntry.getPartBinding(ProjectBuildPathEntry.java:137) at org.eclipse.edt.ide.core.internal.lookup.ProjectEnvironment.getPartBinding(ProjectEnvironment.java:97) at org.eclipse.edt.compiler.binding.PackageBinding.resolveType(PackageBinding.java:82) at org.eclipse.edt.compiler.internal.core.lookup.FileScope.findTypeInDeclaringPackage(FileScope.java:137) at org.eclipse.edt.compiler.internal.core.lookup.FileScope.findType(FileScope.java:105) at org.eclipse.edt.compiler.internal.core.lookup.SystemScope.findType(SystemScope.java:44) at org.eclipse.edt.compiler.internal.core.lookup.FunctionContainerScope.findType(FunctionContainerScope.java:337) at org.eclipse.edt.compiler.internal.core.lookup.FunctionScope.findType(FunctionScope.java:128) at org.eclipse.edt.compiler.internal.core.lookup.AbstractBinder.bindTypeName(AbstractBinder.java:138) at org.eclipse.edt.compiler.internal.core.lookup.AbstractBinder.bindTypeName(AbstractBinder.java:132) at org.eclipse.edt.compiler.internal.core.lookup.AbstractBinder.bindType(AbstractBinder.java:117) at org.eclipse.edt.compiler.internal.core.lookup.LocalVariableAndIOObjectBinder.processDataDeclaration(LocalVariableAndIOObjectBinder.java:181) at org.eclipse.edt.compiler.internal.core.lookup.LocalVariableAndIOObjectBinder.visit(LocalVariableAndIOObjectBinder.java:118) at org.eclipse.edt.compiler.core.ast.FunctionDataDeclaration.accept(FunctionDataDeclaration.java:76) at org.eclipse.edt.compiler.internal.core.lookup.LocalVariableAndIOObjectBinder.internalVisitStatement(LocalVariableAndIOObjectBinder.java:107) at org.eclipse.edt.compiler.core.ast.AbstractASTStatementVisitor.visit(AbstractASTStatementVisitor.java:112) at org.eclipse.edt.compiler.core.ast.IfStatement.accept(IfStatement.java:58) at org.eclipse.edt.compiler.core.ast.Node.acceptChildren(Node.java:83) at org.eclipse.edt.compiler.core.ast.NestedFunction.accept(NestedFunction.java:94) at org.eclipse.edt.compiler.internal.core.lookup.FunctionBinder.visit(FunctionBinder.java:160) at org.eclipse.edt.compiler.core.ast.NestedFunction.accept(NestedFunction.java:89) This is not a case of the fields being missing. The problem is that the binder is finding the fields in the defaultSuperType and is treating them as annotataions, rather than fields. This is causing the code that generates the mof to throw an exception when it attempts to find things like "targetWidget" or "initialUI". I have fixed this problem with the changes for Bug 350069. this is fixed |