| [EMFStore] access to EditingDomain in EMFStore [message #1126710] |
Sat, 05 October 2013 18:19 |
 Scott Dybiec
Messages: 69
Registered: July 2009 |
Member |
|
|
I have an EMF-based RCP application that looks like a good fit for
EMFStore. The offline-by-design capability is particularly attractive
since my application times sporting event and needs to be resilient even
over an unreliable network.
I've read your paper, looked over the source code and have built
prototypes to understand how to EMFStore works and to explore the
external API. It's a very impressive piece of work!
I'm starting to integrate EMFStore with the application. The core of my
application uses code patterns generated from EMF's 'edit' and 'editor'
code generators, which leverage the EditingDomain's command stack for
executing commands, providing do/undo support and determining whether a
model instance is dirty.
EMFStore's own persistent store and ModelElements seems to be a very
different persistence model than the Resource-based XMI and CDO
persistence engines. And I'm guessing that it's use of the internal
EditingDomain is different as well.
What recommendations do you have surfacing do/undo and determining
whether model instance is dirty? Should I use the EditingDomain
available in the ESWorkspaceImpl?
Scott
|
|
|
Powered by
FUDForum. Page generated in 0.01381 seconds
] 
Search
Help
Register
Login
Home
