1. Generate an ArgoUML graphical model including a class 'A' having an attribute 'x' which is an enumerated list 'B'.
2. Export the model as XMI, convert to Ecore using argo2ecore, and attempt to create an EMF model from that. The process of "validating and converting the Ecore models" fails with this diagnostic detail: "The attribute 'A.x' is not transient so it must have a data type that is serializable"
3. If the attribute is changed to some other data type but the enumeration left in the model, the Ecore model is created successfully and the enumeration "Serializable" property is shown as "false".
I'm wondering whether this is a real bug or a problem with my modelling as enumerations are quite important and fairly basic, however I think I know what I'm doing (:-).
I'm planning a course centered on ArgoUML & Eclipse in a few months time so would really appreciate any advice.
Regards,
David
Logged In: YES
user_id=1830446
Originator: YES
I should have added that the "enumeration" shown in the Ecore model after conversion by argo2ecore is a [java.lang.Object] - presumably that's why it's not serializable. Also, I'm using ArgoUML 0.24 and wondering whether this behaves differently to version 0.22 when the green "new enumeration" icon is clicked.
The enumeration included in the test.zargo model at http://argo2ecore.sourceforge.net/ appears to work fine and is correctly mapped into an Ecore enumeration (though there seem to be a few other errors with test.zargo). However ArgoUML 0.24 shows it as a normal class with an <<enumeration>> annotation.
David