Re: [mdt-bpmn2.dev] ItemDefinition's Import is transient ?

[Antoine Toulme <antoine@xxxxxxxxxxxxxxx>]

The spec has a serious problem on this: the import attribute is not in the schema, but it shows in the table of the attributes of Item Definition.

Our code uses StructureRef on Item Definition as an object, while the spec mentions it should be a qname, and casts it as an EObject.

I think we should leave import as it is, set structureRef as a qname, and later on the getImport method should be rewired to get the right Import object that matches the qname's prefix of the StructureRef attribute.

WDYT ?

On Wed, Sep 15, 2010 at 08:50, Henning Heitkötter <hheitkoetter@xxxxxxxxxxxxxx> wrote:

Hi Antoine,

I guess it's transient because this attribute is not supported by the XSD.
Apparently the specification does not mention a replacement - at least I couldn't find anything. Note that a normal reference by ID is not possible in XSD, because Import elements do not have an ID.

Regards,
Henning

2010/9/15 Antoine Toulme <antoine@xxxxxxxxxxxxxxx>

Not sure why, but it looks like the ItemDefinition's Import relationship is marked as transient.

Is that a bug or how do you persist the link between an ItemDefinition and an Import ?

I'll parse the spec for answers, and I'll change the setting to false if I don't find a better way.

Antoine

_______________________________________________
mdt-bpmn2.dev mailing list
mdt-bpmn2.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev