ChrisH07
commented
6 years ago I'm trying to work on a solution to this problem, but I need assistance. It looks like the eAnnotations are lost by the time TransformationEngine.Transform gets called. Should we create a SerializedName property (where?) and assign a value in the appropriate transform (e.g. EReference2Property)? Something like this (not tested):
public class ENamedElement2MetaElement : AbstractTransformationRule<IENamedElement, IMetaElement>
{
public override void Transform(IENamedElement input, IMetaElement output, ITransformationContext context)
{
if (!(input is IEDataType) || (input is IEEnum))
{
output.Name = input.Name.ToString();
var extendedMetaData = input.EAnnotations.FirstOrDefault(o => o.Source.Equals("http:///org/eclipse/emf/ecore/util/ExtendedMetaData"));
if (extendedMetaData != null)
{
var name = extendedMetaData.Details.FirstOrDefault(o => o.Key.Equals("name"));
if (name != null)
{
output.SerializedName = name.Value.Replace("_._type", "");
}
}
}
}
}
public class Class2Type : ClassGenerator<IClass>
{
public override void Transform(IClass input, CodeTypeDeclaration generatedType, ITransformationContext context)
{
....
if (input.SerializedName != null)
{
generatedType.AddAttribute(typeof(XmlElementNameAttribute), input.SerializedName );
}
else if (input.Name != generatedType.Name)
{
generatedType.AddAttribute(typeof(XmlElementNameAttribute), input.Name);
}
}
}
georghinkel
When converting an Ecore model to NMeta (Ecore2Code) the generated classes and properties have the wrong name in the XmlElementNameAttribute attribute. This occurs when the Ecore model is generated from an XML schema. The rules defined in XML Schema To Ecore Mapping specify the serialized name in an eAnnotation where the source is http:///org/eclipse/emf/ecore/util/ExtendedMetaData.
Here is a simplified Ecore model demonstrating the issue:
Currently in Attribute2Property, Class2Type, and Reference2Property the XmlElementNameAttribute is only added when the input and output names don't match. For the example above the reference to PType in AnnotationDefaultsType will be generated as
instead of an uppercase P as specified in the "name" key in the annotation for the reference. Likewise the PType and AnnotationDefaultType classes should be have similar annotations based on their "name" keys (minus the _._type).