Community
Participate
Working Groups
The runtime should persist diagram information in a separate file from domain models, using XML/XMI capabilities of EMF in both cases.
Assigning to Steve's team
Sometimes I want store all model information in one file? Not two separate files. It should be possible to let desinger to choose the persistent way. Maybe some services(extensions) in GMF can deal with this case? (ps:I'm starting to learn GMF recently, it seems great but also a bit more complex^_^)
IMHO there should be the option both for separate and merged persistence For ex., I have requirements to upload/download all relevant to workflow definition information in one XML file
more exactly, I should upload/download (and locally save/open) the diagram (workglow definition) as one merged file but I should have a separate persistence for palette. Meanwhile, as I understand, palette elements should be also linked to semantic and non-semantic models, with corresponding instantion of this linked structures
would be nice to have it ASAP
You can refer to the logic example. This example stores the semantic model and diagram model in the same file resource.
Can't this be closed?
There are 2 variations: - logic example demonstrates how to store diagram and model in same file. - Generator example taipan shows how to separate diagram and model into separate resources.
[GMF Restructure] Bug 319140 : product GMF and component Runtime Diagram was the original product and component for this bug
