| Summary: | Required property in a Workbench model | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Yves YANG <yves.yang> |
| Component: | UI | Assignee: | Project Inbox <e4.ui-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Eric Moffatt <emoffatt> |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Yves YANG
Yves, if we were to do this would we still be able to use the various 'xxxFactoryImpl.eINSTANCE.create<xxx>()' methods? Does the generator change these methods to have constructor args? If not then the initially created element (say MPart) would be broken under the contract since the 'contributionURI' wouldn't be defined. (In reply to comment #1) > Yves, if we were to do this would we still be able to use the various > 'xxxFactoryImpl.eINSTANCE.create<xxx>()' methods? Yes. The change of lowBound of eStructureFeature from 0 to 1 doesn't impact the generated Java APIs. > Does the generator change these methods to have constructor args? Neither. > > If not then the initially created element (say MPart) would be broken under the > contract since the 'contributionURI' wouldn't be defined. Here is the list of features I found, whose lowbound should be 1. Application Package ==================== ApplicationElement -> elementId StringToStringMap -> key Contribution -> contributionURI Commands Package ==================== BindingContext -> name Command -> commandName KeyBinding -> command Parameter -> name UI Package ==================== Input -> inputURI UILable -> label Menu Package ==================== HandledItem -> command UILable -> label Decriptor.Basic Package ==================== PartDescriptor -> contributionURI (In reply to comment #3) > Contribution -> contributionURI This should be removed from list (ref comment #1 about MPart) This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This is a mass change to close all e4 bugs marked with "stalebug" whiteboard. If this bug is still valid, please reopen and remove the "stalebug" keyword. |