| Re: [mdt-bpmn2.dev] ItemDefinition's Import is transient ? |
|
Hi Henning, hi Antoine, I think that having structureRef as EObject is ok and should be
changed.. I have even an example where the EObject is almost correctly resolved
from XSD schema. It is only a matter of how good our URIHandler works: It is
responsible to use the QName, find the corresponding Import, load the file and
resolve the reference. I don’t see why we need the “import” reference
for that resolution process – the Qname in the file is sufficient. BTW: The current implementation only work if the target
namespaces in the Import are unique. I think this is a valid assumption, even
if the only example from the Spec (the Correlation Example Seller) violates it.
Else we would need to have a global QName index, which would be quite time and
memory intentensive. Regards, Reiner. Von:
mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im
Auftrag von Antoine Toulme OK I'll change the model to use
a qname for now. Thanks for confirming. On Wed, Sep 15, 2010 at 09:03, Henning Heitkötter <hheitkoetter@xxxxxxxxxxxxxx>
wrote: Yes, judging from the "BPMN 2.0 by Example"
document, chapter 11, that's how it's supposed to work: structureRef as a QName
with a NS prefix pointing indirectly to the import element. 2010/9/15 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, 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 _______________________________________________ |