[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mdt-bpmn2.dev] ItemDefinition.import transient?
- From: "Hille-Doering, Reiner" <reiner.hille-doering@xxxxxxx>
- Date: Fri, 13 Jul 2012 09:10:32 +0200
- Accept-language: de-DE, en-US
- Acceptlanguage: de-DE, en-US
- Delivered-to: email@example.com
- Thread-index: Ac1gxpdqy/SnO4J6TMOkRLwK/x8MHg==
- Thread-topic: [mdt-bpmn2.dev] ItemDefinition.import transient?
I'm on vacation, so I can't look into the source code right now. But I remember that I had some rule in the merge tool how to set the flags.
Transiient=false would mean that there is a MOF attribute in the metamodel that can't be persisted, propably because there is no equivalent in the XSD schema. If you say there is a representation of the reference in XSD, maybe there was simply a mapping missing during merge. You can try what happens if you change to true. But carefully check if the result is compliant to the XSD.
Am 10.07.2012 um 22:22 schrieb "Bob Brodt" <bbrodt@xxxxxxxxxx>:
> Hi all,
> I'm currently working on import functionality in the bpmn2 modeler. The goal is to automatically create Interface, Operation, Message, ItemDefinition, etc. elements (based on the type and contents of file being imported) as necessary.
> It would be nice to be able to reference the Import from an ItemDefinition such that, when an Import is removed, the ItemDefinitions that were created by that Import can be removed as well. The ItemDefinition does have an import reference, but this is marked as "transient" in the model. I can't think of any reason why this should be the case, and the BPMN2 spec. doesn't indicate that this is a transient or derived attribute.
> Is this a bug in the bpmn2 metamodel or am I missing something?
> Robert ("Bob") Brodt
> Senior Software Engineer
> JBoss by Red Hat
> mdt-bpmn2.dev mailing list