Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366350

Summary: Ecore to UML2 exporter ignores Default Value Literal
Product: [Modeling] MDT.UML2 Reporter: Stephen Egan <ftam_ftp>
Component: CoreAssignee: Kenn Hussey <Kenn.Hussey>
Status: VERIFIED FIXED QA Contact:
Severity: major    
Priority: P2 Flags: Kenn.Hussey: juno+
Version: unspecified   
Target Milestone: M6   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Stephen Egan CLA 2011-12-11 23:18:17 EST 
Build Identifier: Build id: 20110916-0149  org.eclipse.uml2.uml.ecore.exporter-2.4.100.v201008301510

When exporting an Ecore model to UML2, the Ecore "Default Value Literal" property value for a given EAttribute does not map to an equivalent "Default Value" element in UML2 model.  No warning/error dialog is displayed nor is there an entry in the workspace .log file.
This would suggest that this is not an error as such, but rather an omission.  Whether the omission is intentional or not, I cannot determine, however to me this seems like a mapping that should take place when exporting.

Reproducible: Always

Steps to Reproduce:
1. Create an Ecore Model with an EClass that has at least one EAttribute.
2. Give the EAttribute a default value by setting its "Default Value Literal" property to an appropriate (non-zero/non-null) value.
3. Create a generator model (.genmodel), and genertae model code.  Confirm that the default value is set in the generated code.
4. Export the model to a UML2 model using the "Export Model..." menu.
5. Confirm that the default value is not present within the generated UML2 model.
Comment 1 Kenn Hussey CLA 2012-01-08 20:54:23 EST 
This does indeed appear to be an omission.
Comment 2 Kenn Hussey CLA 2012-03-18 21:17:03 EDT 
A fix has been committed and pushed to git.
Comment 3 Kenn Hussey CLA 2012-03-18 21:55:53 EDT 
The fix is available in an integration build. The M6 milestone build will be published tomorrow (Monday).