Bugzilla – Full Text Bug Listing
| Summary: | EEF generates wrong setup instructions for custom EMF Enums with unsettable=true | ||
|---|---|---|---|
| Product: | [Modeling] EEF | Reporter: | Markus <mail> |
| Component: | General | Assignee: | EEF Inbox <emft.eef-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | goulwen.lefur, sbouchet, stephane.begaudeau |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
HI, can you provide us your ecore model to reproduce this problem ? FIXED I am closing this issue since Goulwen has determined that it was fixed. |
As mentioned in the Summary I get the following code from the generator. The corresponding file ends with PropertiesEditingComponent.java if (isAccessible(messageViewsRepository.OUTPUTMESSAGETYPE.Properties.protocolType)) { basePart.initProtocolType((EEnum) messagePackage.eINSTANCE.getMESSAGETYPE_ProtocolType().getEType(), oUTPUTMESSAGETYPE.getProtocolType()); } When I change it to if (isAccessible(messageViewsRepository.OUTPUTMESSAGETYPE.Properties.protocolType)) { MESSAGEPROTOCOLTYPETYPE temp = oUTPUTMESSAGETYPE.getProtocolType(); if (temp == null) temp = MESSAGEPROTOCOLTYPETYPE.NOT_SPECIFIED; basePart.initProtocolType((EEnum) messagePackage.eINSTANCE.getMESSAGETYPE_ProtocolType().getEType(), temp); } it works okay. the NOT_SPECIFIED is not part of the enum but added by EMF if unsettable=true is set.